Type, name, where, when
Choose your business type (hospital, real estate, salon, restaurant, hotel, resort, education or technology), enter the business name, your area and your opening hours. Callers hear these facts exactly as written.
Give your receptionist the right information.
Start with one service. Add the facts callers need, choose the opening greeting, and test the result. Add departments and people only when your business needs them.
Examples are starting points, not live business information.
Replace every sample name, address, schedule, price and policy. Preview all imported text before saving. Directory CSV examples are paused by default; activate entries only after customising them.
Quick setup: three questions, about two minutes
Open AI receptionist in the portal. The Quick setup card at the top asks three things and fills in everything else from your business type — the assistant's name, the three most common services, every safety rule for your industry and the greeting. You can change any of it later under Fine-tune.
Tick the services
The three most common services for your type are pre-ticked; untick any you do not offer or add more. Pick the language it greets in — after the greeting it follows the caller — and, optionally, a number to send callers to.
Save & go live
Review the one-line summary and save. New business types are approved by Naadham within a working day; your number answers as soon as it is approved. Pick a number on the same page if you have not yet.
WhatsApp is one more click. On the WhatsApp agent page, Use your AI receptionist on WhatsApp builds the assistant from this setup — same name, greeting and services — and publishes it once your number is connected with Meta.
Fine-tune (optional) holds the full form: assistant name and greeting, per-service details and documents, common answers, rules, bookable time slots and the languages included in your plan (Starter includes any 3 of the 10 Indian languages; Growth and above include all 10).
Outreach campaigns: let the AI call your customers
Open Outreach campaigns in the portal (Growth and up, verified account). Three steps: write what the AI should say, paste who to call (name, phone, a note per person), tick the confirmation that these are your own customers, and press Save & start calling. The AI keeps one line free for incoming calls and dials the rest between the hours you set (always inside 10:00–19:00 IST). Each row then fills in with status, duration, outcome, a QA score, the transcript and the recording; download the campaign as CSV any time. Full walkthrough: Outreach campaigns guide.
Choose how the conversation opens
- Under Greeting language, choose the language for the opening. Read the preview.
- Leave Opening greeting blank to use the standard greeting. If you supply your own, write it in the intended language: custom text is spoken as written.
- After the greeting, the receptionist follows the caller’s language. The greeting choice does not lock the entire call.
Available languages: Starter includes any 3 of the 10 Indian languages; Growth and above include all 10.
Examples for every supported service
Each editable text document includes an example description, service hours, locations, information to collect, confirmation process, limits and a sample question and answer. TXT is the simplest starting format and can be imported directly after editing.
61 service examples
Site visit requests
Site visit requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on listings, site visits, buying/renting, and connecting callers to an agent.
- How the AI handles it
- Ask project/area → preferred day/time → name + phone → confirm visit request; do not promise until checked.
- What the AI must not promise
- Never quote a final price without confirming with an agent. Never promise a site visit without checking availability. Do not share internal owner or broker phone numbers unless approved.
Property sales enquiries
Property sales enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on listings, site visits, buying/renting, and connecting callers to an agent.
- How the AI handles it
- Ask buy/invest, budget, and locality → share high-level info from FAQs → offer site visit or agent.
- What the AI must not promise
- Never quote a final price without confirming with an agent. Never promise a site visit without checking availability. Do not share internal owner or broker phone numbers unless approved.
Rental enquiries
Rental enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on listings, site visits, buying/renting, and connecting callers to an agent.
- How the AI handles it
- Ask area, budget, BHK → note requirements → offer matching help / agent follow-up.
- What the AI must not promise
- Never quote a final price without confirming with an agent. Never promise a site visit without checking availability. Do not share internal owner or broker phone numbers unless approved.
Resale enquiries
Resale enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on listings, site visits, buying/renting, and connecting callers to an agent.
- How the AI handles it
- Ask locality and budget → capture brief requirements → schedule agent callback.
- What the AI must not promise
- Never quote a final price without confirming with an agent. Never promise a site visit without checking availability. Do not share internal owner or broker phone numbers unless approved.
New project information
New project information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on listings, site visits, buying/renting, and connecting callers to an agent.
- How the AI handles it
- Ask which project → answer from knowledge/FAQs only → offer site visit.
- What the AI must not promise
- Never quote a final price without confirming with an agent. Never promise a site visit without checking availability. Do not share internal owner or broker phone numbers unless approved.
Agent callbacks
Agent callbacks guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on listings, site visits, buying/renting, and connecting callers to an agent.
- How the AI handles it
- Take name, phone, and interest → confirm an agent will call back → thank them.
- What the AI must not promise
- Never quote a final price without confirming with an agent. Never promise a site visit without checking availability. Do not share internal owner or broker phone numbers unless approved.
Home loan referrals
Home loan referrals guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on listings, site visits, buying/renting, and connecting callers to an agent.
- How the AI handles it
- Ask if pre-approved → note bank preference if any → offer loan-desk callback; never guarantee approval.
- What the AI must not promise
- Never quote a final price without confirming with an agent. Never promise a site visit without checking availability. Do not share internal owner or broker phone numbers unless approved.
Appointment requests
Appointment requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on departments, doctor availability, appointments, visiting hours, and emergencies.
- How the AI handles it
- Ask specialty or doctor → preferred slot → name → confirm all three → create_booking only with an offered slot_id.
- What the AI must not promise
- Never give a medical diagnosis or prescribe treatment. Never promise an appointment without confirming the schedule. For emergencies, advise calling emergency services or coming to ER immediately.
Doctor availability
Doctor availability guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on departments, doctor availability, appointments, visiting hours, and emergencies.
- How the AI handles it
- Ask doctor or specialty name → check knowledge → say availability in one sentence → offer to book.
- What the AI must not promise
- Never give a medical diagnosis or prescribe treatment. Never promise an appointment without confirming the schedule. For emergencies, advise calling emergency services or coming to ER immediately.
Department information
Department information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on departments, doctor availability, appointments, visiting hours, and emergencies.
- How the AI handles it
- Ask which department → answer from knowledge/FAQs → offer appointment if relevant.
- What the AI must not promise
- Never give a medical diagnosis or prescribe treatment. Never promise an appointment without confirming the schedule. For emergencies, advise calling emergency services or coming to ER immediately.
Diagnostics / lab enquiries
Diagnostics / lab enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on departments, doctor availability, appointments, visiting hours, and emergencies.
- How the AI handles it
- Ask test type and preferred time → note it → offer callback or book if slots exist.
- What the AI must not promise
- Never give a medical diagnosis or prescribe treatment. Never promise an appointment without confirming the schedule. For emergencies, advise calling emergency services or coming to ER immediately.
Report collection information
Report collection information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on departments, doctor availability, appointments, visiting hours, and emergencies.
- How the AI handles it
- Ask patient name / report type → explain pickup hours from FACTS → offer desk contact if stuck.
- What the AI must not promise
- Never give a medical diagnosis or prescribe treatment. Never promise an appointment without confirming the schedule. For emergencies, advise calling emergency services or coming to ER immediately.
Home visit requests
Home visit requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on departments, doctor availability, appointments, visiting hours, and emergencies.
- How the AI handles it
- Ask service needed + preferred day/area → name + phone → take a staff callback request; do not invent availability.
- What the AI must not promise
- Never give a medical diagnosis or prescribe treatment. Never promise an appointment without confirming the schedule. For emergencies, advise calling emergency services or coming to ER immediately.
Patient reception callbacks
Patient reception callbacks guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on departments, doctor availability, appointments, visiting hours, and emergencies.
- How the AI handles it
- Take name, phone, and brief need → confirm staff will call back → thank them.
- What the AI must not promise
- Never give a medical diagnosis or prescribe treatment. Never promise an appointment without confirming the schedule. For emergencies, advise calling emergency services or coming to ER immediately.
Product demos
Product demos guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on product/support enquiries, demos, onboarding, and routing to the right team.
- How the AI handles it
- Ask use case + preferred time + contact → schedule demo callback.
- What the AI must not promise
- Never invent product features that are not listed. Never share internal credentials or admin access details. Do not promise SLA timelines without confirming with support.
Technical support requests
Technical support requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on product/support enquiries, demos, onboarding, and routing to the right team.
- How the AI handles it
- Ask brief issue + account/email if offered → reassure routing to support — no invented fixes.
- What the AI must not promise
- Never invent product features that are not listed. Never share internal credentials or admin access details. Do not promise SLA timelines without confirming with support.
Onboarding assistance
Onboarding assistance guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on product/support enquiries, demos, onboarding, and routing to the right team.
- How the AI handles it
- Ask company name + who is onboarding → note and offer onboarding callback.
- What the AI must not promise
- Never invent product features that are not listed. Never share internal credentials or admin access details. Do not promise SLA timelines without confirming with support.
Product information
Product information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on product/support enquiries, demos, onboarding, and routing to the right team.
- How the AI handles it
- Answer only from FAQs/knowledge; if unknown, say so and offer a demo.
- What the AI must not promise
- Never invent product features that are not listed. Never share internal credentials or admin access details. Do not promise SLA timelines without confirming with support.
Pricing enquiries
Pricing enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on product/support enquiries, demos, onboarding, and routing to the right team.
- How the AI handles it
- Share only FAQ pricing; otherwise offer sales callback — never invent discounts.
- What the AI must not promise
- Never invent product features that are not listed. Never share internal credentials or admin access details. Do not promise SLA timelines without confirming with support.
Account / billing support
Account / billing support guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on product/support enquiries, demos, onboarding, and routing to the right team.
- How the AI handles it
- Ask account email / invoice issue in one line → route to billing; never take card CVV.
- What the AI must not promise
- Never invent product features that are not listed. Never share internal credentials or admin access details. Do not promise SLA timelines without confirming with support.
Partnership enquiries
Partnership enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on product/support enquiries, demos, onboarding, and routing to the right team.
- How the AI handles it
- Ask partnership type + company → capture and promise partnership team follow-up.
- What the AI must not promise
- Never invent product features that are not listed. Never share internal credentials or admin access details. Do not promise SLA timelines without confirming with support.
Admissions enquiries
Admissions enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on courses, admissions, fees overview, schedules, and campus queries.
- How the AI handles it
- Ask programme + intake period → share FAQ dates → offer counselling callback.
- What the AI must not promise
- Never guarantee admission or exam results. Never quote final fees without confirming the current fee sheet. Do not collect sensitive ID documents over the phone.
Course information
Course information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on courses, admissions, fees overview, schedules, and campus queries.
- How the AI handles it
- Ask stream/level → answer from knowledge/FAQs → offer brochure/callback.
- What the AI must not promise
- Never guarantee admission or exam results. Never quote final fees without confirming the current fee sheet. Do not collect sensitive ID documents over the phone.
Fees enquiries
Fees enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on courses, admissions, fees overview, schedules, and campus queries.
- How the AI handles it
- Share only published FAQ ranges; say final fees need confirmation from admissions.
- What the AI must not promise
- Never guarantee admission or exam results. Never quote final fees without confirming the current fee sheet. Do not collect sensitive ID documents over the phone.
Campus tour requests
Campus tour requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on courses, admissions, fees overview, schedules, and campus queries.
- How the AI handles it
- Ask preferred day → name → confirm tour request pending availability.
- What the AI must not promise
- Never guarantee admission or exam results. Never quote final fees without confirming the current fee sheet. Do not collect sensitive ID documents over the phone.
Class schedule information
Class schedule information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on courses, admissions, fees overview, schedules, and campus queries.
- How the AI handles it
- Ask programme → answer from knowledge; if unknown, offer office hours callback.
- What the AI must not promise
- Never guarantee admission or exam results. Never quote final fees without confirming the current fee sheet. Do not collect sensitive ID documents over the phone.
Scholarship enquiries
Scholarship enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on courses, admissions, fees overview, schedules, and campus queries.
- How the AI handles it
- Share FAQ eligibility only; never promise an award.
- What the AI must not promise
- Never guarantee admission or exam results. Never quote final fees without confirming the current fee sheet. Do not collect sensitive ID documents over the phone.
Counsellor callbacks
Counsellor callbacks guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on courses, admissions, fees overview, schedules, and campus queries.
- How the AI handles it
- Take name, phone, programme interest → confirm counsellor will call.
- What the AI must not promise
- Never guarantee admission or exam results. Never quote final fees without confirming the current fee sheet. Do not collect sensitive ID documents over the phone.
Accommodation enquiries
Accommodation enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on stays, packages, availability, amenities, and booking enquiries.
- How the AI handles it
- Ask dates + guests + room preference → name → check availability path; no fake confirm.
- What the AI must not promise
- Never confirm a booking without checking real availability. Never quote a final package price without confirming current rates. Do not promise complimentary upgrades unless listed.
Holiday package enquiries
Holiday package enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on stays, packages, availability, amenities, and booking enquiries.
- How the AI handles it
- Ask travel dates + guests → outline FAQ packages → offer booking follow-up.
- What the AI must not promise
- Never confirm a booking without checking real availability. Never quote a final package price without confirming current rates. Do not promise complimentary upgrades unless listed.
Amenities information
Amenities information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on stays, packages, availability, amenities, and booking enquiries.
- How the AI handles it
- Answer from FACTS/FAQs only; then ask if they want to reserve.
- What the AI must not promise
- Never confirm a booking without checking real availability. Never quote a final package price without confirming current rates. Do not promise complimentary upgrades unless listed.
Event / banquet enquiries
Event / banquet enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on stays, packages, availability, amenities, and booking enquiries.
- How the AI handles it
- Ask event date + guest count + type → capture for events team callback.
- What the AI must not promise
- Never confirm a booking without checking real availability. Never quote a final package price without confirming current rates. Do not promise complimentary upgrades unless listed.
Spa / activity requests
Spa / activity requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on stays, packages, availability, amenities, and booking enquiries.
- How the AI handles it
- Ask preferred activity/time → note request; confirm only if listed as available.
- What the AI must not promise
- Never confirm a booking without checking real availability. Never quote a final package price without confirming current rates. Do not promise complimentary upgrades unless listed.
Airport transfer requests
Airport transfer requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on stays, packages, availability, amenities, and booking enquiries.
- How the AI handles it
- Ask flight time + guests → note transfer request with booking.
- What the AI must not promise
- Never confirm a booking without checking real availability. Never quote a final package price without confirming current rates. Do not promise complimentary upgrades unless listed.
Table reservation requests
Table reservation requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on reservations, hours, menu highlights, and private dining.
- How the AI handles it
- Ask covers → date → time → name → confirm reservation request; note special needs if offered.
- What the AI must not promise
- Never confirm a reservation without checking table availability. Never promise dishes that may be unavailable that day. Do not take card payments over the phone.
Private dining enquiries
Private dining enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on reservations, hours, menu highlights, and private dining.
- How the AI handles it
- Ask date, guests, occasion → capture for private-dining follow-up.
- What the AI must not promise
- Never confirm a reservation without checking table availability. Never promise dishes that may be unavailable that day. Do not take card payments over the phone.
Catering enquiries
Catering enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on reservations, hours, menu highlights, and private dining.
- How the AI handles it
- Ask date, guest count, venue → take callback details.
- What the AI must not promise
- Never confirm a reservation without checking table availability. Never promise dishes that may be unavailable that day. Do not take card payments over the phone.
Menu / dietary information
Menu / dietary information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on reservations, hours, menu highlights, and private dining.
- How the AI handles it
- Share FAQ highlights only; never invent dishes or allergens beyond known FAQs.
- What the AI must not promise
- Never confirm a reservation without checking table availability. Never promise dishes that may be unavailable that day. Do not take card payments over the phone.
Group booking requests
Group booking requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on reservations, hours, menu highlights, and private dining.
- How the AI handles it
- Ask guest count + date → route to group booking callback if large.
- What the AI must not promise
- Never confirm a reservation without checking table availability. Never promise dishes that may be unavailable that day. Do not take card payments over the phone.
Takeaway enquiries
Takeaway enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on reservations, hours, menu highlights, and private dining.
- How the AI handles it
- Share hours and FAQ takeaway info; do not take card payments on the call.
- What the AI must not promise
- Never confirm a reservation without checking table availability. Never promise dishes that may be unavailable that day. Do not take card payments over the phone.
Room enquiries
Room enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on room booking, check-in/out, amenities, and stay enquiries.
- How the AI handles it
- Ask dates + guests + room type → name → check availability; confirm only when sure.
- What the AI must not promise
- Never confirm a room without checking availability. Never quote a final rate without confirming current tariffs. Do not take card CVV or full card details over the phone.
Check-in / check-out information
Check-in / check-out information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on room booking, check-in/out, amenities, and stay enquiries.
- How the AI handles it
- Answer from FACTS/FAQs; offer early check-in as subject to availability.
- What the AI must not promise
- Never confirm a room without checking availability. Never quote a final rate without confirming current tariffs. Do not take card CVV or full card details over the phone.
Amenities information
Amenities information guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on room booking, check-in/out, amenities, and stay enquiries.
- How the AI handles it
- List known amenities briefly; ask if they want a room.
- What the AI must not promise
- Never confirm a room without checking availability. Never quote a final rate without confirming current tariffs. Do not take card CVV or full card details over the phone.
Airport transfer requests
Airport transfer requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on room booking, check-in/out, amenities, and stay enquiries.
- How the AI handles it
- Ask flight time + guests → attach to stay enquiry.
- What the AI must not promise
- Never confirm a room without checking availability. Never quote a final rate without confirming current tariffs. Do not take card CVV or full card details over the phone.
Conference / banquet enquiries
Conference / banquet enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on room booking, check-in/out, amenities, and stay enquiries.
- How the AI handles it
- Ask date + headcount + setup → events callback.
- What the AI must not promise
- Never confirm a room without checking availability. Never quote a final rate without confirming current tariffs. Do not take card CVV or full card details over the phone.
Long-stay enquiries
Long-stay enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on room booking, check-in/out, amenities, and stay enquiries.
- How the AI handles it
- Ask duration + budget band if offered → sales callback.
- What the AI must not promise
- Never confirm a room without checking availability. Never quote a final rate without confirming current tariffs. Do not take card CVV or full card details over the phone.
Restaurant enquiries
Restaurant enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on room booking, check-in/out, amenities, and stay enquiries.
- How the AI handles it
- Share hours/FAQs; offer table help if that service is offered.
- What the AI must not promise
- Never confirm a room without checking availability. Never quote a final rate without confirming current tariffs. Do not take card CVV or full card details over the phone.
Haircut appointments
Haircut appointments guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on appointments, services, stylist availability, and pricing ranges.
- How the AI handles it
- Ask preferred time + stylist if any → name → confirm appointment request.
- What the AI must not promise
- Never confirm an appointment without checking stylist availability. Never quote a final price for custom work without confirmation. Do not give medical or dermatology advice.
Hair colour enquiries
Hair colour enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on appointments, services, stylist availability, and pricing ranges.
- How the AI handles it
- Ask colour type + time → warn it may take longer → book slot request.
- What the AI must not promise
- Never confirm an appointment without checking stylist availability. Never quote a final price for custom work without confirmation. Do not give medical or dermatology advice.
Spa / massage appointments
Spa / massage appointments guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on appointments, services, stylist availability, and pricing ranges.
- How the AI handles it
- Ask therapy type + time → name → book.
- What the AI must not promise
- Never confirm an appointment without checking stylist availability. Never quote a final price for custom work without confirmation. Do not give medical or dermatology advice.
Facial appointments
Facial appointments guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on appointments, services, stylist availability, and pricing ranges.
- How the AI handles it
- Ask preferred time → name → book.
- What the AI must not promise
- Never confirm an appointment without checking stylist availability. Never quote a final price for custom work without confirmation. Do not give medical or dermatology advice.
Bridal enquiries
Bridal enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on appointments, services, stylist availability, and pricing ranges.
- How the AI handles it
- Ask event date + package interest → counselling/callback; do not final-quote custom bridal work.
- What the AI must not promise
- Never confirm an appointment without checking stylist availability. Never quote a final price for custom work without confirmation. Do not give medical or dermatology advice.
Manicure / pedicure appointments
Manicure / pedicure appointments guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on appointments, services, stylist availability, and pricing ranges.
- How the AI handles it
- Ask service + time → name → book.
- What the AI must not promise
- Never confirm an appointment without checking stylist availability. Never quote a final price for custom work without confirmation. Do not give medical or dermatology advice.
Stylist availability
Stylist availability guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on appointments, services, stylist availability, and pricing ranges.
- How the AI handles it
- Ask stylist name if known + time → check availability path.
- What the AI must not promise
- Never confirm an appointment without checking stylist availability. Never quote a final price for custom work without confirmation. Do not give medical or dermatology advice.
Service booking
Service booking guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on service bookings, repair estimates, pick-up/drop and spare-part approvals.
- How the AI handles it
- Ask vehicle + service type → preferred day/time → name → confirm booking request.
- What the AI must not promise
- Never replace or add a part without the customer's approval. Never quote a final repair price before the vehicle is inspected. Never promise a delivery time the workshop has not confirmed.
Repair & diagnosis
Repair & diagnosis guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on service bookings, repair estimates, pick-up/drop and spare-part approvals.
- How the AI handles it
- Ask vehicle + problem → offer inspection slot → name → confirm; price after inspection.
- What the AI must not promise
- Never replace or add a part without the customer's approval. Never quote a final repair price before the vehicle is inspected. Never promise a delivery time the workshop has not confirmed.
Price / estimate enquiries
Price / estimate enquiries guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on service bookings, repair estimates, pick-up/drop and spare-part approvals.
- How the AI handles it
- Ask vehicle + job → give listed price or range → offer inspection for a firm estimate.
- What the AI must not promise
- Never replace or add a part without the customer's approval. Never quote a final repair price before the vehicle is inspected. Never promise a delivery time the workshop has not confirmed.
Vehicle status updates
Vehicle status updates guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on service bookings, repair estimates, pick-up/drop and spare-part approvals.
- How the AI handles it
- Ask registration number → hand to the team for the live status; never guess.
- What the AI must not promise
- Never replace or add a part without the customer's approval. Never quote a final repair price before the vehicle is inspected. Never promise a delivery time the workshop has not confirmed.
Spare-part approvals
Spare-part approvals guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on service bookings, repair estimates, pick-up/drop and spare-part approvals.
- How the AI handles it
- Ask which estimate → ask them to tap Approve or Decline on the estimate message.
- What the AI must not promise
- Never replace or add a part without the customer's approval. Never quote a final repair price before the vehicle is inspected. Never promise a delivery time the workshop has not confirmed.
Pick-up & drop requests
Pick-up & drop requests guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on service bookings, repair estimates, pick-up/drop and spare-part approvals.
- How the AI handles it
- Ask address area + preferred time + vehicle → name → confirm request.
- What the AI must not promise
- Never replace or add a part without the customer's approval. Never quote a final repair price before the vehicle is inspected. Never promise a delivery time the workshop has not confirmed.
Accident / insurance repair
Accident / insurance repair guide: hours, request details, handoff rules and an example answer.
Download example · TXTSee what belongs in this document
- Service information
- Focus on service bookings, repair estimates, pick-up/drop and spare-part approvals.
- How the AI handles it
- Ask vehicle + damage + insurer → offer inspection → never promise claim approval.
- What the AI must not promise
- Never replace or add a part without the customer's approval. Never quote a final repair price before the vehicle is inspected. Never promise a delivery time the workshop has not confirmed.
No matching examples. Clear the search or choose another business type.
Import a supporting document
- Download the closest example. Replace sample facts with your approved business information and save the file.
- In AI receptionist → Services & knowledge, select the service and open its card.
- Expand Add supporting documents (optional) and select your file.
- Review and correct the extracted text. Importing does not save or publish it. Remove irrelevant content and confirm names, hours and policies.
- Choose the document’s review / expiry date in the form. A date typed inside a file does not set this field automatically. Expired documents stop being used.
- Save the receptionist setup. Check the confirmation message and resolve any approval or voice-sync issue before relying on the change.
File formats and limits
- TXT or Markdown: clear headings and short factual paragraphs.
- PDF: selectable text. Scanned images need conversion to text first; image-only PDFs are not a reliable source for this importer.
- Word: .docx files, not legacy .doc files. Keep tables simple.
- Spreadsheets: .csv or .xlsx with clear column headers. Avoid merged cells and review what was extracted.
- Up to 5 MB per file and 3 documents per service. Each reviewed document must fit within 12,000 characters. Combined service context is also bounded; split or shorten oversized material.
- The importer retains reviewed text, not the original file. Keep your original documents elsewhere.
Which upload belongs where?
- Service documents: published menus, enquiry guides, approved service policies and location information. Add them to the matching service card.
- Directory CSV: structured locations, departments and people. Use Locations & team, not the service document importer, when you want editable directory entries.
- Business verification: genuine registration/identity documents belong in Verification. The examples here are not verification documents.
Use public-facing business facts. Do not upload patient records, private customer lists, passwords or internal HR files.
One location today. Many teams tomorrow.
A small business can keep its hours and service details in AI receptionist. Use Locations & team when you need shared branch or staff information. These entries do not create staff logins; use Portal access for that.
- Add location: name, address and opening hours.
- Add department: link its location and select the services it supports.
- Add person: link the department and location where relevant. Leave hours inherited unless this person works a different schedule.
- Save entry: review the confirmation. Uncheck “Available to the receptionist” to pause an entry. Pausing a department also prevents its linked people being offered.
Hospital directory example
One sample location, one department and one person, all paused. Customise before using.
Download example · CSVReal estate directory example
One sample location, one department and one person, all paused. Customise before using.
Download example · CSVSalon directory example
One sample location, one department and one person, all paused. Customise before using.
Download example · CSVBulk updates without recreating people
- Expand Manage many entries with a spreadsheet. Download the current directory to keep the existing references.
- Edit the spreadsheet. Keep each
idunchanged. Uselocation,departmentorpersonforkind. Link entries withlocation_idsanddepartment_ids; separate several references with|. - Preview a UTF-8 CSV: at most 1 MB and 500 rows per upload. Split larger exports into batches, keeping the header. Import locations and departments before people when splitting linked records.
- Review each new or updated entry, then apply. An omitted row stays unchanged; an omitted column keeps its saved value; a blank cell clears it. Set
active=falseto pause. - If someone edited the same entries after preview, refresh and preview again instead of overwriting their changes.
The directory supports up to 10,000 entries per business. Availability information is not a booking calendar.
Naadham AI and Naadham SI
Naadham SI is the same product as Naadham AI, built and operated by Vistraal Private Limited at naadham.ai. SI receptionist and super intelligence receptionist are Naadham branding for its existing AI receptionist capabilities, not claims of verified general or superhuman intelligence. These setup instructions apply to both names. Read the product and brand explanation.
Confirmed bookings, requests and external calendars
Naadham can confirm a booking against configured available slots when the reservation succeeds. If no matching slot is available or the booking cannot be confirmed, it records a request for staff. Directory hours, documents and temporary availability notes provide information; they do not create bookable slots or automatically synchronize an external calendar or hospital system.
- Configured booking slots: use the business schedule to offer a matching service, location, person and time. Confirm only after the reservation succeeds and appears in Bookings & requests.
- Information-only availability: a note that a doctor or stylist works from 10am to 1pm helps answer an enquiry. It does not reserve any appointment in that period.
- External calendars and EHR/HMS: uploading a document or directory does not enable automatic synchronization. The API and webhook reference describes integration interfaces; confirm account availability and test the actual integration before promising external write-back, cancellation or rescheduling.
Review booking assistant features and test both a confirmed reservation and an unavailable-slot request during onboarding.
Keep changing availability fresh
For a doctor, stylist or advisor, edit the person in Locations & team and expand Temporary availability update. Enter the change, optional start date and required expiry. For a service-wide change, use the service card’s temporary update instead.
Example: a one-day doctor schedule
“Dr Example is available at Central branch from 10am–1pm today. Reception must confirm appointment requests.” Choose today for both start and expiry, replace the example with the real schedule, then save.
Dates follow the business region. Expired or future updates are excluded from current answers. An expired note does not mean someone is free. There is no automatic hospital-system or calendar sync in this workflow.
Daily update worksheet · TXT Common questions template · TXTBefore answering real callers
- Replace all example information and review each selected service.
- Check the opening greeting, fallback contact, schedules and expiry dates.
- Complete email verification, business verification, account approval and number allocation as shown in the portal.
- Call the allocated line. Test an ordinary question, another language, an unavailable person and a request the AI must hand off.
- Review Call logs for the transcript, recording and outcome. Confirm that appointments are described as requests until your actual booking process confirms them.
Something does not look right?
- The document has no usable text
- Use selectable text or a plain-text version. Shorten the document if it exceeds the text limit.
- The receptionist uses old information
- Check that the change was saved, the entry is active, dates cover today and the save message reports no voice-sync failure. Retry a failed sync before relying on the update.
- A person does not appear
- Check their department/location references, active status and whether the department supports a selected service. Search by the exact saved name.
- My number is not answering
- Check account approval, verification and number allocation first. Setup documents alone do not enable calling. Contact support with the number and call time if the line still fails.