Askcord turns your returns policies, warranty booklets, spec sheets, and manuals into a support bot on your own WhatsApp or Telegram. Your customers ask in plain language and get answers built from your documents — never invented. No fine-tuning. No engineering project.
E-commerce, automobile, technical documentation, and more — each business gets its own knowledge base, its own bot, and its own voice, and one business's documents can never surface in another's answers.
Return policies, warranty terms, spec sheets, installation manuals — all written down, all buried. So the same questions land in your inbox every day. Generic chatbots hallucinate because they don't know your documents, and building retrieval in-house means vector search, extraction pipelines, channel integrations, and access control before you answer a single question.
The same twenty questions arrive every day, and an agent types the same answers every time.
A confident wrong answer about your warranty or return policy is worse than no answer at all.
Most platforms assume a single deployment — serving ten brands or clients means ten builds.
Your team curates. Your customers ask. Nothing to install on either side.
Your admins upload PDFs — policies, warranties, spec sheets, manuals — from the bot or the operator console. Extraction, chunking, and indexing run automatically into your private namespace.
We wire your own Telegram bot or WhatsApp Business number to Askcord during onboarding. You set the assistant's name, voice, and persona.
No signup, no account, no app to install. The number they message is your business — the first message just works.
Upload → extract & chunk → embed & index into your private namespace. Runs asynchronously, so large files never block a conversation.
Ask → retrieve & rerank → answer on your channel, inside the messaging platform's real-time response budget.
Most of what a customer asks is already written down — in a returns policy, a warranty booklet, a spec sheet, an installation manual. Askcord turns those documents into an assistant that answers on the chat app they already have open.
A branded bot on your own WhatsApp Business number or Telegram, answering pre-sales and post-sales questions from your own documents — no queue, no hold music, no wrong answer invented on the spot. When the documents don't cover it, it says so instead of guessing, and the customer goes to a human already knowing what's missing.
Fields we're built for
Return windows, shipping rules, sizing charts, warranty terms.
"Can I still return a sale item after 30 days?"
Warranty booklets, service schedules, spec sheets, finance terms.
"Is the 60,000 km service covered under warranty?"
Manuals, install guides, troubleshooting trees, release notes.
"How do I reset the controller to factory defaults?"
Listing details, lease terms, society rules, handover checklists.
"What's the notice period on this lease?"
Policy wordings, fee schedules, eligibility rules, claim steps.
"What's the prepayment penalty on this loan?"
Package inclusions, cancellation rules, house policies, visa notes.
"Is airport transfer included in this package?"
Not on the list? The assistant is document-driven, not vertical-specific — if the answer is written down anywhere, it can be the knowledge base.
An ops, HR, or support assistant over policies and SOPs — so people stop pinging a human for answers that already live in a document.
Recurring member questions from bylaws, event info, and FAQs — 24/7, in the group's own voice, on the group's own number.
A separate branded assistant per client, all from one system — the same multi-tenant isolation, one bot per customer of yours.
Grounding, isolation, and channel independence are the architecture — not features bolted on later.
Every answer is retrieved from your documents. When a question has no strong match, the assistant says "I don't have that" and points to a human — a customer never gets a confidently wrong policy.
It tells chit-chat from "what do you have?" from "summarise everything" from a factual lookup, and routes each correctly. Casual messages skip retrieval; inventory questions answer from your document list; factual ones get query expansion and reranking.
Each business sets its own assistant name and persona. Customers talk to your brand — Askcord never introduces itself in the middle.
Telegram and WhatsApp today; web and email next. A clean channel seam means new channels never disturb the knowledge layer.
A tenant-scoped admin view: curate documents, register your channels, watch the ingest pipeline, and test answers in a built-in chat playground.
Only recognised admins can upload or delete documents. Customers get answers, never the ability to reshape the knowledge base — safe to put the number on your website.
If you run several brands, clients, or locations, isolation isn't a filter applied at query time — there is no cross-business read path in the system at all.
Each tenant's embeddings live in their own namespace. Retrieval is scoped before it runs.
Channel tokens are encrypted at rest, per tenant. Nobody reads another business's bot credentials.
Every inbound message is authenticated before it's processed — a per-tenant secret token on Telegram, an HMAC signature on WhatsApp.
Who can ask and who can curate is resolved per business, and enforced before any handler runs.
Your documents are used to answer your customers' questions — nothing else. They are never used to train models.
No new app to download, no account to create. Your assistant meets them in the chat app already on their phone.
Full experience: customer Q&A, admin uploads, and document management commands.
Try the live bot →Customer Q&A on your own WhatsApp Business number — where most people already message businesses. Admin uploads land here next.
Talk to us about setup →Web widget and email are next on the roadmap.
Two roles, resolved automatically. Your staff are recognised as admins the moment they message the bot; everyone else is a customer who can ask, and only ask — so a public number is safe to hand out.
Your staff, pre-registered in the console
Admin accounts carry the person's messaging username, so your staff get elevated access the moment they first message the bot — no separate login to hand out.
Anyone who messages your number
A customer who tries an upload or a command gets a friendly reply in your assistant's own voice, never an error screen.
We build in the open. Here's exactly where the product stands.
Send us a sample of your documents and the questions your customers ask most. We'll stand up an assistant on them, so you can judge the answers rather than the pitch.
Or try the live bot on Telegram first — no email required.