When the call ends, the follow-up starts on its own
Set a rule once — a missed call, an unhappy caller, a word you listen for — and every call that matches is passed on when it ends: a message to your team in Slack, a tag on the call, or a webhook to your CRM or automation tool.
Three steps in your dashboard, no code · Google Workspace in beta
The call
+1 555 0142
Didn't connectNo conversation — the call didn't connect.
The rule
When
- Call ended
- Missed call
- Negative sentiment
- Keyword heard
Then
- 1Notify Slack#front-deskWaiting
Where it lands
front-desk
Call alerts · just now
📞 inbound call from +1 555 0142 (n/a).
Play a rule
Setting one up
Three steps, no code
If you can fill in a form, you can build a workflow. Pick when it runs, pick what happens, give it a name — and it's live. Open New workflow in your dashboard and see for yourself.
- 1Choose when it runsTap one of four moments: a finished call, a missed one, an unhappy caller or a word you listen for.
- 2Choose what happensTick one or more steps. Slack needs a link you copy from Slack once; a tag needs just a word.
- 3Name it and saveGive it a name you'll recognise. It starts working on the next call, and a switch turns it off.
The idea
A workflow is a rule for what happens after the call
Every call your agent finishes becomes a record: who rang, how long it lasted, how it went, and a summary of what was said. A workflow watches for the records you care about and does something with each one.
You choose the moment — any call, a missed one, an unhappy caller, a word someone used — and the steps that follow, in order. From then on it runs by itself, call after call.
After the call
Workflows start once a call is over and its record has arrived — never mid-conversation.
In the order you set
Steps run one after another, exactly as you arranged them.
Stops at a failure
If a step fails, the ones after it don't run, and the run counts as failed.
Triggers
Four moments worth acting on
Call ended
Fires for every call the agent completes — the one to use for sending everything to your CRM.
Every call → CRM
Missed call
Fires when a call fails to connect, so a person can ring back before the caller tries someone else.
Missed → #front-desk
Negative sentiment
Fires when the call's analysis reads the caller as unhappy — a cue for a manager, not a script.
Unhappy → tag + #managers
Keyword heard
Fires when a word you choose appears anywhere in the transcript, from either side of the call.
“emergency” → on-call
Actions available today
Pass it on, mark it, or hand it to any system that listens
POST→200
Send a webhook
A POST with the call's details as JSON, to any address you give it — your CRM's inbound hook, Zapier, Make, n8n, or your own server.
Needs: a URL that accepts POST requests
# front-desk📞 inbound call from +1 555 0142
Notify Slack
A message in the channel of your choice with the caller's number, how the call went and its summary.
Needs: a Slack incoming-webhook URL
[tag:follow-up]
Tag the call
A label added to the call — follow-up, escalated, vip — so the calls that need a person stand out as you read through them.
Needs: a tag name
5 s
Wait
A short pause between two steps, for a system on the other end that needs a moment.
Up to 30 seconds
Slack, Zapier, Make and n8n are trademarks of their respective owners. Neuro Tech Voice sends data to them through their standard webhook features and is not affiliated with or endorsed by them.
For developers
What your endpoint receives
Only needed if you're connecting a system of your own — Slack and tags don't need any of this. One POST per matching call, with a JSON body.
eventAlways this value, for now.call.idThe call's id in your dashboard.call.conversation_idThe conversation's id, unique per call.call.caller_numberThe caller's number, when it was shared.call.directionWhich way the call went.call.duration_secondsLength of the call.call.statusHow the call ended.call.sentimentPositive, neutral or negative, when known.call.summaryA short summary of the conversation.call.started_atWhen the call began.timestampWhen this request was sent.
POST · Content-Type: application/json
{"event": "workflow_triggered","call": {"id": "9f1c…","conversation_id": "conv_7a2…","caller_number": "+15550163","direction": "inbound","duration_seconds": 167,"status": "completed","sentiment": "neutral","summary": "Water coming…","started_at": "2026-09-16T09:41:07Z"},"timestamp": "2026-09-16T09:44:02Z"}
No transcript in the body
The summary travels; the full transcript stays in your dashboard.
Signed
Requests carry an HMAC-SHA256 signature made with your workflow's own secret, so you can check each one came from us.
Up to three attempts
If your endpoint is down or busy, the request is tried again, up to 3 attempts; if it still fails, the run is marked failed and later steps don't run.
Knowing it worked
Every workflow keeps count of how it's doing
Each workflow shows how many times it has run, how often it succeeded and when it last ran — so the rule that broke on Tuesday doesn't stay broken until someone notices.
Emergencies to on-call
Rules to start with
Five workflows worth setting up on day one
- 01
Call endedSend webhook
Every call lands in your CRM without anyone copying it across.
- 02
Missed callNotify Slack
Someone rings back while the caller is still deciding.
- 03
Negative sentimentTag: follow-upNotify Slack
A manager hears about it the same day, not in the monthly review.
- 04
Keyword: emergencySend webhookNotify Slack
Urgent calls reach the person on call, wherever they are.
- 05
Keyword: cancelTag: retention
Customers thinking of leaving stand out the next time you read your calls.
Beta
Google Workspace, in beta
Connect your Google account and the same rules can write into Gmail, Sheets, Calendar and Docs. It's in beta, so what each one does may still change as we refine it.
BetaGmail
Emails a call's summary to whoever needs it.
BetaGoogle Sheets
Adds a row for every call: time, number, length, sentiment, summary.
BetaGoogle Calendar
Puts a follow-up for a call in the calendar.
BetaGoogle Docs
Writes a call report as a document.
Gmail™, Google Sheets™, Google Calendar™ and Google Docs™ are trademarks of Google LLC. Neuro Tech Voice is not endorsed by Google.
Questions
About integrations
Do I need to know how to code?
No. A workflow is three steps in your dashboard: choose when it runs, choose what happens, give it a name. The webhook step is there for people who have a system to connect; everyone else can use Slack and tags.
Can the agent use my tools during the call?
Partly. While the call is live, the agent can notify your on-call contact or transfer the caller to them. Workflows run after a call has ended and its record has arrived, so they suit follow-up — notifying, logging, tagging.
Which tools can I connect?
Anything that accepts a webhook, plus Slack through its incoming webhooks. That covers most CRMs and automation tools such as Zapier, Make and n8n. Gmail, Google Sheets, Google Calendar and Google Docs are in beta.
Is there a Zapier app?
Not a dedicated one. Start a Zap with Zapier's own webhook trigger, paste its address into a Send webhook step, and the call's details arrive as fields.
Does the webhook include the transcript?
No — it carries the call's summary and details. The full transcript stays in your dashboard.
How does the keyword trigger match?
It looks for the word anywhere in the transcript, ignoring capitals — including in what the agent said. Pick words callers use but your agent wouldn't.
What happens if my endpoint is down?
The request is tried again, up to 3 attempts. If it still fails, the run is marked failed, the steps after it don't run, and the workflow's success rate shows it.
Is the data I send protected?
Requests go only to https addresses and are signed with your workflow's own secret, so your system can check they came from us. You decide where call data goes, so send it only to systems you're allowed to share it with.
Can I use Google Workspace already?
Yes, in beta. Gmail, Google Sheets, Google Calendar and Google Docs connect through your Google account; while they're in beta, what they do may still change.
Get started
Start with the call you'd hate to miss
Make a workflow for missed calls, point it at the Slack channel your team reads, and the next one that slips past has someone ringing back.