The follow-up nobody forgot, because nobody had to remember
When something happens in a conversation, something else happens — every time, at the hour you chose.
The situation today
The second message is the one that closes. It is also the one that gets skipped when the day is busy, and there is no way to tell which ones were skipped.
The answer
Automations that run from what a conversation did: a label added, a form filled, a call ended, a stage moved. Each run is recorded, including the ones that did nothing and why.
What you actually get
- Triggers from real events, not a clock nobody set.
- Steps that send, tag, assign, call a webhook, or wait for your own server.
- A run that could not happen says so, with the reason.
- Runs are bounded by your plan, so one busy agent cannot flood anything.
The limits that actually move for this
Every limit is sold on its own. If this is the only thing you need, these are the only numbers your quote is built from — and the maximum you agree is the maximum the system enforces.
-
Automations
automations
Generous by default
Automations held, draft or live.
-
Automation runs
runs a month
Metered
Times an automation ran from start to finish.
-
AI skill calls
calls a month
Metered
Times the AI used one of your skills (your own system) in a conversation.
-
Webhook endpoints
endpoints
Generous by default
Endpoints of the customer's own subscribed to events.
Runs and skill calls are fractions of a cent, so the allowances are large. The stop exists to bound a runaway loop, not to charge you.
Questions about Automations
What happens if I run out of runs?
A run over the limit is recorded as "Not run" with the reason, and does nothing. It never half-runs.
Ready to put this to work?
Start on the free tier with your own documents, or tell us what you need and we will price exactly that.