
Let customers and staff act without opening the whole back office.
Kelvia uses scoped customer verification, authenticated staff channels, and email sender authentication so routine changes can happen safely: customers move appointments, doctors see their own day, and the company keeps control.
What this changes for the business
The useful part is not more passwords. It is fewer interruptions, fewer mistakes, and fewer broad admin logins for everyday operations.
Customers fix simple booking issues
Verified customers can look up, cancel, or reschedule their own eligible appointments with explicit confirmation before anything changes.
Professionals handle their own calendar
Linked staff can see assigned appointments, prepare for the next customer, block their own availability, and add notes to assigned bookings.
Email becomes a usable identity signal
DMARC/SPF/DKIM-authenticated senders matched to known customer email contacts can unlock profile-scoped self-service and memory without an OTP.
Every action is verified against its resource
To cancel or change something, Kelvia verifies that specific booking — not broad access — and on a shared company phone it never assumes who is calling before confirming the person.
Voice and messaging customers
The phone number is only a hint, never a proof. Kelvia verifies with a temporary code before showing or changing private data; on apps like WhatsApp it can recognize the already-verified account and skip the code.
Staff contact methods
Verified email, SMS, WhatsApp, Telegram, push, webhook, or XMPP contact methods can authenticate staff for routing and assigned-scope operations.
Inbound email
The email channel handles customer threads, draft-first or safe auto-send replies, and authenticated sender matching for known customer profiles.
Caller ID is not authentication.
Kelvia lets customers check, cancel, or reschedule their own appointments, but those tools are gated behind temporary verification and explicit confirmation for sensitive changes.
The channel phone number or typed phone is treated as a hint, not proof.
Kelvia sends a temporary code with request_customer_verification_code.
After verify_customer_code succeeds, the customer becomes verified for scoped self-service.
Cancellation or rescheduling still requires an explicit confirmation step before the booking changes.
Own bookings only
check_my_appointment looks up appointments by phone only after explicit customer verification and never for third parties.
Sensitive actions confirmed
cancel_my_appointment and reschedule_my_appointment require confirmation, ownership checks, and active booking status before execution.
Audit trail
The booking module marks cancellation and rescheduling as sensitive actions, with verification and changes recorded for review.
Staff absences block the right calendar slots — without turning Kelvia into HR software.
Managers and linked professionals can record a full day, date range, or same-day unavailable window. Kelvia applies it to booking and staff routing; leave policy, balances, approvals, payroll, and medical records stay in the workforce system that owns them.
Choose a full day, an inclusive date range, or a same-day time window.
Kelvia previews any confirmed appointments affected before the block is saved.
If appointments are affected, a second explicit confirmation is required; Kelvia never cancels or reassigns them automatically.
Shared calendars show only that the professional is unavailable, without exposing the category or private note.
Scoped self-service
A linked professional can manage only their own availability. Managers retain the team-wide scheduling view.
An operating fact, not an HR file
Kelvia stores only what its booking engine needs. It does not calculate leave balances, run approvals, process payroll, or hold medical documents.
Ready for future connectors
A provider-neutral integration boundary is ready for a future connector to import approved availability from workforce software. No connection to a specific HR provider is claimed today.
Give the front desk fewer small fires.
Keep humans in charge of exceptions while Kelvia handles verified routine changes across calls, chat, and email.

