Workflows
Build pre call, during call and post call actions and enable them on an agent.
Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.
A workflow is a reusable set of actions an agent can take around a call: look up an account before dialling, check a calendar while the caller waits, or write the outcome to your system when the call ends. You build a workflow once, then enable it on every agent that needs it. Each action is an HTTP request to one of your own APIs.
When a workflow runs
| Category | Runs | Typical use |
|---|---|---|
| Pre call | Before the call starts | Load the amount due, the application status or the customer's history |
| During call | While the conversation is live, when the agent decides it needs it | Check availability, book a slot, check a date against policy, look up an order |
| Post call | After the call ends | Write the outcome, open a ticket, alert a person |
A workflow belongs to one category and always runs at that point in the call. You cannot move it to a different stage from the agent.
Create a workflow
- Open the workflows area of the dashboard or admin console.
- Choose the category: pre call, during call or post call.
- Create a new workflow and give it a name that says what it does, such as Check due amount or Book test drive.
- Make sure it is enabled, so it can be assigned to agents.
- Add one or more actions, described below.
- Save.
Add an action
Each action is one request to one endpoint.
| Setting | What to enter |
|---|---|
| Action name | A short, code style name such as check_due_amount. Letters, numbers, underscores and hyphens only. The agent uses this name to call the action. |
| Method and URL | GET, POST, PUT, PATCH or DELETE, and the endpoint. The URL can contain variables. |
| Headers | Any headers the request needs, as name and value pairs. |
| Body | A JSON request body, which can contain variables. |
| Authentication | None, basic (username and password), a bearer token, or an API key sent as a header or query parameter. |
Test the action before saving: the request runs with sample values in place of the variables, and you see the status, timing and response body.
Variables in actions
Variables are replaced with real call details when the action runs.
| Group | Variables |
|---|---|
| Customer | Name, phone number, email |
| Call | Summary, outcome, duration, call ID |
| Agent | Agent name |
For example, https://lms.example.com/accounts?phone={{customer_phone}} is sent with the caller's number in place of the variable.
Where actions can reach
On Xebit VoiceCloud, actions are sent from Xebit's infrastructure, so your endpoints must be reachable from the internet. Restrict them with authentication.
On Xebit VoiceKit, actions are sent from your own deployment, so they can reach internal systems. In an air gapped deployment they can only reach systems inside the network.
Enable a workflow on an agent
- Open the agent and go to its workflows.
- Add a workflow. Workflows are grouped as pre call, during call and post call, and you can search by name or action.
- Add each workflow the agent should use. It appears in the agent's enabled workflows, under its category.
- Save the agent.
Removing a workflow from an agent only disables it for that agent. The workflow itself, and other agents using it, are unaffected.
Preview what the agent will do
An action contains technical detail the agent does not need to read. Xebit turns each enabled workflow into plain instructions the agent follows on the call: when to use the action, what to find out from the caller first, and what to say when it succeeds or fails. You can preview these instructions for one workflow or for all of an agent's workflows together, and add them to the agent's instructions if you want to adjust the wording.
You do not need to add them for the workflow to work. Enabling it is enough.
How the agent calls an action
The generated instructions use one fixed form, which you must keep if you write your own guidance around an action:
call_workflow_api(action_name="check_due_amount", variables_json={"phone_number": "<caller's phone number>"})action_namemust match the action's name exactly, including case.variables_jsonholds only the values that action needs. Each comes from the call context, from what the caller said or from an earlier action's response. If a value is not known yet, the agent asks for it rather than inventing it.- Before the call, the agent says a short filler such as "Let me check that for you", so there is no silence.
Manage workflows
For each workflow you can see how many actions it has and which agents use it, and you can edit, duplicate, enable or disable, or delete it.
Workflows are shared. Editing a workflow changes it for every agent that uses it. To change behaviour for one agent only, duplicate the workflow and enable the copy on that agent.
Examples
- EMI reminders: a pre call action loads the amount due, a during call action checks a new date against policy, a post call action writes the promise to pay.
- Test drive and service booking: during call actions read the calendar and write the booking.
Next steps
- Workflows & Integrations: the CRM connector, webhooks and the REST API
- System Prompt: the tokens that tell the agent which actions exist
- Agent Testing