Skip to content

Services

AI Front Desk, in detail

One system, sold at a fixed price on a fixed timeline. This page is the full scope — what is included, what is deliberately not, and what we need from you to hit ten days.

What is included

  • WhatsApp Business API setup

    Business verification, a verified sender on the number you already advertise, message templates written and submitted to Meta, and opt-in capture that matches their policy. If you already run a WhatsApp Business account we migrate it rather than starting a second number.

  • The languages your patients actually write in

    English, Tamil and transliterated Tamil typed in Latin script — which in practice is how most people message. Additional languages are possible; we scope them in discovery rather than assuming.

  • Retrieval over your documents

    Timings, location and parking notes, test panels, preparation instructions, price lists, insurance and empanelment details, doctor profiles and availability rules. You hand us the documents you already have; we do not ask you to rewrite them into a bot builder.

  • Appointment booking and rescheduling

    Two-way sync with Google Calendar or your existing HMIS where it exposes an API. Slot length, buffers, doctor leave and double-booking rules live in ordinary code with tests, not in a prompt.

  • Reminders and no-show recovery

    A confirmation request ahead of the appointment, automatic release of unconfirmed slots on your rules, and a re-booking prompt for patients who did not turn up.

  • Report delivery with identity checks

    Once a report is released, the patient is notified and can retrieve it after a verification step you configure. Every delivery is logged with a timestamp and the identity check that passed.

  • Human escalation

    A single instruction — or any clinical question, complaint or confusion the assistant detects — routes the conversation to your front desk with the full history attached.

  • An evaluation harness you keep

    The graded question set built from your real message history, and the script that runs it. You can re-run it yourself after any change to see whether you broke anything.

  • Logging and a weekly digest

    Every conversation is searchable. A weekly email shows volume, what got escalated and what the assistant could not answer, which is usually where the next improvement is.

The ten days

  1. Days 0–2

    Discovery

    We sit with your front desk for a morning, read the last few hundred real patient messages, and write down every question they actually ask.

  2. Days 3–6

    Build

    Retrieval over your documents, booking logic against your calendar, WhatsApp templates submitted for approval while the rest is being built.

  3. Days 7–8

    Evaluation

    We run the assistant against the real question set from day one and fix what it gets wrong. You see the pass rate before anything goes live.

  4. Day 9

    Supervised pilot

    Live with a subset of patients, every conversation reviewed by your staff, escalation path tested under real load.

  5. Day 10

    Handover

    Full switch-on, a walkthrough with your team, and written runbooks for the things you will want to change yourself.

Fixed price, quoted in full on the first call, payable in two instalments. No hourly billing and no change-request meter running in the background.

Scope boundaries

What we will not build

Every fixed-price project needs a clear edge. These are ours, and they are the reason ten days is a real number rather than an optimistic one.

  • Anything clinical

    No symptom checking, no triage, no advice on results, no dosage or medication questions. The assistant is instructed and tested to refuse these and hand off to a human. This is a hard boundary, not a configuration option.

  • Payment collection

    We do not take payments inside the chat in the ten-day build. Sharing an existing payment link is fine; a reconciled payment flow is a separate project.

  • Building an API for your HMIS

    We integrate with what your system already exposes. If your HMIS has no API and the vendor will not provide one, we will tell you in discovery — before you pay — rather than quietly reducing the scope later.

  • Voice calls

    WhatsApp text and media only. Voice is a genuinely different engineering problem and pretending otherwise is how ten-day projects become ten-week ones.

  • Bulk marketing broadcasts

    This is a service channel. Using it to push promotional messages is the fastest way to get a WhatsApp number rate-limited or banned, and we will not build it.

What we need from you

Ten days only works if these are ready. We will tell you in discovery if something is missing.

  • A named person on your side who can answer questions within a day
  • Your existing documents — timings, price lists, preparation instructions — in whatever form they are already in
  • Access to the calendar or HMIS the front desk uses today
  • A morning with your front-desk staff during discovery
  • Authority to complete Meta business verification, which needs your registered business details

Cost, data handling and what happens after handover are answered on the home page.

Is your front desk drowning in the same forty questions?

Fifteen minutes to find out whether this is worth building for you, and an honest answer if it is not.