Skip to main content
Workflows turn what happens on a call into automatic follow-up actions. Pick a trigger like Call ended, add the actions you want (send a webhook, update a contact, sync to Salesforce), and telli takes care of the rest after every call.

What you can automate

Use caseWhat it does
Push call data to your toolsSend call summaries, outcomes, and collected data to a URL after every call.
Keep contact records currentUpdate telli contact fields or custom properties based on what the agent collected.
Sync your CRMCreate or update Salesforce records straight from a completed call.
Branch on call resultsUse conditions so only certain calls trigger certain actions (e.g. only qualified leads sync to Salesforce).

Available blocks

Triggers decide when a workflow runs. Today, workflows run after a completed call:
BlockUse it to
Call endedEvaluate the workflow after a completed call from a selected agent

Build your first workflow

1

Open Workflows and create a new one

Go to Workflows in the telli dashboard and click Create Workflow.
2

Name and describe the workflow

Use a name that describes the result, like “Send call summary to CRM” or “Update lead status after call”.
3

Select and configure a trigger

Choose Call ended as the trigger, then pick the agent whose completed calls should start the workflow.
4

Add action and condition blocks

Use the + button on the canvas to add blocks after the trigger. Configure each block in the side panel, and add If / else or Switch when only some calls should follow a given path.
5

Publish the draft

Click Publish once the trigger and required blocks are configured. Publishing creates the version telli uses for new runs.
6

Enable the workflow

Flip the Enabled switch to turn on automatic execution. A workflow must be published before it can be enabled.
Test with a manual run before relying on automatic execution. In the workflow builder, open the Runs tab, click Run manually, and pick a completed call to step through the workflow against real data.

Go deeper

Workflows reference

Full reference for triggers, blocks, manual runs, version history, and end-to-end examples like logging telli calls back to Salesforce.