Letterbook
All docs

Letterbook Docs

Auto label tickets

Apply labels automatically based on sender or subject rules.

Last updated June 25, 2026

What this guide covers#

Auto-labeling applies labels to conversations based on predictable sender or subject patterns. Use it to make queues easier to scan and to prepare tickets for routing, reporting, or AI review.

Configure it in Settings > Automations > Auto Label Tickets.

Before you start#

Create the labels you want to apply before adding auto-label rules. If no labels exist, Letterbook will prompt you to create labels first.

Good first labels include:

  • Billing
  • Bug
  • Enterprise
  • Refund
  • Churn risk
  • Partner
  • Security

Rule types#

Rule typeMatches
Sender email/domainThe sender's full email address or domain
Subject containsText contained in the email subject

Sender rules accept either a full email address, such as finance@customer.com, or a domain, such as customer.com.

Subject rules are useful for recurring system-generated emails, billing notices, app store reviews, import workflows, or customer forms that include consistent subject text.

Add a rule#

  1. Go to Settings > Automations.
  2. In Auto Label Tickets, select Add rule.
  3. Choose Sender email/domain or Subject contains.
  4. Enter the pattern.
  5. Select the label to apply.
  6. Save the rule.

Letterbook lowercases and trims the pattern before saving it. It also prevents duplicate rules with the same match type, pattern, and label.

Examples#

GoalMatch typePatternLabel
Label all email from a customer domainSender email/domainacme.comEnterprise
Label messages from a billing systemSender email/domainbilling-provider.comBilling
Label cancellation requestsSubject containscancelChurn risk
Label invoice questionsSubject containsinvoiceBilling

Best practices#

  • Prefer domain rules for known customer or partner domains.
  • Prefer subject rules only when the subject text is stable.
  • Keep labels meaningful to agents, not just reporting.
  • Review rules after changing label names or support workflows.
  • Avoid over-labeling. Too many automatic labels can make conversations harder to scan.