Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This glossary includes the most commonly used x-hoppers terms and features and their descriptions.

Created: November 2024

Permalink:

Introduction

Voice Bots is a poweful tool that allows automated responses and routes customers' and your team’s queries via bot assistance.

  • Generative AI let you create highly interactive and intelligent Voice Bots without any coding expertise. By providing specific instructions, the AI model generates dynamic, context-aware responses that enhance user engagement. You can also create easily incorporate custom functions to interact with third-party servers, allowing your bot to perform actions like fetching real-time data, updating records, or triggering external processes during a conversation.

  • Webhooks and AWS SQS allow you to take full control over your voice bot sessions. These options are ideal if your voice bot requires custom handling of conversations; you can build a service to analyze events and generate responses.

  • Dialogflow CX is a versatile AI platform, which is great at handling natural language and managing conversations, even when they get a bit complicated. It is good for automating customer interactions, handling queries, and passing customers to agents when needed.

  • OpenAI Assistant connects your Voice Bot to OpenAI’s language models, which lets to handle complex conversations and provide natural responses to user queries. With OpenAI’s advanced AI capabilities, your Voice Bot can understand context, manage dialogues, and deliver personalized interactions.

Voice Bot Creation

It is possible to set up to ____ Voice Bots per organization.

To create a Voice Bot, proceed with the following steps:

  • Navigate to WMS -> PBX -> Integrations -> Cloud integrations -> Voice Bots

    wms-voice-bots.png

  • Click Add New Voicebot:

    add-new-voicebot.png

  • Enter Voice Bot name

  • Enter First message (optional)

  • Select the integration type for processing events:

    • Generative AI

    • Webhook

    • AWS SQS

    • Dialogflow CX

    • OpenAI Assistant

  • Fill out the necessary fields depending on the selected integration type (see instructions below)

voice-bot-name-message.png
  • Configure Advanced Configuration:

    • Interruption Detection: if enabled, customers can interrupt the bot and the system will stop the playback of the voice bot's response. By default, the option is disabled.

    • Silence Timeout: set the timeout before a call is automatically ended due to inactivity and the action (hangup or transfer) that should be performed when the call ends.

    • Maximum Duration: the maximum duration of a call in seconds and action (hangup or transfer) that should be performed when the call ends.

      voice-bot-additional-configuration.png
  • Click Add to save your Voice Bot

Generative AI

When configuring Generative AI as the integration type, you need to create a clear and precise prompt with instructions for AI agents, which directly impacts Voice Bot performance and reliability. Prompt engineering is an iterative process, so based on user feedback, you can refine your prompts for even better Voice Bot efficiency.

You can divide your system prompts into the distinct sections, each focusing on a specific element of the AI agent's behavior. For example:

  1. Identity: define who the AI agent is, outline its persona and role to set the context for interactions.

  2. Style: establish guidelines for the agent's communication style, including tone, language, and formality.

  3. Response Guidelines: specify preferences for the response format, including any limitations or requirements in terms of the response structure.

  4. Task and Goals: indicate the objectives the agent should achieve and outline the steps it should follow.

generative-ai-voice-bot.png

Webhook

Specify the following fields, when configuring Webhook as the integration type:

  1. Target: enter the URL that the Webhook will use to send POST requests with the event payload.

  2. Secret: the secret ensures that only requests from Wildix system are accepted, preventing unauthorized access or potential security breaches. The secret key is included in the headers of each POST request sent by the Webhook. Your server should validate this key to ensure the request is legitimate before processing the event data

voice-bot-webhook.jpg

Important: The endpoint should be publicly accessible with a valid HTTPS certificate, accept HTTP POST requests with JSON payloads, respond with codes from 200 to 299 as quickly as possible, and handle multiple identical calls in case of retries due to network or server failures (up to 3 times).

AWS SQS

If you configure AWS SQS as integration type, you need to provide the following details to establish the connection with your AWS SQS queue:

  • Target: enter the URL of your SQS queue. This is where the events are sent, for example, https://sqs.amazonaws.com/11111/wildix-events-queue

  • Key: enter your AWS Access Key ID. It is used to sign the request that x-hoppers sends to AWS SQS.

  • Secret: enter your AWS Secret Access Key, which is paired with your AWS Key to sign the requests securely.

aws-sqs-voice-bot.png

Dialogflow CX

If you configure Dialogflow CX as the integration type, you need to fill out the following fields to establish the connection between x-hoppers and your Dialogflow CX agent:

  • Private Key: click Upload and upload the private key file associated with your Google Cloud service account

  • Location: fill out the region where your Dialogflow CX agent is deployed (typically it is a region-specific identifier, for example, europe-west1, us-central1)

  • Language: indicate the language that your Dialogflow CX agent will use to understand and respond to user inputs. Make sure the language code matches the languages supported by your Dialogflow CX agent, e.g.:en for English

  • Agent ID: provide the unique identifier of your Dialogflow CX agent, links your Voice Bot to the specific Dialogflow CX agent that you’ve configured in Google Cloud.

voice-bot-dialogflowcx.jpg

OpenAI Assistant

If you configure OpenAI Assistant as integration type, you need to fill out the following fields to enable the connection between x-hoppers and OpenAI's API:

  1. API Key: enter the unique identifier that allows to grant access to the OpenAI API, which lets to send requests and receive responses from the Assistant

  2. Assistant ID: fill out the unique identifier of a specific OpenAI Assistant you created.

openaiassistant-voice-bot.jpg

Add Tools

Manage Voice Bots

The Voice Bots that you have created are displayed in WMS -> PBX -> Integrations -> Cloud integrations -> Voice Bots section. You can see the Voice Bot name, Bot ID, and Integration type.

voice-bots-lists.jpg

Edit a Voice Bot

  1. To edit a Voice Bot, click on the Edit (pencil) icon:

    voice-bot-edit.png

  2. Make the necessary changes and click Save:

save-edited-voice-bot.png

Delete a Voice Bot

  1. To delete a Voice Bot, click on the Delete icon:

    delete-voice-bot.png
  2. On the screen that pops up, type the word “delete” and click Delete:

confirm-voice-bot-deletion.png

Dialplan Configuration

Language. -

Traces

Bot application

  • No labels