Skip to content

Features

How the platform is built

Reliability and depth for facility managers who already know the use cases. Step-by-step call control, booking rules, named safeguards, and a set-up model that makes 24-hour onboarding possible.

Call control

How step-by-step call control works

Most AI phone tools let one instruction set run the whole call. Vgentive breaks each call into clear steps. The system decides what happens next, not free-form AI answers.

    • Step 01

      What does the caller need?

      The first words decide the path: question, booking, emergency, reminder reply, or handoff to staff. Each path follows its own steps, not an open chat.

    • Step 02

      Facts from your setup only

      Timings, doctors, slots, and answers come from what you have set up. If nothing is found, the agent says so. It does not make up an answer.

    • Step 03

      Caller must say yes

      Bookings and sensitive steps need a clear yes from the caller. The agent reads back doctor, time, and department from the booking system only.

    • Step 04

      Call closes with a record

      Every ended call is logged on the Facility Desk with transcript and outcome. Built-in checks run throughout the call, not only at the end.

Booking rules in practice

What the agent is allowed to say

Redacted call excerpt. System results are shown in brackets. The agent does not invent doctors or slots. It does not guess when a lookup fails.

Multi-speciality clinic, anonymised

  1. Caller

    Do you have Dr. Sharma available tomorrow morning?

  2. SystemSystem result

    doctor.lookup → no match for "Sharma"

  3. Agent

    I don't have a Dr. Sharma on our schedule. We have Dr. Mehta and Dr. Kapur in general medicine. Would you like an appointment with either of them?

  4. Caller

    Dr. Mehta, please.

  5. SystemSystem result

    slots.list → 10:30 AM, 11:15 AM (tomorrow)

  6. Agent

    Dr. Mehta has 10:30 AM or 11:15 AM tomorrow. Which works for you?

  7. Caller

    10:30.

  8. SystemSystem result

    booking.create → pending confirmation

  9. Agent

    I'll book Dr. Mehta tomorrow at 10:30 AM. Shall I confirm that booking?

  10. Caller

    Yes.

  11. SystemSystem result

    booking.confirm → confirmed

  12. Agent

    Your appointment with Dr. Mehta is confirmed for tomorrow at 10:30 AM. Is there anything else I can help with?

Illustrative excerpt. Names and times are fictional; behaviour matches production tool-gating rules.

Built-in checks

40+ safeguards, named

Each check is a small rule that runs during a live call. The platform has 40+ of them. Below is a sample grouped by what each protects.

Boundaries

Built with limits, on purpose

A voice agent on a hospital line should know what it isn't. Here's what Vgentive refuses to do, by design.

  • No medical advice

    Symptoms go to a department or doctor. The agent never diagnoses, recommends medication, or suggests treatment.

  • No invented confirmations

    A booking is only confirmed after the booking system succeeds. If it fails, the agent says so. It does not pretend the appointment is set.

  • No invented facts

    If something isn't in your knowledge base, the agent says it doesn't know and offers a callback. It never guesses to sound helpful.

  • No unsolicited outgoing calls

    Reminders, follow-up, and feedback calls only go out when your staff starts them. Nothing dials on its own schedule.

  • No silent failures

    If a call drops, stalls, or hits an error, it's logged and flagged. It is not marked as a clean, successful call.

  • No pretending it's human

    The agent identifies itself as the hospital or clinic voice assistant. It does not claim to be a staff member.

  • No third-party disclosure

    The agent will not share another patient's appointment, diagnosis, or details with a caller, regardless of how the request is phrased.

These aren't gaps. They're the same discipline that makes the rest of the agent's behavior something you can trust on a real patient line.

Set-up model

Every hospital or clinic runs on the same engine

24-hour onboarding works because you change data, not code. The voice engine and built-in checks are shared. Your doctors, hours, and rules are yours alone.

Per facility

What changes per hospital or clinic

Loaded as your data and settings, with no custom code per site.

  • Doctors, departments, and bookable services
  • Hours, holidays, and slot rules
  • Knowledge checklist (parking, insurance, fees, custom facts)
  • Greeting, language setting, and clinic voice
  • Emergency acceptance and transfer rules
  • Incoming and outgoing call types per module

Shared platform

What never changes

The platform every site inherits on day one.

  • Voice engine and speech stack
  • Step-by-step call control and 40+ built-in checks
  • Booking chain: doctor schedule → slots → confirm
  • Safety fast-paths and refusal rules
  • Facility Desk modules, call records, and audit trail

Testing discipline

Built from real production calls

Every safeguard on this page exists because a real call surfaced the problem it solves. We do not ship call behaviour from a whiteboard alone.

  • Scenarios from real recordings

    70+ test scenarios come from anonymised hospital and clinic calls. They cover booking edge cases, emergency language, Hindi-English switches, and schedule mismatches.

  • Checks tied to observed failures

    When a live call exposes a gap, the fix becomes a named check with a replay scenario. It is not a one-off instruction tweak.

  • Language parity before release

    Hindi sites get Devanagari copy. English sites get English-only paths. Both are tested on the same scenarios before release.

This is ongoing review from production calls and scenario replay. It is not a claim that every path runs in a fully automated test suite today.

Facility Desk

What your team controls after go-live

The desk is where staff review calls, manage the doctor schedule, and run outgoing calls, separate from the voice engine that handles the line.

  • Facility Desk modules

    See call quality, full call records, appointments, outgoing call queues, review flags, and credit balance in one login.

  • Team roles and credit controls

    Set who sees call records, spends credits, or starts outgoing calls. Voice pauses when credits run out.

  • One platform, many sites

    Each hospital or clinic gets its own knowledge, doctor schedule, language setting, and emergency rules on shared platform infrastructure.

Recently added

  • Voices you can hear

    Your facility gets a natural clinic voice from an official speaker list. Staff hear a sample before it goes live on the line. Unofficial speakers are not used.

  • Voice stays out of the long settings form

    Changing the speaker is a focused picker on the facility record, so the rest of hospital setup stays short.

  • Low-credit warning

    The Facility Desk shows a warning when a hospital is running low on credits, before calls are affected.

  • True Hindi on generated copy

    Knowledge drafts, campaign lines, reminder wording, and call summaries follow the hospital's language. Hindi facilities get proper Devanagari, not Latin Hinglish. Every scenario is tested in both Hindi and English before release.

Everything the hospital runs from one desk

People, reception, outgoing calls, services list, and access. Scoped to your account.

  • Home

    Overview of calls, outcomes, and quality, including completion and needs-review. Credits: balance and history. View only.

    Overview of calls, outcomes, and quality, including completion and needs-review. Credits: balance and history. View only.

  • People

    Callers who phoned the line. Patients the agent and desk share for booking and follow-up.

    Callers who phoned the line. Patients the agent and desk share for booking and follow-up.

  • Reception

    Call logs with transcript, intent, outcome, and duration. Open a conversation and generate an AI summary (uses credits). Enquiry view. Em…

    Call logs with transcript, intent, outcome, and duration. Open a conversation and generate an AI summary (uses credits). Enquiry view. Emergency when the facility accepts it, with transfer to staff. Appointments: calendar, slots, desk booking, and next available, from the same roster the voice agent uses.

  • Re-engagement

    Campaign lists with agenda, calling window, and desired outcome. People and leads, including CSV upload. The agent records the outcome on…

    Campaign lists with agenda, calling window, and desired outcome. People and leads, including CSV upload. The agent records the outcome on the call.

  • Reminders and scheduled

    Appointment reminders with confirm, cancel, callback, or no-answer. Staff-scheduled calls for follow-up, missed visit, feedback, payment …

    Appointment reminders with confirm, cancel, callback, or no-answer. Staff-scheduled calls for follow-up, missed visit, feedback, payment reminder, or custom, with Call now, reschedule, or cancel.

  • Feedback

    Post-visit patient feedback: ratings, comments, and questions the hospital edits. Alerts on poor scores.

    Post-visit patient feedback: ratings, comments, and questions the hospital edits. Alerts on poor scores.

  • Services list

    Departments and doctors with hours and bookable slots. Knowledge: a checklist of hospital facts (hours, parking, insurance, billing, book…

    Departments and doctors with hours and bookable slots. Knowledge: a checklist of hospital facts (hours, parking, insurance, billing, booking rules, plus custom facts). Not a document-upload chatbot. Staff can ask for an AI draft in the hospital's language.

  • Access

    Users and roles for this facility only.

    Users and roles for this facility only.

  • Facility settings

    Hours, emergency, online, offline, or both, and incoming or outgoing. Turn reception, re-engagement, reminders, and feedback on or off. D…

    Hours, emergency, online, offline, or both, and incoming or outgoing. Turn reception, re-engagement, reminders, and feedback on or off. Desk menus hide what is off. Language for the hospital. The clinic voice is set up for staff, not picked in a long form.

  • Support

    Tickets to Vgentive when the hospital needs help.

    Tickets to Vgentive when the hospital needs help.

  • Branches

    Switch facility if the admin is on more than one branch.

    Switch facility if the admin is on more than one branch.

  • Blocked states

    Suspended facility or zero credits: clear desk screens, not a silent failure.

    Suspended facility or zero credits: clear desk screens, not a silent failure.

Get a facility live

Book a demo. Bring your facility phone line and doctor list. See inbound and outbound healthcare use cases on the Facility Desk.