Approved information
Services, hours, locations, policies, appointment rules, and approved answers are documented with the business.
Trust & data
Clear boundaries before a call goes live.
Every deployment starts by defining the information the assistant may use, the details it may collect, and the situations that must be handed to a person. This page explains that operating approach and the website's current data flow in plain language.
This is operational information, not a certification or a substitute for the terms agreed for a production deployment.
Operating approach
Configure, review, then launch
A dependable call flow needs explicit information, collection, escalation, and test boundaries.
Purpose-limited fields
We agree which caller details are needed for each outcome. The assistant is not given permission to collect unrelated information.
Defined escalation
Unsupported questions, unavailable integrations, requests for a person, and scenarios outside the approved flow move to a message or transfer path.
Pre-launch testing
Selected languages and realistic booking, message, transfer, and fallback scenarios are reviewed before launch.
Website enquiries
The website fails visibly when a request cannot be delivered
The public website is hosted on Vercel and asks only for the details needed to review and respond to an enquiry.
- Contact and demo forms collect the request details shown on the form and send them through server-side delivery routes.
- Each submission receives a unique ID and timestamp. If every delivery route is unavailable, the site reports an error instead of showing a false success.
- Requests are checked for origin, size, format, automated submissions, and excessive repetition. Additional server-verified bot protection can be enabled.
- The site uses Vercel Analytics for page and conversion measurement. Form contents are not included in this application's custom analytics events.
Deployment-specific facts
Provider, recording, access, and retention details are confirmed per customer
Voice deployments can use different call flows and integrations. These details belong in the agreed deployment scope instead of a blanket website claim.
- Active telephony, voice, scheduling, messaging, and infrastructure providers
- Whether calls are recorded and the caller disclosure used
- Where call outcomes are delivered and who can access them
- Retention and deletion schedule
- Languages and scenarios tested before launch
Sensitive and regulated workflows
Requirements for health, payment, financial, legal, or other sensitive data must be reviewed before commitment. This page does not claim SOC 2 certification, HIPAA or PCI DSS compliance, or universal compliance with GDPR, KVKK, CCPA, or other laws.
Need a data or security review?
Tell us which systems, locations, languages, and data types your workflow uses. We will answer with the deployment-specific facts we can verify.
Ask a data question