<aside> ℹ️

Prerequisite: This guide assumes you have completed the Interaction Parking: Mitel Workflow Setup guide and have a functioning Hunt Group, speed calls, parking lot, API key, and YSE workflow in place.

</aside>

Introduction

Use this guide when your Voice AI Bot handles the inbound call and you want to hand off to a human agent — passing full interaction context (transcript, collected data, console URL) through to the agent's WebIgnite console.

When the bot decides to transfer, it claims a free parking space, stores the interaction metadata against that slot, and SIP Refers the call to the corresponding speed call extension. The MCX workflow then retrieves the metadata via the Talkative API and routes the call to the correct queue.

image.png

Configuring the Transfer Tool in Your Voice Bot

Navigate to your Voice Bot in Talkative and add a Transfer Tool. Within the tool, add a destination and configure it as follows:

Option Value Details
Transfer Type Interaction Parking Lot Instructs Talkative to claim a parking space, store metadata, and SIP Refer the call
Parking Lot {your parking lot} Select the parking lot created in the workflow setup guide
Destination {target extension or queue} The destination the MCX workflow will transfer the call to after retrieving metadata
Prompt e.g. "Use this to transfer to the agent queue" Tells the AI when to invoke this transfer
Voice Assist Config Leave blank Adding a Voice Assist Config changes the transfer from SIP Refer to SIP Dial — see the Voice Assist guide if required

How the Flow Works

When the bot invokes this transfer tool:

  1. Talkative identifies a free parking slot and stores the interaction metadata (transcript, collected data, destination, console URL) against it
  2. Talkative SIP Refers the call to the parking space speed call extension (e.g. ext. 1000) — the bot leg ends here
  3. The MiVB Hunt Group picks up and fires the YSE Workflow
  4. The workflow makes a REST GET request to the Talkative Parking Lot API, which returns the metadata and clears the slot
  5. The workflow assigns the returned values to variables and transfers the call to the returned destination
  6. MiVB routes the call to the agent's extension — the agent answers in WebIgnite
  7. The Console URL and Interaction Log URL are surfaced in WebIgnite, giving the agent full interaction context

Next Steps

Once a call has been successfully transferred and the agent can see the interaction data in WebIgnite, the setup is complete.

If you also need Voice Assist — live transcription and AI assistance during the agent leg — see the Interaction Parking for Voice Assist guide.