How it works

Your clinic's AI front-desk, end to end

Ginivo reads a clinic's website, learns its services, answers every client instantly, and books real appointments — like a trained receptionist that never sleeps and never makes things up. Here's the whole process.

The flow, in six steps

1

Scan the website

The clinic pastes its website URL. Ginivo crawls the pages safely (SSRF-guarded — it can't be tricked into reaching internal systems).

2

Learn the business

An AI extraction pass turns the raw pages into structured, editable knowledge: services, prices, durations, staff, hours, policies and FAQs.

3

See the magic moment

Immediately — no login — the owner chats with an AI front-desk that already knows their real services and prices. That's the proof it works.

4

Answer clients 24/7

On the live website widget, every client message is answered naturally from the clinic's own knowledge. Never invents a price, hour, or service.

5

Book into the calendar

When a client wants to book, the system shows real open times. The client taps one and it's written into the clinic's own calendar — double-booking is impossible.

6

Hand off + track

Medical, complaints, or 'talk to a human' are flagged to staff with a summary. The owner sees every conversation, booking, and escalation in the dashboard.

Where the AI is used — and where it isn't

The AI is the language brain. Everything that touches money or the calendar is deterministic code. That split is why it's safe in front of real clients — a wrong sentence can't become a wrong appointment.

The AI does

  • Understand the message. Detects intent (pricing, booking, complaint, human request…) and writes the natural reply.
  • Read the clinic's knowledge. Pulls the right facts from the extracted services / hours / policies.
  • Decide to hand off. Flags medical / complaint / human-request and writes a staff summary.

Code does (never the AI)

  • Pick available times. Done by code reading the real calendar — not the model.
  • Write the appointment. A guarded database transaction books it; a DB rule blocks any overlap.
  • Send anything. No emails/texts are claimed unless actually sent.

The seven trust rules

Non-negotiable. Each one protects client trust — the whole product depends on them.

1. No hallucinations

Answers only from what was extracted from the clinic's site. Missing fact → 'the team will confirm', never a guess.

2. No fake availability

Never says 'fully booked' or invents a time. The system surfaces the real open slots; the model never picks times.

3. No fake actions

Never claims it sent a text, email, or invite. It only does what the system actually did.

4. No partial bookings

An appointment is created only with a specific service, time, name and contact — and the client's confirmation.

5. No medical advice

Aesthetic-safety questions get general info only, then a handoff to a clinician.

6. Human always wins

If a client asks for a person, Ginivo acknowledges and hands off — every time.

7. Source-bound

Prices, policies, hours and service details come only from the clinic's knowledge base.

Its own calendar — double-booking is impossible

Ginivo runs a real calendar per clinic. Availability respects working hours, service duration, buffers and timezone. When two people try to grab the same slot, the database itself rejects the second one — not a software check that can be raced, but a hard rule at the data layer. The client who lost the race is simply offered the next open time.

Running it day to day

Home

Setup checklist + today's numbers (conversations, bookings, handoffs).

Calendar

Every appointment on a week view; add or cancel with one click.

Conversations

Inbox of AI chats by status: booked, needs-human, resolved.

Bookings

Booking requests captured when a client didn't finish on the spot.

Escalations

What the AI flagged for a human, with the reason.

Knowledge

View / edit / publish services, prices, FAQs, policies.

Services & Staff

Add, edit, delete — deletions persist (no ghost records).

Hours & Settings

Working hours, timezone, brand tone, slot length, buffers.

Embed / Go live

The one line of code the clinic drops on its own website.

What's live now — and what's next

Live in this MVP

  • Website chat widget (the recommended, lowest-risk V1 channel)
  • Website scrape → AI knowledge extraction → editable knowledge center
  • No-login magic-moment demo on real data
  • Source-bound AI agent with all 7 safety rules + human handoff
  • Own calendar: real availability, tap-to-book, DB-enforced no double-booking
  • Self-serve signup, onboarding wizard, full owner dashboard
  • Multi-tenant from day one (each clinic's data fully isolated)
  • Cancel / reschedule, rate-limiting, embeddable widget + one-line script

Built to add next

  • Instagram & WhatsApp. Channel layer is built channel-agnostic; these plug in once Meta access is approved.
  • Google / Outlook calendar sync. Today Ginivo runs its own calendar; external-calendar sync is the next integration.
  • Email / WhatsApp notifications. Built in and switchable — turned off until an email key is added.
  • Roles, internal admin, deep analytics. Owner role ships now; staff roles, a Ginivo-admin console, and a full analytics funnel come next.

Channels, AI provider and calendar are deliberately modular — each of the "next" items plugs into the same engine without a rebuild.

See it on real data

Paste a clinic URL on the home page and watch Ginivo learn it in seconds.