How do I sort and route incoming email to the right team automatically?

You draw it. Mail arriving at dispatch@ gets classified as a quote, a tracking question, a carrier update or an exception, and each type follows the path you designed. Changing the map is changing a diagram, not writing code.

Can it answer track-and-trace email on its own?

Where you allow it. Status replies come from templates you wrote, and each branch either sends or waits for approval. Most desks start with approval on everything and let the proven branches go automatic after a couple of weeks.

What happens to mail it cannot classify?

It goes to the catch-all branch — normally 'tell the team, leave it in the inbox'. Nothing is dropped, which matters when the unclassifiable message is an angry shipper.

Do we have to change email provider or addresses?

No. dispatch@ and quotes@ stay exactly where they are, on a domain you already own. The workflow attaches to them.

Does it run after hours and through peak?

It runs on every message whenever it arrives. Routine replies go out at 2am if you let them; anything held for approval is waiting as a sorted list rather than a raw inbox when the morning shift starts.

← All use cases

dispatch@quotes@ops@

Email automation for logistics and freight

A freight desk is an inbox with a company attached. Quotes, track-and-trace, carrier updates and the one message that turns out to be a damage claim all arrive in the same place, and somebody has to read every one to find out which is which. An agent reads them first.

What it looks like today

Quote requests worth real money sitting under carrier updates until someone digs them out.
The same one-line status answer typed out all day while the sender waits four hours for it.
Mail forwarded around dispatch until it finds whoever owns that lane, and a night shift's worth of it waiting every morning.

How the dispatch@ workflow runs

1
Mail arrives at dispatch@ or quotes@
Your addresses, your domain, unchanged. The workflow triggers on every message.
2
It gets a request type
Quote, track-and-trace, carrier update, exception. You set the categories to match how the desk actually works, not how a vendor thinks it should.
3
Status questions get answered, quotes get routed
A status question comes back from your own template within the minute. A quote request goes to the person who owns that lane, with the reference and the details pulled out of the email.
4
Exceptions stop the automation
Damage, delays with money attached, claims. These skip every automatic path and land with a person.

What changes

Track-and-trace gets answered in minutes at three in the morning.
Quotes reach the right lane owner first time, with the details already pulled out.
Peak season raises the message count, not the number a dispatcher has to read.

Where you stay in charge

Freight email moves money and freight, so the agent only runs the lanes you drew.

Anything with a price in it waits for a dispatcher. The workflow drafts and routes; it does not quote.
Exceptions, damage and claims escalate untouched, arriving with the request type and details attached.
Whatever cannot be confidently classified lands where your team can see it. In this business the unclassifiable email is usually the claim.

One morning, concretely

A track-and-trace request arrives at 06:00. By 06:01 the sender has a status reply built from your template, and the quote request that came in behind it is with the right lane owner, details extracted.

Questions people ask

How do I sort and route incoming email to the right team automatically?: You draw it. Mail arriving at dispatch@ gets classified as a quote, a tracking question, a carrier update or an exception, and each type follows the path you designed. Changing the map is changing a diagram, not writing code.
Can it answer track-and-trace email on its own?: Where you allow it. Status replies come from templates you wrote, and each branch either sends or waits for approval. Most desks start with approval on everything and let the proven branches go automatic after a couple of weeks.
What happens to mail it cannot classify?: It goes to the catch-all branch — normally 'tell the team, leave it in the inbox'. Nothing is dropped, which matters when the unclassifiable message is an angry shipper.
Do we have to change email provider or addresses?: No. dispatch@ and quotes@ stay exactly where they are, on a domain you already own. The workflow attaches to them.
Does it run after hours and through peak?: It runs on every message whenever it arrives. Routine replies go out at 2am if you let them; anything held for approval is waiting as a sorted list rather than a raw inbox when the morning shift starts.