Apps
AI Chat
A chat assistant for your website that answers from your own help material, cites its sources, and hands over to a person when it should.
What it does
AI Chat adds a launcher and chat panel to your site. Visitors ask questions; the assistant answers from the knowledge pack you write in the console and cites the article it used. When the pack has nothing relevant it either answers from general knowledge with a visible label, or — in Grounded only mode — offers your support form instead of guessing.
Your team can step into any conversation from the console. While a person holds the thread the assistant stays silent.
AI Chat is delivered by the Engage SDK — one script tag, a publishable key, and a per-site origin lock.
Features
| Feature | Detail |
|---|---|
| Grounded answers | Retrieves matching articles per question and cites them in the reply. |
| Website knowledge | The guided app setup accepts up to 20,000 characters of website knowledge. Existing article-backed integrations retain their API-managed articles. |
| Answer modes | Grounded with general fallback (labelled) or Grounded only (declines and offers support). |
| Human takeover | Take over or Reply silences the assistant; Return to assistant resumes it; Close ends the thread. |
| Escalation steering | Billing, refund, legal and account questions are pointed to your support form and reported to you as chat.escalated. |
| Visitor identity | Anonymous by default, or require an email before the first message. |
| Guided configuration | Assistant name, greeting, website knowledge and human-handover preference. |
| Privacy | No cookies or trackers. A random visitor token in localStorage lets a conversation resume. |
| Safe by default | The widget renders nothing if the key, origin or site is wrong — no broken launcher. |
How it works
- The SDK calls
GET /v1/engage/configwith your key. If the site is active and the page's origin is allow-listed, the launcher renders. - Each message is posted to
POST /v1/engage/chat. Buckhy retrieves matching articles, answers with citations, and stores both sides of the conversation. - If the message mentions billing, refunds, legal or account actions, the answer also points to your support form and Buckhy attempts the configured
chat.escalatedwebhook. - When you reply from the console, the thread's status becomes agent: visitor messages are stored and shown to you, and the assistant stays silent until you hand back.
Get started
- Open Businesses, add or select your website, and verify domain ownership. Choose Test for local development or Live for your production website.
- Open Apps > AI Chat > Configure. Set the app's fields and exact allowed origins. HTTP localhost origins belong only in Test.
- In Integrate, create or reuse the environment's Engage credential. Keep one SDK loader when another Engage app is already installed:
<script src="https://api.buckhy.com/v1/engage/sdk.js" defer
data-site-key="bk_live_…"></script>
Complete the Chat interaction below, then open Test, run the checks and continue to Activate. Creating a credential or copying this snippet does not complete activation. 4. In Configure, add website knowledge: what the business does, hours and headline policies. 5. Load your site and ask a question covered by that knowledge. Review the answer and the website's Inbox > Chat, then finish Test > Run checks > Activate.
Framework install, verification and a copy-paste AI-agent prompt: Install the Engage SDK.
Configure
Open Businesses > your website > Apps > AI Chat > Configure. Use the website's Settings > Assistant for its existing shared Engage connection. Preparing changed Live settings can affect visitors before final activation; review the confirmation in the Integrate step.
| Setting | Effect |
|---|---|
| App status | Enable, disable or remove AI Chat from the Apps page. |
| Human handover | Offer support when the knowledge does not answer a question. |
| Assistant name and greeting | Identity and opening text for the panel. |
| Website knowledge | Up to 20,000 characters in guided setup. |
| Allowed origins | Exact origins for the selected environment; HTTP localhost is Test-only. |
Guides
Write a knowledge pack that answers well
- Put policies in the context; put procedures in articles. Keep the context to what every answer should know.
- One question per article. The operative fact goes in the first sentence.
- Titles carry the most weight in retrieval; tags add recall. Use the words a visitor would type — refund, size exchange, parking.
- Test with real questions after each change; the 5-minute cache applies to config, not to knowledge used per message.
Take over a conversation
Open Businesses > your website > Inbox > Chat. Open a conversation and choose Take over, or send a Reply, to enter human mode. Return to assistant resumes AI replies; Close ends the thread. Use assignment to make responsibility explicit.
Handle escalations
When a visitor mentions billing, refunds, legal matters or account actions, the assistant points to your support form. A configured chat.escalated webhook includes the conversation ID, page and message; verify your receiver's acknowledgement before treating it as delivered.
Build a custom chat UI
Skip the launcher and call the API from your own interface: POST /v1/engage/chat with message, then reuse the returned visitorToken to continue the thread, and GET /v1/engage/conversations/:id?visitorToken=… to render history. Details: Engage API → POST /chat.
Reference
| Topic | Page |
|---|---|
/config, /chat, /conversations/:id — requests, responses, errors |
Engage API |
chat.escalated payload, signature, retries |
Webhooks |
| Rate limits (12 messages / minute per key + visitor) and knowledge sizes | Limits |
| Why the key is publishable; origin lock | Keys · Security |
