AI customer service and order bots for Telegram, WhatsApp and your website

One path from the question to a person

Customers ask on Telegram, on WhatsApp or on your site. The replies are slow because the facts live in a price list, a PDF or someone's head, and the order is copied by hand into another tool. An assistant can take the first pass. It does not replace the person who owns the customer.

The path we scope is short. The assistant answers from the material you provide. It recognizes an order or a lead in the text, a photo or a sheet. It writes the agreed fields to a sheet, Notion, a CRM or another system that actually has an API. It notifies the owner. If it cannot find the fact or is not sure, it hands the case to a person and says why. That sequence is the acceptance test, not a slogan.

Telegram is the platform of the public demos, described on the Telegram bot page. WhatsApp uses Meta's Cloud API and is described on the WhatsApp page, including the message fees Meta bills to you. A chat on your own website can follow the same answers and the same handoff. There is no separate website-chat page yet, so that channel is named in the form.

How wrong answers are kept out

The assistant is not invited to be general knowledge. It answers from the price list, the documents and the rules you hand over. If the material does not contain the answer, the correct behavior is to say so and pass the question on, not to invent a price, a stock figure or a policy. The owner is notified when that happens.

Before launch we agree a list of questions: ones the material answers, ones it must refuse, and ones that should always reach a person. The bot is checked against that list. A later change to the price list is a content update with the same checks, not a new personality.

The person who receives the handoff sees the question, the bits the assistant already collected, and the reason it stopped. They do not have to re-ask the customer for the order number or the product name if those were already clear.

Systems it can write to

Sheets, Notion, a CRM or a store admin are possible destinations. They are assessed, not claimed as integrations we have already switched on for a client. The check is practical: is there an API, can you grant access, which fields move, how often, and what happens when the other system is down or rejects a row. Those answers go into the acceptance checklist.

Two things on this site are related and are ours, not a client's. Inquiry notifications are the real internal step that tells a person a form was saved; the home page shows an illustration with sample data and sends nothing. The record export shows saving a row and downloading a CSV. It does not connect to Google Sheets or a CRM. It is a picture of the 'write it down' step, not a finished connector.

Price and what stays extra

Custom development starts at US$500. Price depends on how many features you need, which platforms and external systems it connects to, whether it takes payment, and whether it includes a Mini App. The quote is written after a free assessment of the scope. About two to four weeks is a planning range, not a promise, because access to the CRM or the store admin is often the slow part.

AI calls are billed to you at the usage of the model you choose. If the channel is WhatsApp, Meta's per-message fees are also yours, as described on the WhatsApp page. Hosting, if you want the bot kept running, is a separate monthly fee, priced by complexity.

More than one language is possible when you can provide the price list and the policies in those languages, or you explicitly accept translation of the material you supply. The assistant should not be the only translator of a price. The question list used for acceptance should include each language you expect customers to use.

Work we do not take

We do not take gambling, adult content, fake engagement or account farming, spam, or scraping that bypasses captchas or logins.

Questions about the assistant

Will it invent an answer?

It answers only from the price list, documents and rules you provide. Anything missing or uncertain goes to a person, and the owner is notified. We test an agreed question list before launch.

Can it connect to the tools we already use?

Only if the tool has an API and you can grant access. Fields, frequency and errors are written into the acceptance checklist. A named product is not a claim that it is already connected.

Can it work in more than one language?

Yes, when the source material exists in those languages or you accept a translation of what you supply. The acceptance questions should cover each language.