Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

Document Title: Orbita Appointment Scheduling Solution

Solution Version: V 1.0.0

Creation Date:

Author:

Status
colourBlue
titleORBITA

Table of Content Zone
minLevel1
maxLevel7
Table of Contents
minLevel1
maxLevel7

Prerequisites

  1. The users should use their own office 365 account credentials to book the appointments.
    https://support.microsoft.com/en-gb/account-billing/how-to-create-a-new-microsoft-account-a84675c3-3e9e-17cf-2911-3d56b15c0aaf

...

  1. Login to Experience Manager

  2. Navigate to your project > Project side navigation menu > Create > Agents > Package

  3. Click the Install button against the Appointment Scheduling solution.

    Image Added

Dashboards

How to access dashboards?

...

Tip

The Appointment Scheduling solution data is captured in the data-<environment>-backend.userinfoscheduleappointmentuserinfo index pattern.

Solution Customization

...

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:

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

  2. Select the Flow Studio “Schedule Appt Intro Flow” and navigate to “Welcome Prompt” that contains the text and edit it.

...

List of appointment types included:

To add an appointment type to the existing list of appointment types, please get in touch with your Customer Success representative.

Prompts:

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

  2. Select the Flow Studio “Schedule Appt Book Flow”

  3. The Prompts can be configured in the respective nodes as per the below table.

...

Prompt

Node

Screenshot

Prompt before appointment type buttons

 

Appointmenttype

 

Image Added

Prompt before calendar directive

appointmentDetails

Image Added

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

firstname

lastname

dob

phonenumber

email

contacttype

Image AddedImage AddedImage AddedImage AddedImage AddedImage Added

Appointment confirmation say node:

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

  2. Select the Flow Studio “Schedule Appt Book Flow” and navigate to the Say node that contains the appointment confirmation message and edit it.

...

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

...

Length of each appointment type:

 To change the length of the existing list of appointment types, please get in touch with your Customer Success representative.

How to update the branding of the chatbot

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.