Vonage AI Studio
  • Welcome to AI Studio!
  • ✨Platform Updates
  • AI Studio
    • Create a new agent
    • NLU AI Engine - Traditional vs Hybrid
    • Agent Building Features
    • Agent Templates
      • Take Message
      • Updating Details
      • Survey
      • FAQ
      • Package Tracking
      • Caller Identification
      • Customer Service
      • Hotels
      • Appointment Management
    • Tester
    • Editor Mode & Publish
    • Reports
    • Users
    • Knowledge AI
  • Properties
    • Entities
      • System Entities List
      • Best Practices
    • Intents
      • How do we analyze user input?
      • Generate Training Data
      • System Intents
      • Intent Annotation
    • Parameters
    • Contacts
    • Tags
    • Recordings
  • Voice
    • Get started
      • Create your first conversational flow!
      • Triggering Outbound Call API
      • Sending an Outbound Call Request via Postman
      • Integration via SIP for Telephony Agents
    • Nodes
      • Start node
      • Conversation
        • Classification
          • Intent Ambiguity
        • Collect Input
          • Entity Ambiguation
        • Speak
        • Conditions
        • Listen
        • Q&A Node
      • Advanced
        • Reset Counter
        • Counter
        • Set Parameter
        • Custom Code
        • NCCO Node
      • Actions
        • Send Email
        • Call Routing
        • End Call
        • Start Recording
        • Stop Recording
        • Send SMS
      • Integrations
        • Webhook
        • Legacy SalesForce Authentication Node
          • SalesForce Authentication
            • How to create a SalesForce Connected App
        • SalesForce Actions
        • Generative AI
          • Setting up Generative AI Node Integration
          • Migrating from the GenAI node to Knowledge AI
      • Flow Control
        • Context Switch
        • Flows
    • Events
  • WhatsApp
    • Get started
      • Create your first conversational flow!
      • Triggering an outbound WhatsApp virtual agent
    • Nodes
      • Start node
      • Conversation
        • Collect Input
          • Entity Ambiguation
        • Classification
          • Intent Ambiguity
        • Send Message
        • Conditions
      • Advanced
        • Reset Counter
        • Counter
        • Set Parameter
        • Custom Code
      • Actions
        • Send Email
        • End Conversation
        • Send SMS
        • Live Agent Routing
      • Integrations
        • Webhook
        • Legacy SalesForce Authentication Node
          • SalesForce Authentication
            • How to create a SalesForce Connected App
        • SalesForce Actions
        • Generative AI
          • Setting up Generative AI Node Integration
          • Endless FAQs on WhatsApp With Generative AI and AI Studio
      • Flow Control
        • Context Switch
        • Flows
    • Events
  • SMS
    • Get started
      • Create your first conversational flow!
      • Triggering an outbound SMS Virtual Agent
    • Nodes
      • Start node
      • Conversation
        • Classification
          • Intent Ambiguity
        • Conditions
        • Send Message
        • Collect Input
          • Entity Ambiguation
      • Advanced
        • Reset Counter
        • Counter
        • Set Parameter
        • Custom Code
      • Actions
        • Send Email
        • End Conversation
        • Send SMS
        • Live Agent Routing
      • Integrations
        • Webhook
        • Legacy SalesForce Authentication Node
          • SalesForce Authentication
            • How to create a SalesForce Connected App
        • SalesForce Actions
        • Generative AI
          • Setting up Generative AI Node Integration
          • Use Case Example: Gym Business
      • Flow Control
        • Context Switch
        • Flows
    • Events
  • HTTP
    • Get started
      • Create your first conversational flow!
    • Nodes
      • Start node
      • Conversation
        • Classification
          • Intent Ambiguity
        • Collect Input
          • Entity Ambiguation
        • Send Message
        • Conditions
      • Advanced
        • Reset Counter
        • Counter
        • Set Parameter
        • Custom Code
      • Action
        • Send Email
        • Send SMS
        • Live Agent Routing
          • Websockets connections for Live agent Routing
      • Integrations
        • Webhook
        • Legacy SalesForce Authentication Node
          • SalesForce Authentication
            • How to create a SalesForce Connected App
        • SalesForce Actions
        • Generative AI
          • Setting up Generative AI Node Integration
          • Use case Example : Online Shopping
      • Flow Control
        • Context Switch
        • Flows
    • Events
  • API Integration
    • Authentication
    • Insights
  • There's more
    • FAQs
    • Languages Available
Powered by GitBook
On this page
  • Flow Overview
  • Flow Explanation
  • Appointment Management
  • Account Management
  • Appointment Address
  • Talk to someone
  • Appointment Reminders

Was this helpful?

  1. AI Studio
  2. Agent Templates

Appointment Management

Manage user appointments and account changes

PreviousHotelsNextTester

Last updated 1 year ago

Was this helpful?

Use this template to efficiently manage appointment and account-related queries along with escalations to live agents without leaving the conversation in both inbound and outbound scenarios.

To use this template, simply choose it from the templates page when you create a new agent. You can then make changes to customize it based on your business needs.

Flow Overview

Collection and Classification of User Intent

This template covers various actions under the following topics: Appointment management, Account management, Address information, Appointment Reminders and Live Agent Handover.

Additionally, different flows are accessible depending on whether the conversation is Inbound or Outbound.

Flow Explanation

The following flows are available for Inbound Calls:-

Appointment Management

This template is built to handle the following actions: Scheduling, Rescheduling and Cancelling appointments.

These flows first authenticate your user using the verification flow, before asking for further information.

Scheduling Flow: Depending on whether the user is verified or not, the flow is slightly altered.

  • If the user chooses one of the available time slots, the VA logs their request into Salesforce and provides them with a confirmation number. If the user chooses to change any of the collected parameters, the flow then routes them back to the specified part in the flow that handles the parameter they want to edit.

  • If there are no available dates returned, the VA asks the user to retry and re-enter a different service and physician to retry the query to receive available dates.

  • For Unverified users, the VA lets the user know that they need to create an account to schedule an appointment and allows them to create a new account by collecting their name, email address, and phone number preference before logging a request on SalesForce.

Rescheduling Flow: Requires the user to be verified. If they are not verified, the VA falls back into the Verification Flow.

  • The flow begins with a SalesForce check of the user's scheduled appointments. The VA then confirms the appointment time, date and physician with the user and asks them if they want to change the time or the date.

  • The VA then looks for new times/dates as per the user's request and provides a list of available options, allowing the user to pick from them. Once this is done a request is logged into SalesForce and the user receives confirmation of the change.

Cancellation Flow: Requires the user to be verified. If they are notverified, the VA falls back into the Verification Flow.

  • The flow begins with a SalesForce check of the user's scheduled appointments. The VA then confirms the appointment time, date and physician with the user.

  • The VA then confirms with the user if they want to go ahead with the cancellation. If an affirmative response is received from the user, the VA logs the request on SalesForce and confirms the cancellation with the user. Otherwise, the flow moves on to ask the user what else they need help with.

Account Management

This flow consists of the following options: Create an Account, Update Personal Data and Address Management.

Create an Account: This flow interlinks with a few other flows on this template.

  • This flow allows users to create a new account by collecting their name, email address, and phone number preferences before logging a request on SalesForce.

Update Personal Data: This flow requires mandatory verification before use.

  • Post verification, this flow allows your users to update either their phone number or email and logs a request on SalesForce before providing a confirmation to the user of the updated detail.

Address Management: This flow requires mandatory verification before use.

  • Post verification, this flow allows your users to choose from either editing an existing address or adding a new one.

  • Both flows lead to the collection of the update which is then logged onto SalesForce before confirmation with the user.

Appointment Address

This flow only has one subfunction: Appointment Location

This flow requires mandatory verification before execution.

If a booking ID was retrieved, the VA asks the customer to confirm the booking ID. The VA then checks to see if the booking ID provided by the user is the same as the one retrieved from SalesForce, if so it provides the location for the appointment, or else it provides the user with a retry.

If no booking ID was retrieved from SalesForce, the VA lets the user know that there aren't any scheduled appointments and takes the user down the Schedule appointment flow.

Talk to someone

Outbound sessions have access to the following flow:-

Appointment Reminders

If the user confirms, a request is logged in SalesForce and the agent thanks the user before checking to see if the user needs help with anything else (if the user requires more help, the inbound flows are then accessed).

If the user does not confirm the appointment, the VA asks the user if they want to either cancel or reschedule the appointment.

Rescheduling allows for either a date or time change which is logged into SalesForce.

Cancellation prompts the VA to confirm the cancellation from the user. If the user agrees a request is sent to SalesForce and the appointment is cancelled before the VA confirms the cancellation. If the user decides not to cancel, the VA then asks the user if it can help with anything else (if the user requires more help, the inbound flows are then accessed).

The Inbound flow starts with a check of working hours using a node. By default, working hours are set to between Monday to Friday, 8 am to 8:30 pm.

Next using a text-based node, the user is asked what they need help with. This then leads to a sub-flow with all four topics and their subtopics mentioned above

Verification Flow: This flow consists of an email and phone number check which integrates into SalesForce to see if a user is verified. In case of verification failure, the flow is then escalated to a live agent using the .

For Verified users, the Virtual Assistant (VA), first asks the user what service they require (which by default is displayed via ), then asks them to select a Physician (which by default is set up using ).

Next, using a , the VA does a check of available dates.

Depending on the response from Salesforce (which is categorized using a ), the flow then branches out into two smaller flows.

If available dates are returned from SalesForce, the VA then presents these to the user and asks them to make a selection. This is then followed by another that retrieves available times. The available time list is then presented to the user, after which the user has the ability to either, change one of the previously selected parameters (Physician, date or time) or choose one of the available times.

Post verification, a checks to see if the user has scheduled appointments.

Users can also choose to speak to a live agent from the main menu. This is accomplished using the .

You have the ability to test all the different outcomes of the before you set it up using the options in the Tester!

All of these inbound flows also include a to either go back to the main menu or Route to a human.

The flow begins with a check using a to retrieve information about an upcoming appointment. The first message that goes out to the user states the appointment information and asks the user to confirm the appointment.

This flow includes a to Route to a human.

Conditions
Collect Input
Live Agent Routing Node
Reply Buttons
List Messages
SalesForce Action Node
Conditions Node
SalesForce Action Node
SalesForce Action Node
Live Agent Routing Node
Live Agent Routing Node
Context Switch
SalesForce Action Node
Context Switch