Every feature

Everything the shop needs, behind one login.

Most of this started as something a merchant was doing by hand at eleven at night: counting a shelf, working out a delivery charge, writing an address on a parcel, remembering who asked for the kurti that sold out. Each one is below, and none of them is a separate subscription.

1 / 7

Answering customers

The part that is awake when you are not. It reads what a customer actually wrote — in whichever of three languages they wrote it in — and answers out of your catalogue rather than out of its imagination.

Bangla, Banglish and English: Customers type all three and often mix two in one sentence. Your catalogue is searchable in all three, so “kurti”, “কুর্তি” and “kurta” all find the same rack. Replies come back in whatever the customer wrote in.
Voice notes, read and answered: A large share of messages here are voice. They are transcribed and answered like any other message, rather than sitting unopened until somebody has a free hand.
Messenger, Instagram and WhatsApp: Three surfaces, one inbox, one catalogue and one connect. An Instagram professional account is reached through the Page it is linked to, so you never sign in twice; WhatsApp runs on the official Cloud API.
Comments answered in private: Somebody asking the price under a post gets a private reply with the real figure — once, because a second one is what Meta counts as spam.
Your own answers, repeated exactly: The questions you answer a hundred times — how long delivery takes, whether a size can be exchanged, where the shop is — are written once, in whatever language you like, and relayed in whatever language the customer used.
“Where is my order?”: Answered from the customer’s own orders, and only ever theirs: a reference printed on a slip is not a password, so quoting one at us does not hand a stranger somebody’s name and address.
Handover, and handback: The moment a person is genuinely needed — a complaint, a request nobody planned for, a customer who asks — the conversation is handed to you and the assistant stops. It picks up again when you are done.

2 / 7

What it is never allowed to say

Any language model will eventually invent a number. So nothing it writes is trusted: every message is checked on its way out, by code, and a draft that fails is rewritten or handed to a person.

No price or stock figure the catalogue cannot support: Every figure in an outbound message is checked against the rows the order pipeline will actually charge from. A draft that says 1,150 when the catalogue says 1,250 does not leave the building.
Nothing sent outside the 24-hour window: Meta’s messaging window is enforced before a send, not discovered afterwards. Outside it, only a message with a tag that genuinely fits — and on WhatsApp, only an approved template.
No “ok”, no “noted”, no bare emoji: A reply that says nothing costs a conversation from your allowance and teaches a customer that the Page does not really answer. Those are dropped rather than sent.
A budget per conversation: The assistant cannot ramble its way through your month. There is a cap on how much it will say in one thread, and a system message — an abandoned basket nudge, a back-in-stock note — is deliberately not counted against it.
Never past your plan: Sends stop at the allowance you are actually on, so a busy Eid cannot quietly become a bill you did not agree to. Prepaid, so there is nothing to cancel.

3 / 7

Orders, and the money on them

An order is the same object whichever door it came in by — a conversation, your website, the counter, or your own integration — and it walks the same states and takes stock through the same ledger every time.

One order pipeline, four doors: Chat, shop front, point of sale and API all produce the same order, and each one records which door it came in by. A report that counts them is counting one thing.
Delivery charges that match your zones: Price by district — Dhanmondi one figure, outside the city another — with a default for everywhere you have not named. Free over a threshold counts the goods alone, not the fee you are about to waive.
Discount codes: Percentage or flat, with a minimum, an expiry and a number of uses. A use is claimed at confirmation and never before, so a basket abandoned with a code in it has cost you nothing, and the last use cannot be taken twice.
Store credit: Money the shop owes somebody, in a ledger of its own so a balance is always accountable. Earned from a refund taken as credit or granted by you, and never applied unasked — it is the customer’s money and they may be saving it.
Returns without rewriting history: The parcel went out and part of it is coming back. Stock goes back on the shelf through the ledger — unless you mark it unsellable — and the refund is recorded against the order, so a sales report shows what the shop actually kept.
VAT, only if you are registered: Off by default, because most shops this size are below the threshold. Inclusive or added, both computed properly, both snapshotted on the order so registering in June does not rewrite May.
A parcel slip the courier can read: A printable page with the address set large and the amount to collect on delivery on a line of its own — the one figure a courier must never have to work out.

4 / 7

Stock, in one ledger

Every sale, return, restock, correction and sync moves stock through the same ledger. That is what makes “the assistant stops offering what the counter just sold” true rather than aspirational.

One movement, one reason, one place: Nothing changes a stock figure quietly. Every movement is a row with a reason on it, which is why a number that looks wrong can be explained rather than argued about.
Combos that cannot oversell: A three-piece set owns no stock of its own: what it shows is what its parts can actually make. Selling one takes the parts, in one transaction, so a combo whose second component ran out takes none of the first.
Goes well with: What you said pairs with a product wins, because you knew a kurti wants a dupatta long before the arithmetic did. Where you have said nothing, what customers actually bought together fills in — and nothing out of stock is ever suggested.
The back-in-stock list: “Ashbe kobe?” used to be answered with a guess or with nothing. Now everyone who asked is written to the moment the shelf crosses back above zero — and the list of who is waiting is the best restocking advice available.
Your WooCommerce or Shopify shop, in sync: Products, prices and stock come across; sales here push back. Anything else connects generically, so a custom site is a connection rather than a project.
One system owns stock: You say which one it is, and only that one writes the figure. Two systems both believing they own it is precisely how a shop sells the same shirt twice.

5 / 7

More places to sell

The catalogue is one thing. How many counters you put in front of it is up to you, and none of them is a second stock list to keep up to date.

A shop front we host: Your own website at an address of your own, laid out block by block from the dashboard, selling out of the same catalogue. Point your domain at it if you have one.
The counter: A point of sale in the dashboard for the customer standing in front of you. It takes stock through the same ledger and charges no delivery fee, because nothing is being delivered — and stock is re-checked at payment, because chat can sell the last two while the basket sits on screen.
An API for whatever you build: A documented REST API over the same catalogue and orders, with tokens that belong to the shop rather than to the employee who set it up — so the integration outlives their notice period.
A nudge for a left basket: One message, ever, per abandoned basket — off unless you ask for it, never while a colleague has the conversation, and silent rather than sending something with a tag that does not fit.

6 / 7

Running the shop

The screens for the decisions that used to be made from whichever piece of paper happened to be nearest: what to order, what it cost, what the month actually made.

Buying stock in: Purchase orders that expect a supplier to send what they have and the rest next week: goods are booked in as many times as they arrive, and cancelling leaves what already came on the shelf, because it arrived.
What to reorder: What is nearly gone, who is waiting for it, and how fast it has been selling — on one screen instead of three. Anything already on an open stock order is left out, so you do not order the same twenty kurtis twice.
Buying prices and real margin: Optional, because plenty of shops do not track them. Where they exist, each sale snapshots what it cost, so a supplier raising their price in March cannot rewrite February’s profit.
Reports that survive a return: Computed from the orders as they stand now, not from running counters: a delivery that fails a week later and a kameez sent back both change what a month made, and only a figure worked out now reflects that.
Staff, with the right doors: Invite the people who work with you. Staff get the inbox, the counter and orders; the shop’s takings and the billing screen stay the owner’s.
Told on Telegram: Handovers, failed sends, low stock and a Page whose token has expired reach whoever should know, in the app they already have open, on the topics they asked for.
The whole dashboard in Bangla: Not a machine translation of an English screen. Words merchants say in English stay in English, written in Bengali script, and words they say in Bangla are written in Bangla.

7 / 7

Built so it cannot go wrong quietly

The things that would cost you a Page, a customer’s trust, or a night of your life if they were an afterthought.

Official Meta APIs, only, ever: The Graph API and the WhatsApp Cloud API. Never whatsapp-web.js, Baileys or browser automation — those are what get a number banned permanently, and no amount of convenience is worth that.
Your shop’s data is your shop’s: Separation is enforced at the query level rather than by a filter somebody remembered to write, and a missing scope fails loudly instead of leaking a row.
Tokens encrypted, never logged: Access tokens are encrypted at rest, travel as headers rather than in an address, and are scrubbed from anything on its way to a log or an error report.
A retried webhook is still one order: Meta retries anything it thinks was slow, and retries are how duplicate orders happen. The same delivery replayed three times produces one message and one order.
Paid in taka, prepaid: Top up with bKash or SSLCommerz. No card on file and nothing to cancel: stop topping up and you drop back to Free.

See all 41 features

Start with the inbox. The rest is already there.

Connect your Page tonight and let it answer one real customer. Everything on this page is waiting behind the same login for the evening you need it.

Connect your Page and try it Pricing

Free for your first 100 conversations. No card, and nothing to cancel.