AI Automations
Turn on AI features that run automatically in the background of your account. Each toggle lives in Settings → AI and can be flipped on or off at any time by a client admin.
Available automations
- Auto-transcribe & summarise every call - When a call ends, we transcribe it and drop a short AI summary plus action items onto the contact. (~2 credits per call.)
- Auto voicemail digest - Every voicemail is transcribed with a one-line summary you can scan in the inbox. (~1 credit per voicemail.)
- Auto task triage - New tasks are auto-categorised, prioritised, and assigned to the right team member. (~1 credit per task.)
- Auto proposal draft - A proposal is drafted automatically when a lead reaches the Proposal stage. (~5 credits per proposal.)
How credits work
Each automation deducts from your account's monthly AI credit allowance. If you need more triggers than what's listed, contact support and we'll add them.
Merge fields: Full responses
When you write an automated email or SMS you can insert Full responses from the token picker ({{form.full_responses}}). It expands to every question and answer from the form the contact submitted, one pair per line:
What is your full name?: John Smith
What is your approximate monthly revenue?: $100k-$200k
Do you own a business?: Yes
Notes:
- If a contact submitted more than once, the most recent submission is used.
- Questions are shown exactly as they were asked at the time - editing a form later never rewrites old answers.
- Skipped questions are left out, and contacts with no form submission simply get nothing in that spot.
Sending form answers to another system
To push answers into a CRM or spreadsheet (Zapier, Make, AgencyZoom and similar), use a Webhook step instead of an email.
On a webhook step, the Payload fields section defines exactly what gets sent. Each row is a key and a value, and the value can contain any merge token:
| Key | Value |
|---|---|
full_name |
{{contact.name}} |
phone |
{{contact.phone}} |
answers |
{{form.responses_json}} |
{{form.responses_json}}is the machine-readable version of Full responses. It sends every answer as structured JSON, so the receiving system can pick out individual fields:
{
"roof_age": { "label": "Roughly how old is the roof?", "value": "0-10 years" },
"quote_type": { "label": "What do you want quoted?", "value": "Home" }
}
{{contact.<field key>}}sends one specific answer - for example{{contact.roof_age}}. The field key is shown on each question in the form builder.- Payload fields on a webhook step are sent to the URL only; they never change the contact record.
- If the receiving system returns an error, the automation run is marked failed with the status code, so a broken integration is never reported as a success.
Copying and deleting steps in the builder
Hover any step in the automation builder to reveal its quick actions:
- Copy - copies just that step.
- Copy with everything below - copies the step and the whole chain beneath it.
- Paste - drops the copied step(s) directly below the step you're hovering, or from the + button menu at the end of a branch. Anything that was already below stays attached under the pasted steps.
- Delete - removes only that one step. Steps below it are kept and re-attached to the step above. (Deleting a "Split into paths" step still removes its branches, since there's nowhere to reattach them.)
Assigning leads round-robin
The Assign to user step has two modes:
- Assign to specific user - pick the person from a list of team members on the account. The choice is stored against the person, not their email address, so it keeps working if their email changes, and someone who has left the account can't be picked. Switch to Use a merge token for dynamic assignment (e.g.
{{lead.owner_email}}); the token is resolved to an email at run time. Either way, if the step can't resolve exactly one team member the lead is left unassigned and the run log says why. - Round-robin - you tick exactly which team members are in the rotation. Leads are handed out in turn, one each, and the position is remembered between runs.
The rotation never includes people you didn't tick, and anyone who leaves the workspace is skipped automatically. If no one is selected, the step assigns nobody and records the reason on the contact's timeline rather than guessing.