An open-source agent that answers from your manuals and policies on web and chat apps, and hands unsure questions to staff.
Example conversationMade-up brand and terms; the answer comes from the manual, and the blue chip is a logged call the customer doesn't see.
Three things every business with a manual runs into.
Error codes, warranty, opening hours. The answer is on page 14 of a PDF, and staff type it again.
A general bot confidently promises a warranty term you never offered. Then you honour it or apologise.
Vector database, ingest pipeline, chat channels and a handoff inbox, all before the first answer.
Every message is kept. The agent searches its own documents, answers from what it finds, and passes unsure chats to staff.
Customers ask on
Every message kept
Answered in turn
Your knowledge agent
One setup, every channel
The agent answers
Upload PDFs, Word files, Markdown or web pages. Ecbot stores them in Postgres with pgvector, searches by vector and full text, then reranks.
Customer question
“E3 error on the AH-IC22, what does it mean?”
Searched by the AnHome support agent
Not linked to this agent
Passages the model answers from
Postgres + pgvector, on your server if you self-host
The agent hands over when it isn't sure, the customer asks for a person, or a keyword or guardrail fires. Staff reply in one inbox.
The agent hands over when
It's 26 months old, but I bought the store's 3-year extended plan. Does that count?
That plan isn't in our warranty documents, so I'm passing you to our warranty team.
Handed to staff: The agent isn't confident
The manual says what's covered; your system knows if this serial is. Connect REST, MCP or Composio tools, and every call is logged.
| Time | Tool | Input | Result |
|---|---|---|---|
| 21:41 | set_customer_fieldEcbot · model · AH-IC22 | model · AH-IC22 | OK |
| 10:02 | check_warrantyREST API · serial AH22-0457 | serial AH22-0457 | OK |
| 10:03 | book_technicianMCP · District 3 · Sat 9:00 | District 3 · Sat 9:00 | OK |
| 10:03 | schedule_followupEcbot · in 3 days · repair check | in 3 days · repair check | OK |
| 16:05 | check_warrantyREST API · serial AH19-1102 · timed out | serial AH19-1102 · timed out | Error |
Ecbot keeps one profile per person across website, Zalo, Messenger, WhatsApp and Telegram. A shared phone or email suggests a merge your staff confirm.
Merge suggested
The Telegram profile “@trangpham” uses the same phone number as Pham Thu Trang.
Pham Thu Trang
09xx xxx 457 · trang.pham@example.com
Contact points
Staff notes
Bought the store's 3-year plan. Prefers a Saturday morning visit.
Playbooks, no dropped messages, and follow-ups after a repair.
Write your warranty process in markdown. The agent loads it only when a chat needs it.
# Warranty claim 1. Ask for the model and serial number 2. Check coverage with check_warranty 3. Ask for a photo of the receipt 4. Outside the policy: hand to staff
Every message is kept and answered in turn, even when 50 arrive at once.
+50 messages at once
Set a follow-up from 1 minute to 30 days out. The agent rereads the chat and writes a fresh message.
- Technician booked: check the repair 3 days later
Sat 9:00
Technician visit for AH22-0457
Tue 9:00
Agent: “Is the cooker working well since the repair?”
Customer: “all good”
The agent thanks her and stops
Start with one manual and test it privately before customers see it.
The agent builder suggests a persona, tone, goals and rules. Edit what's off.
Describe your business
Home appliance brand answering warranty and error-code questions on our website and Zalo
Suggested by the agent builder. Edit anything.
PDF, DOCX, TXT, HTML or Markdown up to 5 MB, web pages or notes.
In Postgres with pgvector, on your server if you self-host
Tools the agent can use
ComposiomarketplaceEmbed the widget, connect Telegram or call the REST API. No platform approval needed.
On the roadmap: Instagram, TikTok Shop, Shopee, LINE
How Ecbot guards credentials, screens messages and keeps businesses apart.
Platform tokens use AES-256-GCM with versioned keys, so keys rotate without taking channels offline.
Credentials never enter the model's context, so no prompt can pull them out.
Incoming messages are screened for scams and prompt attacks, replies for leaked data. You set the strictness.
Each business gets its own workspace. Staff join by invitation with a role, checked on every request.
Open source. Self-host it if you want.
On GitHub under AGPL-3.0, with every Cloud feature. Your knowledge stays in your own Postgres.
It's an AI agent that answers customers from documents you add: manuals, policies, price lists and web pages. It runs on your website, Zalo, Messenger, WhatsApp, Telegram or REST API, and hands unsure chats to staff.
Last updated: 2026-09-22
Join the waitlist for Ecbot Cloud, or self-host the open-source version today.
Or self-host the open-source version from GitHub