Prepare the tasks AI reception should handle, current practice information and calendar-booking rules. Also assign a person to accept the setup and maintain the information. A price-list PDF alone does not describe the whole reception workflow.
Agree the initial scope
Start with a few frequent tasks that have clear outcomes. Separate booking from service information and requests to speak to a clinician. For each, record the intended result and who handles exceptions.
Prepare an onboarding pack
Review the information with reception, especially where the website, calendar and staff notes disagree.
- Locations: addresses, opening hours and phone numbers.
- Appointments: names, durations, clinicians and online-booking restrictions.
- Prices: amounts or ranges, plus cases requiring an individual consultation.
- Rules: new patients, changes, cancellations and handover to a person.
- Ownership: who approves information, changes scripts and reviews errors.
Check the integration and the outcome
Booking, rescheduling and cancellation are separate operations. IQ Dental supports these actions. With FELG Dent, reception approves a new request and staff make changes or cancellations. Check the current integration scope for your software.
- Create a fictional appointment in an agreed test and verify date, clinician and duration in the calendar.
- Test an unavailable slot, incorrect details and a service outside scope.
- Confirm that an unresolved request reaches someone responsible for completing it.
FAQ
How long does onboarding take?
Timing should follow the agreed scope, telephony and PMS access, and test results. Ask for dependencies and acceptance criteria as well as a launch date.
Should we share a staff member’s password?
First agree the appropriate access method and permissions. Do not send passwords in ordinary messages. Configuration should also cover revoking access later.
What should we agree about cancellation?
Notice, final-month charges, restoring call routing, access to records and disconnecting the integration. Check these in the particular provider’s offer or contract.
Use our 12 voicebot acceptance scenarios before signing off. NIST AI RMF also discusses responsibility and evaluation. This checklist is an editorial implementation proposal, not certification or a promised setup time.


