THE PLATFORM
A conversation that
keeps its context.
Start with approved knowledge and finish with a useful next action. The first KAI workflow connects the customer, the enquiry and the responsible person.
Explore the demo ↗01Approve the information
Add FAQs and text/Markdown sources. Review every source before approval. An edited source goes back to draft; uncertain questions get a fallback rather than an invented answer.
No automatic model retraining, website crawling or PDF ingestion is offered in the current pilot.
02Keep the request with the lead
Capture contact details with consent. Ava’s hotel website refresh and spring launch target stay linked to the original conversation. Retries must not create a second lead.
Lead stages and follow-up tasks work in the dashboard. External CRM sync is not connected.
03Put a person in charge
Request, queue, accept and resolve the conversation. The team sees what has already been said, and the assistant pauses during takeover.
A request is not a promise that someone is online. The business sets its availability and follow-up expectations.
04Give the owner a clear view
Use a verified account to see that business’s saved records and waiting conversations. Scope follows the account’s role and workspace.
Dashboard access is separate from WhatsApp or Apple messaging. Connected-tool writes and automatic outbound messages are not part of this pilot.
READINESS REGISTER
Clear about what works.
These labels refer to bounded capabilities, not to every ambition on the roadmap.
Available for pilotA bounded workflow has been exercised against the hosted service. Access and setup are agreed for each business.
Being validatedImplementation or a connection exists, but a release, provider or operational check remains.
PlannedPart of the product direction. No release date or availability commitment.
Available for pilotApproved FAQ answers
Website answers from reviewed FAQs, with an honest fallback when no answer is available.
Available for pilotEnquiries and lead records
Save contact details with consent and keep the conversation attached.
Available for pilotWebsite inbox and human replies
Ask for a person, pause the assistant and reply through the web dashboard.
Available for pilotSeparate business workspaces
Agency and business permissions, basic display branding and a responsive dashboard.
Being validatedAI-generated answers
The provider is configured; API billing credit and live answer validation are still required.
Available for pilotTracked handoff lifecycle
Requested, queued, accepted and resolved states with a responsible person.
PlannedWhatsApp Business
Customer continuity and verified owner questions require a business channel and provider setup.
PlannedApple Messages for Business
An approved business messaging route; ordinary personal iMessage is not an implemented API connection.
Being validatedPayments and subscriptions
Checkout/webhook code exists. Credentials, offers, entitlements and live verification remain.
Reviewed 2026-11-13. Hosted service checks and release records support pilot claims. Public examples and mock tests alone do not.
START WITH ONE USEFUL WORKFLOW
Let’s talk about
your front desk.
Tell us what customers ask, what your team needs to know, and where a person should step in.
Discuss a pilot ↗