Dental website chatbot: set up services and team scheduling

A patient opens your dental practice website after work and wants to book a routine exam. To offer a usable appointment, the website needs to know how long that visit takes, which dentists provide it and when each of them works. The practice’s opening hours alone cannot answer those questions.

Niwa’s Scheduler lets you define bookable services, assign them to team members and set each person’s working hours, breaks and days off. Visitors can choose an available time and complete a booking that creates an appointment record in WordPress. The website assistant can explain your published service information and guide them into that booking flow.

For a dental office, the practice still decides which visits people may book online and what requires a staff conversation. A service description can explain what an appointment includes. Choosing treatment for someone’s symptoms belongs with a qualified professional. Use fictional contact details while testing, and complete the privacy review below before collecting real patient information.

Prepare your WordPress pages and office information

Start with the information a patient needs to attend. Check the service pages, contact page and booking button together. A visitor who reads an old address or a different set of opening hours will bring that confusion into the booking conversation.

Information	What to record	Who maintains it
Office hours	Public opening hours, holiday exceptions and timezone	Office manager
Location	Address, entrance, parking and accessibility information	Front desk
Services	Approved names and descriptions, plus which visits are bookable online	Practice lead
Scheduling	Booking destination, service durations and the person responsible for the schedule	Scheduling owner
Contact	Main number, contact hours and published after-hours route	Office manager
Policies	Current cancellation and new-patient information	Practice lead
Escalation	Approved wording for clinical, urgent and unanswered questions	Designated reviewer

Add a source URL and a review date to the office information you give the assistant. Resolve any disagreement between that information and the website. Keep patient lists, treatment notes and insurance documents out of this public knowledge set.

Check the site’s timezone under Settings > General in WordPress. For a practice in New York, for example, choose the appropriate city-based timezone and verify the displayed appointment times. WordPress documents the timezone setting here. Niwa uses the site’s timezone for its local scheduling records.

Set up services and each team member’s schedule

Open Niwa’s Scheduler tab in the WordPress admin. Add the people who take appointments, including their names and work email addresses. Enter working days and hours for each person, then their breaks and excluded dates or date ranges. A dentist who works Tuesday and Thursday needs that schedule even if reception is open all week.

Next, add each service with a clear name, description and duration in minutes. Under Assigned team members, select the people the practice has approved to provide that service. Niwa uses this assignment when it offers appointments. The practice is responsible for deciding who is qualified and which services are suitable for online booking.

Consider this fictional US office with two dentists and a hygienist. These hours and durations are examples for configuring software; your clinical team should set the actual appointment lengths.

Team member	Working hours	Break
Dr. Reed	Monday, Wednesday and Friday, 9 a.m. to 5 p.m.	Noon to 12:30 p.m.
Dr. Shah	Tuesday and Thursday, 11 a.m. to 7 p.m.	3 p.m. to 3:30 p.m.
Jamie, hygienist	Monday through Friday, 8:30 a.m. to 4:30 p.m.	12:30 p.m. to 1 p.m.

Bookable service	Example duration	Assigned providers
New-patient consultation	45 minutes	Dr. Reed and Dr. Shah
Routine exam	30 minutes	Dr. Reed and Dr. Shah
Cleaning	45 minutes	Jamie

A visitor looking for a Thursday consultation can see Dr. Shah’s available times. Dr. Reed has no Thursday working hours in this example. Someone selecting Cleaning sees availability for Jamie, because that service is assigned to Jamie. Giving every service to every member would erase the distinction you just configured.

Set the buffer between appointments as well. With a 10-minute buffer, a 45-minute consultation starting at 9 a.m. occupies the provider until 9:55 a.m. for booking-conflict purposes. A second appointment at 9:30 a.m. would overlap. The Scheduler checks the full service duration against working hours and breaks, and checks existing bookings and their buffers before offering a slot.

Enter vacations and other unavailable dates for the affected member. For an office-wide closure, make sure every relevant team member is unavailable. Assign someone to update these settings when shifts change. Niwa’s booking guide explains the relationship between configured services, availability and appointment records.

Put the booking flow on your WordPress website

Niwa provides a booking button shortcode, [niwa_booking], which you can place in a WordPress Shortcode block on your appointment page. You can also use #niwa-booking as the destination of an existing button or menu link. These entry points open the Scheduler’s booking flow outside the chat.

Put the button where someone reading a service description can find it. Preview the page on a phone and check that the button opens the service, date and time controls. Enable frontend scheduling only after the configuration and practice review are complete.

The Niwa website assistant can answer questions from the office information you supply and guide visitors to the enabled booking flow. Give it the approved descriptions and clear instructions for questions that need the front desk. It should not select a treatment based on symptoms or fit an unusual request into a routine appointment simply because a slot is free.

Walk through a patient’s booking

Use the fictional office above and test this question: “Can I book a routine exam on Thursday afternoon?” The assistant can explain the published appointment description and help the visitor reach the Scheduler.

1. The visitor selects Routine exam. The service is 30 minutes long and is assigned to Dr. Reed and Dr. Shah.
2. They choose a provider if they have a preference, or use the available-member option. The selected service limits the eligible team members.
3. They choose a date and an available time. In this example, a Thursday appointment depends on Dr. Shah’s hours, break and existing bookings. A time overlapping the 3 p.m. break should be unavailable.
4. They supply the contact fields the practice has enabled and submit the booking. Scheduler lets you configure collection of name, phone and email. Keep the collection limited to what your approved process needs.
5. Niwa rechecks availability before saving. A successful booking creates a confirmed local appointment record with the service, assigned member, start and end times, and timezone. If the slot is no longer available, the visitor needs another time.

Open the saved appointment in the booking workspace and compare it with what the visitor selected. Check the confirmation channel separately: a saved record and a delivered message are separate results. Email delivery and any configured WhatsApp confirmation need their own test.

Tell patients how to request a change or cancellation. Staff can manage appointment details and status in Niwa’s booking workspace; the practice should publish the customer route it actually supports. A conversation saying “You’re booked” should agree with the saved record.

Check external calendars and existing booking systems

Niwa has local scheduling and appointment records. Its current implementation also supports checking busy periods from a connected team member’s Google Calendar. That requires the relevant member’s authorized connection and a working integration. Connecting an administrator’s calendar alone does not establish each dentist’s busy-time coverage.

If you use that connection, ask your installer to verify the installed version and authorization, then test whether an event marked busy removes the corresponding slot for that member. Verify any booking-to-calendar sync separately. The example in this guide uses the local Scheduler; it does not establish that Google Calendar is connected on your practice’s website.

If the practice keeps its booking process in another portal, Niwa can direct visitors to its reviewed URL. Use a clean link without a patient’s name, symptoms or other personal details in the address. A request form should be described as a request; use confirmation wording only when the destination actually reserves the appointment.

A local Niwa appointment does not by itself prove that an appointment also exists in dental practice-management software. Decide which system staff will use as their scheduling record and verify any connection between systems. The guide to booking administration covers the broader workflow.

Give the front desk clear handoffs

The assistant can explain opening hours, directions, parking and approved service descriptions. Individual insurance questions, treatment suitability, prescription requests and complaints need the appropriate office process. A published fee also needs its stated conditions; it is not an individualized treatment estimate.

Use wording reviewed by the practice for urgent or emergency questions. The chatbot should not decide that symptoms can wait for an available appointment. When a service or policy is missing from the approved information, provide the verified staff contact route.

Set response expectations the office can meet. If the front desk replies during business hours, say so. For a practice that only schedules by phone, publish the correct number and contact hours.

Review patient information before launch

A name linked to a request for care may be protected health information. HHS explains that cloud providers handling electronic PHI for a HIPAA-regulated organization can be business associates even when they cannot read encrypted information. Review the required agreements and risk analysis with the practice’s privacy lead. See HHS guidance on HIPAA and cloud computing.

Map where chat and booking information goes: WordPress hosting, the AI provider, logs, analytics, notification tools and any connected booking or calendar service. Review access, retention, deletion, incident handling and contractual responsibilities. Niwa’s privacy and website safety page explains local storage and processing through connected providers.

Verify Niwa’s suitability and business-associate agreement availability in writing for your proposed setup. Local WordPress storage is not proof of HIPAA compliance. Even a general-information chat can receive unsolicited health information; a notice asking people not to share it does not replace this review. While arrangements are unresolved, keep demonstrations controlled and use synthetic questions and fictional contact details.

Rehearse the workflow before patients use it

Have the office manager and scheduling owner run these checks with test data. Record what happened, including the appointment record and any notification, so a successful chat message is not the only evidence.

1. Ask about regular hours, a holiday, parking and a published service. Answers should match the correct location’s approved information; unknown exceptions should reach staff.
2. Select each service and check its duration and eligible providers. In the example, Cleaning should use Jamie’s schedule.
3. Look for a slot outside a member’s working hours, during a break and on an excluded date. None should be offered.
4. Create an authorized test booking, then check an overlapping time for the same member, including the configured buffer. Repeat the availability check after the first record is saved.
5. Complete a booking and inspect the service, provider, date, start and end times, timezone and confirmed status in the saved record.
6. Check enabled notifications for the correct recipient and permitted content. If using an external calendar, check its busy-time behavior and sync separately.
7. Test the booking button and full form on a phone. For an external portal, verify that the link reaches the intended destination and describes its request or confirmation status accurately.
8. Ask about individual insurance coverage, treatment choice and urgent help. Check the approved handoff and escalation wording.
9. Ask to change an existing visit and ask about an unpublished service. Both questions should follow the practice’s actual process.
10. Review how an unexpected health disclosure would be handled before opening the chat to patients. Resolve failures in privacy handling, clinical escalation, booking status or destination before launch.

Review what the office has to do afterward

Track completed bookings and the corrections staff have to make: wrong services, misunderstood times or requests that needed a conversation first. Keep submitted requests, confirmed appointments and completed visits separate in your reporting.

You can compare staff handling time for similar administrative inquiries before and after a pilot. Define the measurement method first, and keep patient content out of unreviewed analytics tools. Chat message counts alone do not establish saved staff time.

For a Niwa demonstration, bring your service list, each provider’s weekly hours and the assignment of services to providers. Ask to see a complete test booking and its saved record, then change one provider’s availability and check the offered times again. Keep patient records out of the demo.

Updated October 6, 2026. This guide covers administrative scheduling and does not provide clinical or legal advice.