Workflow
How an email assistant sorts and answers email — Incoming email, Classify, branches, Reply, Fixed reply, Leave for a person, and actions like Extract data, API request and Integration
Every email assistant runs on a workflow: one incoming email in, at most one reply out. Open it on the assistant's Workflow tab. It is the same canvas as for voice agents, with steps made for email — there are no keypad, phone transfer or End call steps here.
You can change the workflow yourself on the canvas, or ask Marcus — changes to what the assistant answers are made by HANC Studio.
The standard workflow
A new assistant built From scratch starts with this workflow:
Incoming email → Classify
├─ billing → Leave for a person
├─ simple → Reply
├─ complaint → Leave for a person
├─ sales → Reply
└─ other → Leave for a person
Simple questions and sales enquiries get an answer; invoices, complaints and anything unclear are left for you. Rename the categories, add your own, and decide for each one: answer or leave.
Steps
Incoming email
Every email to the mailbox starts here. Add branches to sort the emails, then a Reply step for each — that is where you set what to answer.
Classify / decide
Reads the email and decides which branch it goes to — it doesn't answer. Describe the categories in plain words ("refund, order, complaint, or other") and list their exact values: each branch leaving this step carries one value. The result is saved in a variable, category by default.
Reply
Writes the answer. In What to reply, give the instructions for this kind of email; the assistant writes the email from them and always answers in the sender's language. On the same step pick a signature and attachments — see Signatures and files.
A Reply is the end of its branch.
Fixed reply
Sends your exact text, word for word — for the emails that always get the same answer.
Leave for a person
The assistant doesn't answer; the email waits for you in the mailbox. On the Activity tab it shows as For a person.
Actions
Actions run along the way, before the reply:
- Extract data — reads the email and saves the fields you name as variables, for example
order_number,first_name,delivery_date. Reuse them anywhere with{{name}}— in branches, integrations and the reply. - API request — calls your system with the data, for example to look up an order status, and saves the answer in a variable the reply can use.
- Integration — the same integrations as in voice workflows: put the contact into HubSpot, GoHighLevel or another CRM, add an appointment to the calendar, using the variables from the email.
Variables of the email
Branches, actions and replies can use the fields of the incoming email:
| Variable | What it holds |
|---|---|
{{subject}} | The subject |
{{from}} | The sender's email address |
{{from_name}} | The sender's name |
{{body}} | The text of the email |
plus everything a Classify or Extract data step saved.
Tips
- Start with drafts. Keep Draft for review for the first days and read what the assistant writes; switch to Send automatically once the drafts are right.
- Leave the sensitive things to a person — money, complaints, legal questions.
- Give it facts. The assistant only sends what it can confirm in the knowledge base; everything else stays a draft.
- Check Activity. It shows which branch each email took and why — see Activity.