A useful first answer
Make reviewed services, policies and common questions available at the point of enquiry.
KAI by AllSocial · In development
We’re building KAI to answer website enquiries using your approved business information, organise leads, and bring your team into the conversation with the context they need.
A focused pilot. A bigger connected-business ambition.

Approved information, with a clear boundary.
What needs my attention?
Ava’s hotel website enquiry is ready to review. Her spring launch requirement stays with the conversation.
Real owner views require a verified account. Messaging-channel access is planned.
ONE ENQUIRY, WITH ITS CONTEXT
Follow Ava’s hotel website enquiry in the demo above. Her requirements stay attached as the team takes over.
Use the services and policies your business has approved.
Save Ava’s contact details and spring launch requirement.
Pause KAI and give a named person the full conversation.
Show the owner what is waiting and what happens next.
PRACTICAL BY DESIGN
Start with the work around an enquiry, then build from there.
Make reviewed services, policies and common questions available at the point of enquiry.
Keep the customer’s request with their contact details, rather than reconstructing it later.
Let your team accept, reply and decide when the assistant can continue.
KNOWLEDGE, CONTROL & BOUNDARIES
The assistant is useful when its boundaries are clear.
Review FAQs and text/Markdown sources. Edited sources return to draft.
Ask for a person, pause the assistant and reply through the web dashboard.
The provider is configured; API billing credit and live answer validation are still required.
The demo uses fictional sample data. It does not send messages, book appointments or establish production availability.
A PILOT STARTS WITH A CONVERSATION
Bring your FAQs, enquiry journey and the person who will handle follow-up. We’ll use them to discuss a bounded pilot.
Product evidence, not customer results. The current pilot has passed scoped authorization and hosted enquiry/handoff checks. No customer performance claims are being made.
View readinessFOR BUSINESS OWNERS
Use the mobile web dashboard today. See the distinction between customer handoffs and planned owner messaging.
Explore owner accessFOR AGENCIES
Separate client workspaces, approved knowledge and explicit responsibilities. Resale features are phased.
Explore the agency path77 capabilities across 11 areas remain part of the wider direction. Explore their individual status.
A FEW GOOD QUESTIONS
The useful details, without the launch-day promises.
KAI is in development. The hosted pilot has a bounded website-chat, enquiry and team-inbox workflow. The wider roadmap is not a list of released products.
Your team supplies and approves FAQs and text or Markdown sources. Editing a source returns it to draft. This is controlled business knowledge, not automatic retraining of an AI model.
The pilot supports takeover in the website chat and web dashboard. The assistant pauses when a person is requested. Availability and follow-up expectations must be agreed with your team.
Those channels are planned. The responsive owner dashboard works on a phone. WhatsApp Business and Apple Messages for Business require separate provider setup; personal iMessage is not connected.
START WITH ONE USEFUL WORKFLOW
Tell us what customers ask, what your team needs to know, and where a person should step in.