-
Notifications
You must be signed in to change notification settings - Fork 0
Demo Part 1 Step 1 Trunk to Queue Basic
Andrey Egorov edited this page May 18, 2026
·
2 revisions
Import: part-1-step-1-trunk-to-queue-basic.json
Complete the smallest queue scenario:
- answer an inbound trunk call
- let the caller choose
SupportorSales - place the caller into the selected queue
- play hold music and periodic queue-position prompts
- dispatch directly to a live agent
- play a plain offline announcement if nobody is online
- queue placement
- queue
Placed,Dispatch, andOfflinehandling - a stable hold loop
- direct agent bridge from queue dispatch
-
put_supportandput_salesplace the current caller leg into the daemon-owned queue, so queue events later refer to the same live caller. -
play_musicruns in background mode, so hold music can continue whilequeue_statandplay_statrun on top of it. -
wait_music_loopis a30-secondcall.waitwithInterrupt On = call_queue_removed. It acts as the queue timer, but also stops quietly if the queue engine has already removed the caller from live waiting. - the
Interruptedbranch ofwait_music_loopis intentionally empty. Once queue has removed the caller, the loop must not continue into another queue stats cycle. -
wait_agentis dial-scoped only. It does not useMaster Leg ID, because queue itself already owns caller-leg cleanup and aborts the queue dial if the caller disappears. -
bridge_agentuses the queued caller leg fromdispatch_entry, so the dispatch branch can bridge the agent directly to the live waiting caller without callback logic. -
play_offlinehasStop Other Media = true, so hold music is removed before the offline announcement starts.
- Import the workflow.
- Activate it.
- Register queue agents from
internal. - Place a trunk call.
- Press
1forSupportor2forSales.
| Situation | Result |
|---|---|
| agent becomes available | queued caller is bridged directly to the agent |
| queue stays busy | caller hears hold music and queue-position prompts |
| no online representatives | caller hears the plain offline announcement |
Part 1 / Step 2 keeps the same queue core and replaces the plain offline announcement with an AI handoff.