Docs/AI agentsAdvanced
Sendify automations guide
Automations are how a conversation turns into work getting done: a notification, a CRM update, a booking, a handoff, or the AI stepping aside.
How automations fire
Triggers come from the conversation itself: the lead asking for something, becoming qualified, booking, or getting disqualified. Actions are the things Sendify then does, inside Sendify or inside your CRM. The node by node reference lives in the automations section of the AI builder guide.
Common patterns
| When this happens | Do this |
|---|---|
| Lead asks for a call | Notify the rep then Disable the AI |
| Lead books | Generate a summary then Update the CRM then Disable the AI |
| Lead books | Hand off to a confirmation AI |
| Lead needs a different time | Reschedule the appointment |
| Lead is disqualified | Update the CRM then Disable the AI |
| Lead gives key qualification info | Save it to a CRM or custom field |
| Lead becomes qualified | Update CRM status then Notify the salesperson |
Start with two
Controlling the AI
Automations can also decide how involved the AI stays:
| Control | What it does |
|---|---|
| Disable the AI | The AI stops replying on that conversation |
| Keep the AI active | The AI keeps handling the thread after the automation runs |
| Disable follow ups only | The AI still replies when the lead writes, but stops chasing unanswered messages |
| Hand off to another AI | A different AI takes over, for example a confirmation agent |
Remember that a human sending a message does not switch the AI off by itself. That is covered in taking over a conversation.
Still need a hand?
If your volume is going to run past the daily or hourly limits, or something is not behaving the way these docs describe, talk to our team.