AI for Service doc updates#782
Conversation
Update product branch from main
new integration document
There was a problem hiding this comment.
Let's blur IPs, ports, and domain names. Use the Gaussian Blur.
There was a problem hiding this comment.
Consider cropping to the canvas to better display the UI of interest.
There was a problem hiding this comment.
Don't use solid blur like this that too with red color.
| title: Five9 Voice Automation Integration with Voice Gateway via SIP | ||
| sidebarTitle: Five9 Voice Automation with Voice Gateway via SIP | ||
| --- | ||
| This guide explains how to integrate Five9 Voice Automation with Voice Gateway using SIP trunking. With this integration, Five9 routes inbound voice calls to an automation flow for self-service. Based on the conversation outcome, the bot can end the call, transfer the caller to a Five9 skill queue, or transfer the caller directly to a Five9 agent. |
There was a problem hiding this comment.
Always leave an empty blank line after the frontmatter.
|
|
||
| ## Prerequisites | ||
|
|
||
| Confirm that you meet the following prerequisites before configuring the Five9 Voice Automation integration: |
There was a problem hiding this comment.
Use the word Ensure or Make sure. We don't seek confirmation from the reader.
| BotUserSession.put('routeValue', "hangup"); | ||
| BotUserSession.put('routeReason', "Hangup"); | ||
| ``` | ||
| The Automation flow supports the following call outcomes: |
There was a problem hiding this comment.
Mention the objective upfront when we start the topic "Configure the Automation Flow". It situates the reader about why they're following the steps - to what effect.
| Add an **Agent Transfer** node at the end of the automation flow. | ||
|
|
||
| <Note> | ||
| The system transfers Custom SIP headers back to Five9 only when the Automation flow contains an Agent Transfer node. |
There was a problem hiding this comment.
This is the objective why we need an agent transfer node. Remove as a note and club it with the above sentence.
| 1. Configure a SIP endpoint for Five9 Voice Automation integration from **Flows & Channels** > **Channels** > **Voice Gateway** > **SIP Numbers**. | ||
| 2. Select **Product Selection** > **Contact Center AI**. | ||
| 3. Select **Network** > **List of IP Address** and use these Five9 IPs to add to the allowlist: | ||
| `3.224.189.218,35.174.41.205,208.69.29.60,208.69.29.43,208.69.29.44,208.69.29.45,208.69.29.46,162.213.153.62,208.69.29.54,162.213.153.52` |
There was a problem hiding this comment.
Wrap each IP individually inside backticks. The comma separator must not be inside the backticks.
| --- | ||
| This guide explains how to integrate Five9 Voice Automation with Voice Gateway using SIP trunking. With this integration, Five9 routes inbound voice calls to an automation flow for self-service. Based on the conversation outcome, the bot can end the call, transfer the caller to a Five9 skill queue, or transfer the caller directly to a Five9 agent. | ||
|
|
||
| ## Prerequisites |
There was a problem hiding this comment.
Try 1 version of tabulated prereq. I think it'll be good to read + faster to scan. Hence, better structuring and formatting.
There was a problem hiding this comment.
Don't change it now but the folder structure and hence the URL structure of all Agent AI integrations is quite repetitive. For now, let it be. We don't want to deal with any new reorg of content leading to redirects.
minor edits
included a learn more link in RN_11.26.0
ashishguptaiitb
added
the
PendingFixes
3 participants
No description provided.