Call triggers: lifecycle, duration, context and contact
Automate actions at every stage of a call: received, answered, missed, rejected, ended, by duration, or by the contact's history.
Watch this step in the video · Orders, payments, calls and more
What it is and when to use it
Omnifox materializes every call as a conversation, so you can fire workflows at any point in its lifecycle. These triggers live under the Call triggers group in the palette and let you route, tag, notify and follow up with no manual work.
Requirements
- A connected voice channel (WhatsApp Calling or the Omnifox PBX).
- A plan with the call triggers feature enabled. If your plan doesn't include it, these triggers won't appear in the palette.
The available triggers
- Call received (
call.received): an inbound call rings. Includes$is_new_contact. - Call answered (
call.answered): an agent picks up. Carries$user.id,$user.nameand$call.answered_at. - Call missed (
call.missed): nobody answered. Carries$call.ring_duration. - Call rejected by agent (
call.rejected_by_agent): the agent declined it. - Call ended (
call.ended): it finished. You can filter by Final status (completed, no answer, busy, failed, cancelled, voicemail) and use$call.recording_url. - Call duration over threshold (
call.duration_threshold): fires when the call exceeds the seconds you set in Threshold (seconds). - Contact's first call (
call.contact.first_call): the first time that number calls you (supports "once per contact"). - Repeat caller (
call.contact.repeat_caller): fires on a Minimum recent calls count within a Look-back window (days). - Out-of-hours call (
call.out_of_hours): the call lands outside the workspace's business hours.
Steps
- Open Workflows and click Create workflow.
- In the palette, expand Call triggers and pick the trigger you need.
- In the inspector, set the common filters: Specific channel and Direction (inbound/outbound). Some add their own filters (threshold, final status, recent-calls window).
- Build your actions using the event variables:
$call.id,$call.direction,$call.status,$call.from,$call.to,$call.duration, plus the contact variables. - Save and turn the workflow on.
Examples
- Missed-call callback: with Call missed, send an automatic WhatsApp "We saw your call, how can we help?".
- VIP welcome: with Contact's first call, add a
new-leadtag and notify sales. - After hours: with Out-of-hours call, reply with your support hours and create a follow-up task.
Verify it
Place a real test call to the channel number. In the workflow, check the runs tab to confirm it fired and that variables ($call.duration, $call.from) arrived with data.
If it doesn't work
- They don't show in the palette: your plan doesn't have the call-triggers feature enabled.
- It never fires: review the Direction and Specific channel filters; a wrong channel filter blocks everything.
- The threshold never trips: Duration over threshold compares against the final duration; shorter calls won't match.
- Test with a real call: smoke tests don't reproduce the voice channel's behavior.
Tips
- Pair Repeat caller with auto-assignment to always route frequent customers to the same agent.
- Use Call ended with the voicemail status filter as a bridge into your voicemail workflows.
Related articles
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.