...

Rajkiran Alla (Deactivated) I added notes directly into this page on the areas that can be edited within the solution experience

Warning message: should not add new nodes but can modify the say text in the node

Areas that can be updated:

1. Non-technical users can update:

2. Conversational Updates

   1. “Welcome” Say node

   2. list of appointment types included

   3. prompt before appointment type buttons

   4. prompt before calendar directive

   5. prompts before patient information collection (first name, last name, DOB, phone number, email, preferred contact type)

   6. appointment confirmation say node

3. buttons for appointment types

4. length of each appointment type

5. Integration w/ Microsoft calendar

   1. which providers are available for scheduling

   2. business hours for scheduling

Conversational Updates:

Welcome Say Node:

...

Prompt	Node	Screenshot
Prompt before appointment type buttons	Appointmenttype	Image RemovedImage Added
Prompt before calendar directive	appointmentDetails	Image RemovedImage Added
Prompts before patient information collection (first name, last name, DOB, phone number, email, preferred contact type)	firstname lastname dob phonenumber email contacttypeImage RemovedImage RemovedImage RemovedImage RemovedImage RemovedImage Removed	Image AddedImage AddedImage AddedImage AddedImage AddedImage Added

Appointment confirmation say node:

...

Buttons for appointment types: 

1. Navigate to the Project side navigation menu > Create > Agents > Flow studio.

2. Select the Flow Studio “Schedule Appt Book Flow” and navigate to “appointmenttype” choose many control and open it. Double click on the node to open.

3. Navigate to “Choices” tab and change the values under the “Text” field to change the button text

...

You can customize the chatbot appearance using CSS and JS. For more information on customizing the appearances of your chatbot, refer https://orbita.atlassian.net/wiki/spaces/OCS/pages/1633681419/3.9.1+Creating+Your+Chatbot#Customizing-your-chatbot

Integrations

Microsoft Graph API

We need verbiage here that mentions that EHR integrations would require custom development and could have associated implementation costs dependent on ideal solution for integration per client.

Video Link

Coming soon