Skip to content
Help Center
Submit a request Sign in

Configure inbound email routes

Email routes turn forwarded support mail into new cases or replies on existing cases. Each route has a generated forwarding destination and a predictable set of case, matching and contact-handling rules.

Applies to: Supportbench Core. Location: Settings → Email configuration → Routes (inbound email). Editing requires Administer email routes.

Before you begin

  • Identify the customer-facing mailbox or distribution group, its mail administrator and the intended Case Division, Priority and Queue.
  • Decide how replies should match existing Cases and how unknown senders should become Contacts. These are customer-identity and routing choices, not just mailbox labels.

Configure and verify

  1. Open Settings → Email configuration → Routes (inbound email) and choose New Route.
  2. Enter Name and select the required Division, Priority and Queue. Choose Email forms only where structured messages need parsing.
  3. Review Match by message references and Match by subject. Message references use email headers; subject matching is a fallback when those headers are unavailable and repeated subjects can group unrelated mail.
  4. Review Create missing contacts and Use forwarded sender as contact. Confirm which sender should identify the customer before enabling automatic creation or forwarded-sender handling.
  5. Review Active and choose Save Changes. Reopen the route, then Copy its generated read-only Forwarding address.
  6. Have the mail administrator configure forwarding from the intended mailbox or distribution group to that exact address. Saving the Supportbench route does not configure the mail provider.
  7. Send one approved new-message test and a reply. Confirm Case creation, Division, Priority, Queue, Contact identity, attachments and reply matching.
  8. Before deactivating or deleting the route, arrange the replacement intake path. These actions stop processing through that route.

Settings reference

Route details and case defaults

SettingWhat it controlsHow to choose
Name / DescriptionAdministrative identity and explanation for the route.Name it after the shared mailbox or channel.
Forwarding addressGenerated read-only destination available after save; Copy puts it on the clipboard.Use the exact destination in your mailbox provider’s forwarding configuration.
Active routeControls whether the route processes forwarded mail.Only activate a route that is ready to receive the intended mailbox.
DivisionDivision for cases created through this route.Choose the team’s intended case scope.
PriorityStarting priority for newly created cases.Choose a normal baseline and let reviewed workflows handle exceptional urgency.
QueueInitial work queue for new cases.Choose a monitored queue with a clear owner.
Email formsOptional parsing forms that extract structured content into fields.Add only forms that match the sender and format of this mailbox.

Matching and contact handling

SettingWhat it controlsHow to choose
Match by message referencesUses email conversation headers to attach replies to existing cases.Preserve message references in forwarding and test a reply to an existing case.
Match by subjectUses subject text to find a case when references are unavailable.Review repeated-subject messages to avoid unintended grouping.
Create missing contactsCreates a contact when the sender is not already known.Enable when this mailbox accepts legitimate new customer contacts.
Use forwarded sender as contactUses the original sender on a forwarded message instead of the forwarding mailbox.Test the exact forwarding format your provider produces.

Behavior to know

  • Deactivating or deleting a route stops mail processing through it. Plan mailbox forwarding changes before removing a route.

Recommended use

  • Keep spam and security filtering in the mailbox provider.
  • Avoid catch-all and personal-inbox forwarding unless its scope is intentional.
  • Keep inbound routes and outbound reply identities documented separately.

Worked example: verify a shared equipment-support intake route

  1. Identify the approved shared mailbox and who monitors its incoming work. In New Route, select the actual intended Division, baseline Priority and monitored Queue. Any names in a teaching example are illustrative, not guaranteed built-in records.
  2. Review Match by message references and any subject fallback. If the mailbox accepts new customer contacts, decide deliberately whether Create missing contacts is appropriate. If messages are forwarded, decide whether the original sender should become the Contact and test the exact provider format before relying on Use forwarded sender as contact.
  3. Choose Save Changes, reopen the route and copy its generated Forwarding address. Have the mail administrator configure the mailbox provider to use that exact destination. Saving the route alone has not changed the provider.
  4. Send an approved new message from a controlled known Contact. Verify the new Case’s Division, Priority, Queue, Contact and attachments, then reply through the normal conversation and confirm the incoming reply joins the intended Case.
  5. If unknown-sender intake or original-forwarded-sender handling is part of the approved design, test each separately with synthetic identities and inspect the actual selected or created Contact. Record the original sender and forwarding mailbox evidence so an identity mismatch can be traced.
  6. Investigate a failed delivery at the provider/route boundary, a wrong Contact at sender handling, and an incorrectly grouped reply at the matching settings. Keep outbound reply-address setup separate. Do not repeatedly resend real customer mail or change all matching options at once to diagnose a single symptom.

Troubleshooting

ProblemWhat to check
No Case arrivesVerify Active, the saved Forwarding address, provider forwarding and mail delivery evidence. Check whether the route was deactivated or deleted.
A reply creates a different CaseInspect message-reference headers and matching options; then review subject fallback carefully.
Unrelated messages are groupedRepeated subjects can be misleading. Review Match by subject and the original message headers.
The wrong Contact is selectedReview forwarded-sender handling and missing-contact creation with the original sender/forwarder evidence.
Structured fields remain emptyCheck the selected Email forms and whether the original message matches the form’s filters and delimiters.
I cannot save the routeCheck Administer email routes and the required Division, Priority and Queue.
  • Email configuration → Configure reply addresses and signatures
  • Email configuration → Parse structured inbound email with route forms
  • Configuration → Configure workflows and automation

Was this article helpful?