Votel workflow triggers and blocks explained.
How an event becomes a reliable chain of conversation, decisions, data, actions, and handoffs.
A Votel workflow is a visual automation made from a trigger and connected action nodes. The trigger decides when the workflow starts. Nodes decide what the agent says, what information it saves, which route it follows, which external tool it calls, and when it transfers to a person or another agent.
Triggers start the work
Every workflow needs at least one trigger. Votel documents triggers for new conversations, inbound calls, inbound messages, schedules, webhooks, app events, pipeline changes, contact conditions, tags, appointments, and execution by another workflow.
| Trigger | Useful example |
|---|---|
| Conversation started | Route a new phone, SMS, email, or widget conversation into one intake flow. |
| Inbound call | Run call-specific greeting, qualification, and transfer logic. |
| Form submitted | Respond quickly, create or enrich the contact, and start follow-up. |
| Appointment scheduled | Send confirmation, reminders, and internal preparation tasks. |
| Pipeline column change | Start the next action when a deal reaches a defined stage. |
| Webhook or app event | Begin work when another system sends an event. |
Nodes perform and direct the work
Votel's documentation calls these workflow building blocks nodes. On All Things Votel, the poster also uses the plain-language term “blocks.” Both refer to the actions and decisions placed after a trigger.
- Conversation nodes produce fixed or AI-generated responses and can branch by intent.
- Ask and Save collects information into a field or variable.
- Decision nodes evaluate explicit rules such as a field value or empty state.
- Classifier nodes use AI to interpret context such as intent, urgency, or sentiment.
- Call forwarding transfers to a person, while Forward to Agent hands the conversation to another AI agent.
- API and integration nodes read or write data in another system.
Conversation routes are not ordinary branches
A conversation node can respond dynamically and route based on what the caller means. Route titles, synonyms, and instructions help it recognize different ways a person may express the same intent. For hard business rules, use a decision node instead. AI interpretation is useful for language; explicit rules are better for exact data.
A simple receptionist workflow
- Inbound Call trigger starts the flow.
- Conversation node greets the caller and asks what they need.
- Intent routes separate booking, urgent service, existing customer, and general questions.
- Ask and Save collects name, contact details, location, and relevant context.
- Calendar action checks availability and books when appropriate.
- Decision confirms whether a booking was completed.
- Follow-up action sends confirmation or creates a human task.
How to keep workflows reliable
- Name each trigger and route for the business outcome it represents.
- Give every uncertain path a human handoff or safe fallback.
- Keep disclosures and policy language static when wording must not vary.
- Test all routes, not only the happy path.
- Log important outcomes in the contact record.
- Break very large workflows into smaller reusable flows where sensible.
Primary sources: Votel's workflow overview, trigger documentation, and conversation node guide.
See the full inventory
The free Votel Workflow Poster maps 130 triggers across 29 groups and 108 blocks across 9 groups, read from the live builder on September 11, 2026. Use it as a visual reference, then verify changing details inside the current builder.