> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ixhc/multi-agent-support-gen-ai-voice-bot/orchestration-for-multi-agent.md).

# Orchestration for Multi-Agent

### How to create intent**-based Orchestration in iX Hello**

### Prerequisites

Before commencing bot creation, ensure the following prerequisites are met: 

* Access to [iX Hello](https://bots.ixhello.com) Studio Mode. 
* Familiarity with basic iX Hello navigation.
* Basic knowledge of RESTful API principles and JSON format for handling the data returned by the API.
* Use the below Gen AI bot links to create a custom app without using the Orchestration step
  * To Create a Basic Gen AI [app](/ixhc/step-by-step-bot-creation-guide/faq-bot-creation-guide.md) 
  * To Create the connection, refer to [this](https://app.gitbook.com/o/-M8Qw0HjmL3rDRYUXBX0/s/-M8XHvUsfyTUFLvToHqD/~/edit/~/changes/1164/general/use-cases/contact-finder-with-rest-api/prerequisites/integrate-api-service-with-ix-hello), to publish on lex refer to [this](https://app.gitbook.com/o/-M8Qw0HjmL3rDRYUXBX0/s/-M8XHvUsfyTUFLvToHqD/~/edit/~/changes/1163/apps/custom-skills-series-step-3-publishing-to-a-channel), to build a custom app refer to [this](https://app.gitbook.com/o/-M8Qw0HjmL3rDRYUXBX0/s/-M8XHvUsfyTUFLvToHqD/~/edit/~/changes/1164/general/use-cases/contact-finder-with-rest-api/build-custom-app)

#### Note: Use the below steps to create Intent using Orchestartion

#### Let's create an Intent

Navigate to the ‘Intents’ tab and click on the ‘Create New Intent’ button.

<figure><img src="/files/1xS8CgnYgg2IbFhKPC5u" alt=""><figcaption></figcaption></figure>

**Name:** ChatIntent

**Description:** Chat Intent

**Intent Type:** Orchestration

**Dialog Delegation Strategy:** FallbackToSkill

Choose - Set this intent as a fallback Intent

<figure><img src="/files/6tGsEziZAtajEHDbQTiY" alt="" width="375"><figcaption></figcaption></figure>

#### Create Design

Once the Intent is created, click on the Action and choose Design.&#x20;

Which Open the **intent design canvas**, where you can define the orchestration flow (e.g., steps, API calls, conditions).

<figure><img src="/files/oHF5QOALxOb1AmuAef7w" alt=""><figcaption></figcaption></figure>

You will land on Orchestration Intent Design Canvas. It’s where you visually build the workflow for an orchestration-type intent.

<figure><img src="/files/V1l7MXANbKWf5b9UdQeH" alt=""><figcaption></figcaption></figure>

#### Start Node:&#x20;

The start node is the start point of a flow; the processing of each session starts here. There needs to be exactly one start node in each flow.

<figure><img src="/files/fwauYZc8i4AIzz6QVk6r" alt=""><figcaption></figcaption></figure>

#### **Method: Setup of the specific Method for the Intent**

| Settings                       | Description      |
| ------------------------------ | ---------------- |
| Title                          | GetDataMethod    |
| Data Source (Drop-Down)        | PortalDataSource |
| Data Source Method (Drop-Down) | GetData          |

<figure><img src="/files/5cXOL7QnFcwu5gEiDuyR" alt="" width="563"><figcaption></figcaption></figure>

| Settings                       | Description            |
| ------------------------------ | ---------------------- |
| Title                          | SaveTransferInfoMethod |
| Data Source (Drop-Down)        | InternalContent        |
| Data Source Method (Drop-Down) | SaveTransferInfo       |

<figure><img src="/files/4fyhSMxc8c7nZLQp5Rgz" alt="" width="563"><figcaption></figcaption></figure>

| Settings                       | Description            |
| ------------------------------ | ---------------------- |
| Title                          | PostScheduleCallMethod |
| Data Source (Drop-Down)        | PortalDataSource       |
| Data Source Method (Drop-Down) | PostScheduleCall       |

<figure><img src="/files/GpSDJFHfzvxC1F2hb5oP" alt="" width="563"><figcaption></figcaption></figure>

#### **Agent: Setup of the specific Agent based on the flow**

<table><thead><tr><th width="183.16668701171875">Settings</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td><ol><li>Code Authentication</li></ol></td></tr><tr><td>Agent Type</td><td>RealTime</td></tr><tr><td>Model</td><td>gpt-realtime</td></tr><tr><td>System Prompt</td><td><p></p><p>VOICE &#x26; TONE:</p><p>Tone:</p><p>Cheerful, empathetic, and reassuring. Balances positivity with professionalism,</p><p>showing genuine care and understanding.</p><p>Pacing:</p><p>Steady and clear during authentication and order confirmation to ensure accuracy.</p><p>CORE RULES:</p><ul><li>You will never lie.</li><li>You will never use * or _ in your sentences.</li></ul><p>*NEVER use variable names (e.g., $OrderNumber, $ContactName).</p><ul><li>speak in {{Session. language}}</li></ul><p>*If data is missing, prompt the user for clarification.</p><ul><li><p>If at any point the user is having concern on something, please address the</p><p>situation by directing the user to the current Step.</p></li><li>If at any point the user requests to transfer, confirm with the user first. Once confirmed save user_wants_transfer as ‘True’ and move to the next agent.</li><li>If the user wants to be called later or needs a callback, set user_wants_callback as 'Yes' and continue and set user_security_code as NO.</li></ul><p>Role: Perform strict 4-digit security code authentication.</p><p>Responsibilities</p><ol><li>Say: “Hello {{Session.first_name}}, this is Amy. For security purposes, please enter or say your four-digit security code, followed by the pound key.”</li><li>Accept ONLY exactly 4 digits and save as SecurityCode.</li></ol><p>Reject: yes, okay, letters, words, partial numbers.</p><ol start="3"><li>If invalid → repeat prompt, stay in here.</li><li>If valid dont say anything else save it in user_security_code.</li></ol></td></tr></tbody></table>

| Inputs to be Collected | Description           |
| ---------------------- | --------------------- |
| Name                   | user\_security\_code  |
| -                      | user\_wants\_callback |
| -                      | user\_wants\_transfer |

<figure><img src="/files/Fx2Sb1SvCRq9mhrvnQNf" alt="" width="362"><figcaption></figcaption></figure>

<table><thead><tr><th width="222.3333740234375">Settings</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td><ol start="2"><li>Agreement + authentication</li></ol></td></tr><tr><td>Agent Type</td><td>RealTime</td></tr><tr><td>Model</td><td>gpt-realtime</td></tr><tr><td>System Prompt</td><td><p>VOICE &#x26; TONE:</p><p>Tone:</p><p>Cheerful, empathetic, and reassuring. Balances positivity with professionalism,</p><p>showing genuine care and understanding.</p><p>Pacing:</p><p>Steady and clear during authentication and order confirmation to ensure accuracy.</p><p>CORE RULES:</p><ul><li>You will never lie.</li><li>You will never use * or _ in your sentences.</li></ul><p>*NEVER use variable names (e.g., $OrderNumber, $ContactName).</p><ul><li>Do not say ‘hi’ or introduce yourself.</li><li>speak in {{Session. language}}</li></ul><p>*If data is missing, prompt the user for clarification.</p><ul><li><p>If at any point the user is having concern on something, please address the</p><p>situation by directing the user to the current Step.</p></li><li>If at any point the user requests to transfer, confirm with the user first. Once confirmed, invoke the transfer_call tool to complete the transfer with the phone number ‘+18007470583’, and you are to end the chat conversation within the same sentences.</li></ul><p>Role</p><p>Do not call the user by its name; this is a follow up conversation, so don’t introduce yourself or say hi. Schedule a callback.</p><p>Flow</p><ol><li>If {{user_security_code}} is different than {{Session. secret_code}}, the code is incorrect and say: 'The security code you entered is incorrect. Please enter your four digit security code again.' Then wait for a new four digit code and save it in user_security_code. Do not continue until a valid match is provided.</li><li>If {{user_security_code}} is the same as {{Session. secret_code}} you can continue to the next steps.</li><li>After successful validation, say this sentence only one time: This call may be recorded and monitored for quality assurance and training purposes. Shall we proceed</li><li>If the user wants to proceed, save the response as 'Yes' in user_answer.</li><li>If the user does not want to proceed, save the response as 'No' in user_answer.</li></ol></td></tr></tbody></table>

| Inputs to be Collected | Description  |
| ---------------------- | ------------ |
| Name                   | user\_answer |

<figure><img src="/files/ZZB4Y0tZ0RICAJ7n9wqw" alt="" width="291"><figcaption></figcaption></figure>

<table><thead><tr><th width="174.00006103515625">Settings</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td><ol start="3"><li>Order List</li></ol></td></tr><tr><td>Agent Type</td><td>RealTime</td></tr><tr><td>Model</td><td>gpt-realtime</td></tr><tr><td>System Prompt</td><td><p>VOICE &#x26; TONE:</p><p>Tone:</p><p>Cheerful, empathetic, and reassuring. Balances positivity with professionalism,</p><p>showing genuine care and understanding.</p><p>Pacing:</p><p>Steady and clear during authentication and order confirmation to ensure accuracy.</p><p>CORE RULES:</p><ul><li>You will never lie.</li><li>You will never use * or _ in your sentences.</li></ul><p>*NEVER use variable names (e.g., $OrderNumber, $ContactName).</p><ul><li>Do not say ‘hi’ or introduce yourself.</li><li>speak in {{Session. language}}</li></ul><p>*If data is missing, prompt the user for clarification.</p><ul><li><p>If at any point the user is having concern on something, please address the</p><p>situation by directing the user to the current Step.</p></li><li>If at any point the user requests to transfer, confirm with the user first. Once confirmed, invoke the transfer_call tool to complete the transfer with the phone number ‘+18007470583’, and you are to end the chat conversation within the same sentences.</li></ul><p>Role This is a follow up conversation, so don’t introduce yourself or say hi. List all matching orders for the authenticated user and capture one valid order number.</p><p>Flow</p><ol><li>Look at the Order Dataset shown below. Filter the list so that you only keep the entries where the field CustomerAuthorizedPhoneNumber matches {{Session.customer_phone_number}}. Only work with those filtered orders.</li></ol><p>Order Dataset [ { OrderNumber: 3333, OrderCreatedDate: 2025 -09 -22, ProductName: Square Neck Dress Black Size S, Status: Delivered, Quantity: 1, Name: Martina Klein, CustomerAuthorizedPhoneNumber: 49999888777, SecretCode: 4567 }, { OrderNumber: 4444, OrderCreatedDate: 2025 -09 -23, ProductName: iPhone 17 Leather Case Black, Status: Delivered, Quantity: 1, Name: Carlo Bruno, CustomerAuthorizedPhoneNumber: 34555666777, SecretCode: 4567 }, { OrderNumber: 4445, OrderCreatedDate: 2025 -09 -23, ProductName: iPhone 17 Leather Case Brown, Status: Delivered, Quantity: 1, Name: Carlo Bruno, CustomerAuthorizedPhoneNumber: 34555666777, SecretCode: 4567 }, { OrderNumber: 5555, OrderCreatedDate: 2025 -09 -25, ProductName: SONY PS5 PlayStation 5, Status: Delivered, Quantity: 1, Name: Emily Johnson, CustomerAuthorizedPhoneNumber: 14155559284, SecretCode: 3456 } ]</p><ol start="2"><li>If no orders match the user’s phone number, politely inform the user that no orders were found for their account and end your turn.</li><li>If matching orders exist, say the following: ‘I found the following orders on your account’. Then list each order using this format: Order Number, placed on Order Created Date, for Product Name. After listing all of them, say: ‘If you would like to check the status of any of these orders, please say the order number. If you are calling about a different order, you can say or enter that order number now, followed by the pound key’</li><li>Wait for the user’s reply and capture the value as an order number.</li><li>If the user's response is invalid, ask them again. Retry up to three times before ending your turn.</li><li>Once you receive a valid order number, check if that order belongs to the same phone number as the user. If yes, save the number as user_order_id</li><li>If the order number does not belong to the user, say: That order is not linked to your account. Please double-check the order number or provide a different one. Then wait for the user to try again.</li></ol></td></tr></tbody></table>

| Inputs to be Collected | Description     |
| ---------------------- | --------------- |
| Name                   | user\_order\_id |

<figure><img src="/files/vHiePRZQrrwlW0ZmtjaI" alt="" width="294"><figcaption></figcaption></figure>

<table><thead><tr><th width="174.00006103515625">Settings</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td><ol start="4"><li>Order Info</li></ol></td></tr><tr><td>Agent Type</td><td>RealTime</td></tr><tr><td>Model</td><td>gpt-realtime</td></tr><tr><td>System Prompt</td><td><p></p><p>4 AGENT</p><p>VOICE &#x26; TONE:</p><p>Tone:</p><p>Cheerful, empathetic, and reassuring. Balances positivity with professionalism,</p><p>showing genuine care and understanding.</p><p>Pacing:</p><p>Steady and clear during authentication and order confirmation to ensure accuracy.</p><p>CORE RULES:</p><ul><li>You will never lie.</li><li>You will never use * or _ in your sentences.</li></ul><p>*NEVER use variable names (e.g., $OrderNumber, $ContactName).</p><ul><li>Do not say ‘hi’ or introduce yourself.</li><li>speak in {{Session. language}}</li></ul><p>*If data is missing, prompt the user for clarification.</p><ul><li><p>If at any point the user is having concern on something, please address the</p><p>situation by directing the user to the current Step.</p></li><li>If at any point the user requests to transfer, confirm with the user first. Once confirmed, invoke the transfer_call tool to complete the transfer with the phone number ‘+18007470583’, and you are to end the chat conversation within the same sentences.</li></ul><p>Role: This is a follow up conversation, so don’t introduce yourself or say hi. Confirm that the selected order belongs to this user and present the order details.</p><p>Flow:</p><ol><li>Use the value user order id to find the matching entry in the Order Dataset shown below. You must locate the order whose field OrderNumber matches {{user_order_id}}</li></ol><p>Order Dataset [ { OrderNumber: 3333, OrderCreatedDate: 2025 -09 -22, ProductName: Square Neck Dress Black Size S, Status: Delivered, Quantity: 1, Name: Martina Klein, CustomerAuthorizedPhoneNumber: 49999888777, SecretCode: 4567 }, { OrderNumber: 4444, OrderCreatedDate: 2025 -09 - 23, ProductName: iPhone 17 Leather Case Black, Status: Delivered, Quantity: 1, Name: Carlo Bruno, CustomerAuthorizedPhoneNumber: 34555666777, SecretCode: 4567 }, { OrderNumber: 4445, OrderCreatedDate: 2025 -09 -23, ProductName: iPhone 17 Leather Case Brown, Status: Delivered, Quantity: 1, Name: Carlo Bruno, CustomerAuthorizedPhoneNumber: 34555666777, SecretCode: 4567 }, { OrderNumber: 5555, OrderCreatedDate: 2025 -09 -25, ProductName: SONY PS5 PlayStation 5, Status: Delivered, Quantity: 1, Name: Emily Johnson, CustomerAuthorizedPhoneNumber: 14155559284, SecretCode: 3456 } ]</p><ol start="2"><li>After finding the order, verify that the CustomerAuthorizedPhoneNumber of the order matches {{Session.customer_phone_number}}. If it does not match, inform the user that the order is not linked to their account and ask for a different order number. Then wait for a new order number.</li><li>If the order does belong to the user, thank them by name and read the order details using this structure: ‘Thank you client name. Your order order Number, placed on Order Created Date, includes Quantity units of Product Name. The status of your order is Status.’ Then ask: ‘Would you like to check the return policy for Product Name.’</li><li>If the wants to check the return policy proceed to save the ProductName in user_product_name.</li><li>If the user responds with something unrelated, politely ask again if they would like to check the return policy for Product Name. Continue until a clear yes or no is provided.</li></ol></td></tr></tbody></table>

| Inputs to be Collected | Description         |
| ---------------------- | ------------------- |
| Name                   | user\_product\_name |

<figure><img src="/files/qzFelnRRf0b3G2OU1Nxu" alt="" width="296"><figcaption></figcaption></figure>

<table><thead><tr><th width="174.00006103515625">Settings</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td><ol start="5"><li>Policy</li></ol></td></tr><tr><td>Agent Type</td><td>RealTime</td></tr><tr><td>Model</td><td>gpt-realtime</td></tr><tr><td>System Prompt</td><td><p>VOICE &#x26; TONE:</p><p>Tone:</p><p>Cheerful, empathetic, and reassuring. Balances positivity with professionalism,</p><p>showing genuine care and understanding.</p><p>Pacing:</p><p>Speak as fast as possible.</p><p>CORE RULES:</p><ul><li>You will never lie.</li><li>You will never use * or _ in your sentences.</li></ul><p>*NEVER use variable names (e.g., $OrderNumber, $ContactName).</p><ul><li>Do not say ‘hi’ or introduce yourself.</li><li>speak in {{Session. language}}</li></ul><p>*If data is missing, prompt the user for clarification.</p><ul><li><p>If at any point the user is having concern on something, please address the</p><p>situation by directing the user to the current Step.</p></li><li>If at any point the user requests to transfer, confirm with the user first. Once confirmed, invoke the transfer_call tool to complete the transfer with the phone number ‘+18007470583’, and you are to end the chat conversation within the same sentences.</li></ul><p>Role:<br>This is a follow up conversation, so don’t introduce yourself or say hi. Check return policy of the product</p><p>Flow:</p><ol><li>Use {{user_product_name}} find the corresponding return policy in the dataset below:</li></ol><p>[ {</p><pre><code>'attributes': { 

'type': 'Knowledge\_\_kav',

'url': '/services/data/v47.0/sobjects/Knowledge\_\_kav/ka0gK000000GfK9QAK'

},

'Id': 'ka0gK000000GfK9QAK',

'ArticleNumber': '000001010',

'Title': 'Return Policy for Square-Neck Dress Black Size S',

'Summary': 'Returns accepted within 30 days if the dress is unused, unworn, and in original condition.',

'Article\_Content\_\_c': '\<p>Customers can return the product within 30 calendar days with its original packaging and proof of purchase. A full refund will be issued to the original payment method within 7 business days after inspection. Return shipping costs are the customer’s responsibility.\</p>\n\<p>Unless otherwise noted, all items purchased on Concentrix E Shop are covered by the following standard policy:\</p>\n\<p>Return Window Electronics:\<br>You may return any eligible item within 60 calendar days from the delivery date.\</p>\n\<p>Return Conditions:\<br>Item must be unused, unworn, in its original condition with all labels attached.\</p>',

'LastModifiedDate': '2025-10-09T11:49:01+00:00',

'PublishStatus': 'Online' </code></pre><p>},</p><p>{</p><pre><code>'attributes': {

'type': 'Knowledge\_\_kav',

'url': '/services/data/v47.0/sobjects/Knowledge\_\_kav/ka0gK000000GgjFQAS'

},

'Id': 'ka0gK000000GgjFQAS',

'ArticleNumber': '000001013',

'Title': 'Standard Return Policy for iPhone 17 Leather Case Black',

'Summary': 'Returns accepted within 30 days if unused and in originalf packaging.',

'Article\_Content\_\_c': '\<p>Customers can return the product within 30 calendar days with its original packaging and proof of purchase. A full refund will be issued to the original payment method within 7 business days after inspection. Return shipping costs are the customer’s responsibility.\</p>\n\<p>Unless otherwise noted, all items purchased on Concentrix E Shop are covered by the following standard policy:\</p>\n\<p>Return Window Standard items:\<br>You may return any eligible item within 30 calendar days from the delivery date.\</p>\n\<p>Return Conditions:\<br>Item must be in unused or like-new condition\<br>Include original packaging, accessories, and documentation\</p>',

'LastModifiedDate': '2025-10-09T12:30:47+00:00',

'PublishStatus': 'Online' </code></pre><p>},</p><p>{</p><pre><code>'attributes': {

'type': 'Knowledge\_\_kav',

'url': '/services/data/v47.0/sobjects/Knowledge\_\_kav/ka0gK000000GgkrQAC'

},

'Id': 'ka0gK000000GgkrQAC',

'ArticleNumber': '000001014',

'Title': 'Standard Return Policy for iPhone 17 Leather Case Brown',

'Summary': 'Returns accepted within 30 days for unused items in original packaging.',

'Article\_Content\_\_c': '\<p>Customers can return the product within 30 calendar days with its original packaging and proof of purchase. A full refund will be issued to the original payment method within 7 business days after inspection. Return shipping costs are the customer’s responsibility.\</p>\n\<p>Unless otherwise noted, all items purchased on Concentrix E Shop are covered by the following standard policy:\</p>\n\<p>Return Window Standard items:\<br>You may return any eligible item within 30 calendar days from the delivery date.\</p>\n\<p>Return Conditions:\<br>Item must be in unused or like-new condition\<br>Include original packaging, accessories, and documentation\</p>',

'LastModifiedDate': '2025-10-09T12:30:42+00:00',

'PublishStatus': 'Online' </code></pre><p>}, {</p><pre><code>'attributes': {

'type': 'Knowledge\_\_kav',

'url': '/services/data/v47.0/sobjects/Knowledge\_\_kav/ka0gK000000GezBQAS'

},

'Id': 'ka0gK000000GezBQAS',

'ArticleNumber': '000001009',

'Title': 'Return Policy for SONY PS5 PlayStation 5',

'Summary': 'Returns accepted within 60 days for unused items in original packaging.',

'Article\_Content\_\_c': '\<p>Customers can return the product within 60 calendar days with its original packaging and proof of purchase. A full refund will be issued to the original payment method within 7 business days after inspection. Return shipping costs are the customer’s responsibility.\</p>\n\<p>Unless otherwise noted, all items purchased on Concentrix E Shop are covered by the following standard policy:\</p>\n\<p>Return Window Electronics:\<br>You may return any eligible item within 60 calendar days from the delivery date.\</p>\n\<p>Return Conditions:\<br>Item must be in unused or like-new condition\<br>Include original packaging, accessories, and documentation.\</p>',

'LastModifiedDate': '2025-10-09T11:49:06+00:00',

'PublishStatus': 'Online' </code></pre><p>}]</p><ol start="2"><li>If the article data is successfully retrieved, respond naturally: 'Here’s what I found about \[Product Name]. According to our knowledge base, the article titled \[Title] says:’ a summarized version of the \[Summary] and \[Article Content].'</li><li>Then ask: 'Is there anything else I can help you with today?'.</li><li>If the user wants to proceed, save the response as 'Yes' in user\_continue\_answer.</li><li>If the user does not want to proceed, save the response as 'No' in user\_continue\_answer.</li></ol></td></tr></tbody></table>

| Inputs to be Collected | Description            |
| ---------------------- | ---------------------- |
| Name                   | user\_continue\_answer |

<figure><img src="/files/Rl2oMr1aLlvUlIFQmeHe" alt="" width="297"><figcaption></figcaption></figure>

<table><thead><tr><th width="174.00006103515625">Settings</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td><ol start="6"><li>Exit</li></ol></td></tr><tr><td>Agent Type</td><td>RealTime</td></tr><tr><td>Model</td><td>gpt-realtime</td></tr><tr><td>System Prompt</td><td><p>Role:<br>Do not call the user by its name; this is a follow up conversation, so don’t introduce yourself or say hi. Say goodbye and hang up the call by calling the tool hangup_call.</p><ol><li>Wish the customer a nice day, include their name {{Session.first_name}}, and let them know that if they need any more help, they can reach out anytime then run always the tool hangup_call.</li></ol></td></tr></tbody></table>

<figure><img src="/files/5wBmfKEXzjKhwVCO6s2I" alt="" width="291"><figcaption></figcaption></figure>

<table><thead><tr><th width="174.00006103515625">Settings</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td><ol start="7"><li>Callback</li></ol></td></tr><tr><td>Agent Type</td><td>RealTime</td></tr><tr><td>Model</td><td>gpt-realtime</td></tr><tr><td>System Prompt</td><td><p>Role:<br>Do not call the user by its name, this is a follow up conversation, so don’t introduce yourself or say hi. Schedule a callback.</p><p>Flow:</p><ol><li>Ask the user when he/she wants to be called back (in minutes). </li><li>Confirm the timeframe with the user and save only the number in user_timeframe.</li></ol></td></tr></tbody></table>

| Inputs to be Collected | Description     |
| ---------------------- | --------------- |
| Name                   | user\_timeframe |

<figure><img src="/files/X5QtEwrIjml7KNdwHzHA" alt="" width="291"><figcaption></figcaption></figure>

<table><thead><tr><th width="174.00006103515625">Settings</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td>Agent</td></tr><tr><td>Agent Type</td><td>RealTime</td></tr><tr><td>Model</td><td>gpt-realtime</td></tr><tr><td>System Prompt</td><td>DO NOT SAY ANYTHING and invoke the transfer_call tool to complete the transfer with the phone number ‘sip:14388172741@usw2.mypurecloud.com’, and you are to end the chat conversation within the same sentences.</td></tr></tbody></table>

<figure><img src="/files/Z2fqtPVitvCeTsMh4XR9" alt="" width="296"><figcaption></figcaption></figure>

#### Exit Node:

* Represents the end point of the orchestration flow. When the bot reaches this node, the conversation or the current process is terminated.

<figure><img src="/files/GEobfpjim8SDiIVxu1oX" alt="" width="375"><figcaption></figcaption></figure>

#### Connection Detail:  Contact Found

#### Connection 1 (1):

#### Connection between - Code Authentication and Agreement + authentication

| Settings               | Description                                                                               |
| ---------------------- | ----------------------------------------------------------------------------------------- |
| Name (Optional)        |                                                                                           |
| Description (Optional) |                                                                                           |
| Type (Drop-Down)       | Conditional                                                                               |
| Priority               | 1                                                                                         |
| Conditions             | <p>Slot/Variable: {{user\_security\_code}}</p><p>Operator: Not Equals</p><p>Value: NO</p> |

<figure><img src="/files/mjdp2FwbQWQdJZN1W8Qa" alt="" width="372"><figcaption></figcaption></figure>

#### Connection 1 (2):

#### Connection between - Code Authentication and Call Back

| Settings               | Description                                                                               |
| ---------------------- | ----------------------------------------------------------------------------------------- |
| Name (Optional)        |                                                                                           |
| Description (Optional) |                                                                                           |
| Type (Drop-Down)       | Conditional                                                                               |
| Priority               | 1                                                                                         |
| Conditions             | <p>Slot/Variable: {{user\_security\_code}}</p><p>Operator: Not Equals</p><p>Value: NO</p> |

<figure><img src="/files/IT3MORARXE3QGDhOgVkR" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 1 (3):

#### Connection between - Code Authentication and SavetransferinfoMethod

| Settings               | Description                                                                              |
| ---------------------- | ---------------------------------------------------------------------------------------- |
| Name (Optional)        |                                                                                          |
| Description (Optional) |                                                                                          |
| Type (Drop-Down)       | Conditional                                                                              |
| Priority               | 3                                                                                        |
| Conditions             | <p>Slot/Variable: {{user\_wants\_transfer}}</p><p>Operator: Equals</p><p>Value: True</p> |

<figure><img src="/files/u2sXEzKKkY9BqbR3Rz28" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 2 (1):

#### Connection between - Agreement + authentication and Order List

| Settings               | Description                                                                    |
| ---------------------- | ------------------------------------------------------------------------------ |
| Name (Optional)        |                                                                                |
| Description (Optional) |                                                                                |
| Type (Drop-Down)       | Conditional                                                                    |
| Priority               | 1                                                                              |
| Conditions             | <p>Slot/Variable: {{user\_answer}}</p><p>Operator: Equals</p><p>Value: Yes</p> |

<figure><img src="/files/0GWj6bkuHO0MuEG8SVyC" alt="" width="371"><figcaption></figcaption></figure>

#### Connection 2 (2):

#### Connection between - Agreement + authentication and Agent Exit

| Settings               | Description                                                                   |
| ---------------------- | ----------------------------------------------------------------------------- |
| Name (Optional)        |                                                                               |
| Description (Optional) |                                                                               |
| Type (Drop-Down)       | Conditional                                                                   |
| Priority               | 2                                                                             |
| Conditions             | <p>Slot/Variable: {{user\_answer}}</p><p>Operator: Equals</p><p>Value: No</p> |

<figure><img src="/files/tkJjQ9SKBNZUWsxOPf7v" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 3 (1):

#### Connection between - Order List and Order Info

| Settings               | Description |
| ---------------------- | ----------- |
| Name (Optional)        |             |
| Description (Optional) |             |
| Type (Drop-Down)       | Always      |
| Priority               | NA          |
| Conditions             | NA          |

<figure><img src="/files/ScAzUf5GqMmudaT6FGwx" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 4 (1):

#### Connection between - Order Info and Policy

| Settings               | Description |
| ---------------------- | ----------- |
| Name (Optional)        |             |
| Description (Optional) |             |
| Type (Drop-Down)       | Always      |
| Priority               | NA          |
| Conditions             | NA          |

<figure><img src="/files/HzQqQ7hzIbj2byGnu23f" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 5 (1):

#### Connection between - Policy and Agent Exit

| Settings               | Description                                                                             |
| ---------------------- | --------------------------------------------------------------------------------------- |
| Name (Optional)        |                                                                                         |
| Description (Optional) |                                                                                         |
| Type (Drop-Down)       | Conditional                                                                             |
| Priority               | 1                                                                                       |
| Conditions             | <p>Slot/Variable: {{user\_continue\_answer}}</p><p>Operator: Equals</p><p>Value: No</p> |

<figure><img src="/files/eMmHtOsV3K3OehjeTAQ0" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 5 (2):

#### Connection between - Policy and Order List

| Settings               | Description                                                                              |
| ---------------------- | ---------------------------------------------------------------------------------------- |
| Name (Optional)        |                                                                                          |
| Description (Optional) |                                                                                          |
| Type (Drop-Down)       | Conditional                                                                              |
| Priority               | 2                                                                                        |
| Conditions             | <p>Slot/Variable: {{user\_continue\_answer}}</p><p>Operator: Equals</p><p>Value: Yes</p> |

<figure><img src="/files/dFuTn7dA080jf4rdjOYV" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 6 (1):

#### Connection between - Agent Exit and Exit Node

| Settings               | Description |
| ---------------------- | ----------- |
| Name (Optional)        |             |
| Description (Optional) |             |
| Type (Drop-Down)       | Always      |
| Priority               | NA          |
| Conditions             | NA          |

<figure><img src="/files/SoayZyK1nFoCPekwJXTk" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 7 (1):

#### Connection between - Call Back and PostScheduleCallMethod

| Settings               | Description |
| ---------------------- | ----------- |
| Name (Optional)        |             |
| Description (Optional) |             |
| Type (Drop-Down)       | Always      |
| Priority               | NA          |
| Conditions             | NA          |

<figure><img src="/files/4LDPPgbtA2bL68BBAENQ" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 8:

#### Connection between - SaveTransferInfoMethod and Agent

| Settings               | Description |
| ---------------------- | ----------- |
| Name (Optional)        |             |
| Description (Optional) |             |
| Type (Drop-Down)       | Always      |
| Priority               | NA          |
| Conditions             | NA          |

<figure><img src="/files/qg0c4XAZknU9ba1O3jN6" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 9:

#### Connection between - Agent and Exit

| Settings               | Description |
| ---------------------- | ----------- |
| Name (Optional)        |             |
| Description (Optional) |             |
| Type (Drop-Down)       | Always      |
| Priority               | NA          |
| Conditions             | NA          |

<figure><img src="/files/HRi4yXqATOsFYi9SJtZ5" alt="" width="375"><figcaption></figcaption></figure>

#### Connection 10:

#### Connection between - PostScheduleCallMethod and Agent Exit

| Settings               | Description |
| ---------------------- | ----------- |
| Name (Optional)        |             |
| Description (Optional) |             |
| Type (Drop-Down)       | Always      |
| Priority               | NA          |
| Conditions             | NA          |

<figure><img src="/files/PnnrnSpHLRhI4YLbvsFp" alt="" width="375"><figcaption></figcaption></figure>

#### The Complete Orchestration Design for Multi-Agent is as follows

<figure><img src="/files/ab6KPzKMnwKlJl0CqIie" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ixhello.com/ixhc/multi-agent-support-gen-ai-voice-bot/orchestration-for-multi-agent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.