Sales email automation
A lead that waits is a lead that cools. An agent on sales@ reads each enquiry, tells a buyer apart from a vendor pitch, and gets a real first answer out before the prospect has moved on to whoever replied faster.
What it looks like today
- Someone asks about pricing on a Friday afternoon and books a call with a competitor on Monday.
- sales@ is half prospects and half recruiters, invoices and newsletters, so nobody wants to be the one who reads it.
- Nothing anywhere records which enquiries got an answer and which did not.
How the sales@ workflow runs
- 1
An enquiry arrives at sales@
Whether it came from your pricing page, a referral or out of nowhere, the workflow runs on it.
- 2
Buyers get separated from everything else
The first branch is simply: is this someone who wants to buy? Vendor pitches, invoices and newsletters stop here. Everything after this only runs on real enquiries.
- 3
The intent decides the reply
'What does this cost for forty seats' and 'just having a look' are not the same email. Each gets its own path — your pricing answer, a couple of questions back, or straight to a person.
- 4
The follow-up is a step, not a promise
'Get in touch next month' becomes a wait node with a date on it. The thread comes back when it should, with a draft that refers to the first conversation.
What changes
- Enquiries get a substantive answer the same hour, including the ones that arrive at the weekend.
- Your reps read a filtered queue instead of a shared inbox.
- Every 'I'll circle back' has a date attached and actually happens.
Where you stay in charge
The agent handles the first response and the chasing. What you promise a prospect stays yours.
- Anything with a number in it — discounts, custom terms, a quote — is the obvious thing to keep behind approval, and most teams do exactly that while letting scheduling replies send themselves.
- Partnership pitches, legal questions and anything unusual escalate with a summary rather than collecting a templated answer.
- There is no built-in CRM sync. If you want leads in your CRM, your own tooling reads the threads through the API or the MCP server and writes them where you want them — with server-side permissions, not a prompt.
One morning, concretely
A prospect asks about pricing for forty seats at 16:50 on a Friday. By 16:52 they have your pricing answer and two suggested times, and the rep who owns it finds the thread already sorted on Monday.
Questions people ask
- Does this send cold outreach?
- No. Every workflow here starts from mail that arrives — someone wrote to you first, and the agent answers them. Nothing here sends to a list of people who did not.
- Which CRMs does it integrate with?
- None directly, and we would rather say so than imply otherwise. What you get is an API and an MCP server with capability-scoped keys, so your own automation can pull the thread, the classification and the draft and put them wherever your team works.
- Can AI write the replies to prospects?
- It drafts them, from the material you wrote. Whether a draft sends itself or waits for a rep is set per mailbox, and you can keep the money conversations behind approval indefinitely.
- What happens to the spam and newsletters that hit sales@?
- They get classified as what they are and stop there. Anything the agent is unsure about goes to a human instead — a real lead never gets binned for being unusual.
- Can I try it without it emailing anyone?
- Yes. Leave approval on. The agent still reads, classifies and drafts everything; nothing leaves the building until someone clicks send.
