Appointment information
Share approved locations, hours, specialties, prices, and administrative requirements.
For clinics
An AI administrator for clinics
Administrative tasks only. AI must not diagnose, prescribe treatment, or replace a clinician. Medical questions are handed to a qualified professional.
Registration, Web Chat, server-side AI, Inbox, CRM, and the built-in calendar are part of the current MVP. External calendars, multiple staff schedules, and industry-specific integrations remain future stages.
HexSales / SolutionMVP · working version
One conversation, one business
AI receives approved knowledge from the current organization only.
01
Understand customer intent
02
Ask only for necessary details
03
Answer or bring in a person
A working-flow illustration, not proof of an industry integration
Challenge
Administrative conversations without medical promises
Patients often need an address, opening hours, appointment price, document list, or help rescheduling. Approved clinic knowledge can simplify these conversations while medical questions remain clearly separated and escalated.
Workflows
What works today and what comes next
Answers from business data, contact capture, Inbox, CRM, the built-in calendar, and human handoff are in the working MVP. External integrations and industry data sources remain clearly marked as future stages.
Enquiry capture
Ask for the specialty, preferred location, and time while collecting only essential contact information.
Specialist handoff
Stop automated replies for medical, urgent, or unusual requests and connect a person.
Now
Working foundation
Before launch, each business validates the product with its own data, policies, and real customer scenarios.
- Registration and setup store the organization, profile, services, and business rules.
- Web Chat creates one tenant-scoped conversation and sends messages to server-side AI.
- Inbox and CRM show real messages, contacts, and leads without demo records.
- The built-in calendar shows real availability and prevents overlapping appointments.
- Manual control keeps AI silent until the owner explicitly returns control.
Process
The working flow and future connections
- 1
The clinic approves its services, locations, opening hours, and administrative FAQ.
- 2
AI classifies the request as administrative, medical, or requiring a person.
- 3
For an administrative enquiry, it confirms the specialty, location, time, and contact details.
- 4
AI books in the primary calendar only after checking the exact slot and receiving explicit patient confirmation.
- 5
Actions remain available in the activity history for clinic staff oversight.
Guardrails
What AI must not do
Server-side AI receives these limits with the business rules. The owner must validate industry-specific policies before serving customers.
- Never diagnose, interpret symptoms, or prescribe treatment.
- Never promise a medical outcome or conceal the limits of an answer.
- Minimize sensitive-data collection and hand medical questions to a person.
FAQ
An honest view of what works today
No decorative promises and no claims about features that are not available.
Can HexSales advise patients about symptoms?
No. The intended flow is limited to administrative tasks. Questions about symptoms, diagnosis, treatment, or urgency must go to a qualified medical professional.
Does automatic clinic booking already work?
Yes, for configured services in one primary clinic calendar. AI first verifies the exact available slot and books only after explicit patient confirmation. Separate doctor schedules and external calendars are not connected yet.
Can answers be limited to approved wording?
Business settings and knowledge limit the AI context, while handoff rules define when a person is required. The clinic must review medical and other sensitive scenarios before launch.
How does HexSales handle personal data?
The system is designed around tenant isolation, data minimization, audit records, and server-side secret storage. Each clinic remains responsible for establishing the applicable legal basis and processes before handling real patient data.
Early access
Start with a real workflow, not a polished demo metric
Add your services, policies, and common questions, then verify answers in Web Chat. External channels become active only after separate server-side verification.