Assistant before booking

Goal

Understand how a visitor can ask a general clinic question before deciding whether to request care, while retaining a clear path to staff and clinical support.

Audience

• Healthcare organization and practice owners
• Marketing managers
• Front-desk staff and practice managers
• Doctors and clinical staff

Before you begin

No account is required. The walkthrough uses the synthetic Cedar Healthcare demonstration interface and does not enter personal health information, submit a screening, create a lead, or request an appointment.

The assistant response is demonstration content. Practices remain responsible for approving public information, defining escalation policy, and ensuring that clinical questions reach an appropriate licensed clinician.

What you will complete

By the end of the tutorial, you will be able to:

1. Identify the assistant’s suggested-question view.
2. Open the free-text chat mode.
3. Ask a general pre-booking question without sharing personal health information.
4. Recognize the informational response area.
5. Identify the clinic-contact fallback and the boundary between general guidance and clinical judgment.

Chapters

1. 00:00 Black pre-roll and tutorial goal
2. 00:07 Suggested questions
3. 00:16 Chat-mode control
4. 00:24 General question field
5. 00:36 Send action
6. 00:47 Assistant response
7. 01:04 Clinic-contact fallback
8. 01:15 Expected result and fade to black

What the video shows

Opening and interface identity

The video begins on pure black, fades into the Tutorial 04 goal card, and then fades into the live assistant. A persistent FRONT-END UI and PATIENT-FACING FRONTDESK indicator identifies the public surface. The unrelated synthetic footer content is covered throughout the tutorial.

1. Suggested questions

The opening assistant view gives visitors a set of common prompts. These can reduce uncertainty and help a visitor understand the kinds of general questions the practice has prepared the assistant to address.

The tutorial explains the feature without endorsing the synthetic clinic’s wording, services, coverage statements, or marketing claims.

2. Chat mode

The pointer moves to the chat-mode control, rests for the 520 millisecond click dwell, and activates it. The free-text field appears while suggested prompts remain available.

3. Synthetic pre-booking question

The tutorial enters:

What should I expect before requesting a Spravato appointment?

This is a general preparation question. It does not contain a real name, symptoms, medical history, insurance identifier, contact information, or another personal detail.

4. Assistant response

After the send action, the recording waits for the conversation pane to contain a substantive response. It then returns the pane to its beginning and focuses on the response area so viewers can read the opening guidance.

The response can orient a visitor to preparation and next steps. It must not be treated as a diagnosis, final eligibility decision, or substitute for clinical care.

5. Clinic-contact fallback

The final interface focus moves to the separate contact panel. This gives visitors an alternative when they need staff help, when the assistant does not resolve the question, or when the question requires clinical escalation.

The recording does not activate a phone link, booking link, screening action, or another server-changing workflow.

Expected result

You can demonstrate how Frontdesk supports general pre-booking questions while preserving a visible route to practice staff and clinician-owned decisions.

Responsibilities by role

• Owners and managers approve assistant scope, public content, escalation rules, and review processes.
• Marketing managers maintain accurate general information and avoid unsupported claims.
• Front-desk staff handle administrative questions, appointment logistics, and unresolved follow-up.
• Doctors and clinical staff own medical interpretation, eligibility, diagnosis, and treatment decisions.