Integrations · 14 entries
Nobody wants a second system. The books are already somewhere, the retailers are already in a group, the counter already has a scanner. What follows is what the conversational layer plugs into, and what stays exactly where it is — because the answer a buyer gets should not depend on which pipe carried the question.
The systems that hold your catalog, prices and stock — Tally, Marg, Busy, a Google Sheet, or your own database over an API — and the surfaces a buyer reaches you on. The same core answers on every one of them from the same data, so a question asked in a WhatsApp group and the same question asked in your app do not get two different answers.
WhatsApp and the website are live today. The rest is a connector, not a second product.
The books stay where they are, and nobody learns a second system
— the accountant does not leave the screen they live in
What you'll observe
The draft order appears where the accountant already works, matched to real Tally ledgers and stock items. Posting is a decision they make, not something that has already happened by the time they look.
— where a great deal of Indian B2B actually keeps its catalog
What you'll observe
A sheet is a perfectly good catalog and is treated as one. Prices and stock are read from it as they stand, so the answer changes when your sheet changes and not when somebody remembers to re-upload.
— the app your retailers already have on their phones
What you'll observe
The same conversation, embedded in your app, answering from the same catalog. A retailer who asks in the app and then asks again on WhatsApp is talking to one agent with one memory, not two.
— the conversation opens mid-history, not at hello
What you'll observe
The scan identifies the buyer, so the conversation starts knowing what they have bought before. They do not re-introduce themselves to a shop they have used for nine years.
— where it must answer only when it is addressed
What you'll observe
It stays silent in the group until somebody addresses it, then answers that person about their own rates. A group is the one place where answering a question nobody asked you is a serious mistake.
Tier pricing in a group of competitors is the sharp edge: the reply goes to the person who asked, and their rate is not broadcast to the other hundred and ninety-nine.
WhatsApp and the website are live today — each of these is the same core pointed at a different pipe, and what changes is the connector rather than the answer
What you'll observe
A marketplace lead is a buyer who is still shopping. The answer that matters is a real price on a real item in their language, before the other three suppliers open.
What you'll observe
Highest-intent message a shop receives: they found you and they want one fact. It is answered as a shop question, not routed into a sales sequence.
What you'll observe
An enterprise RFQ wants a quotation against line items, not a chat reply. The same catalog and pricing answer it, in the form the purchase department can actually put into their file.
What you'll observe
The order arrives structured rather than typed, which removes the reading problem and leaves the catalog, price and serviceability questions exactly where they already were.
What you'll observe
Where a trade already has its channel, the layer goes to it. Asking a market to migrate for your software's convenience is how software gets ignored.
What you'll observe
Prices and buyer names belong in the DM, never in the public comment thread. The distinction is the whole design problem here, and it is a governance question before it is a channel one.
What you'll observe
A driver on a feature phone is not a lesser user. Text is a small enough surface that the answers have to be short and unambiguous, which is a discipline worth having anyway.
What you'll observe
Speech removes the reading problem and adds a harder one: there is no scrollback, so anything uncertain has to be said aloud at the time rather than left for the buyer to notice.
What you'll observe
Internal is a different permission set, not a different product. Your team sees what your team is allowed to see, which is more than a buyer sees and less than an owner does.
No — the point is the opposite. Your books stay where they are and the conversation drafts into them. Marg is read-only by design, and Tally write-back stays off until you switch it on.
That is a supported catalog, not a problem to fix first. A great many working businesses run on a sheet, and requiring an ERP before you can answer a buyer's question would be solving our problem with your money.
No. The catalog, pricing rules and escalation policy are the agent — the channel is where the conversation arrives. Adding a surface does not mean re-teaching it what you sell or what it is allowed to say.
Ask it: “Do you work with Tally?”
You're talking to the product. Nothing you send is added to any business's catalog.