Questions sellers ask before the first call.

A natural Bangla voice greets the customer, introduces itself with your company name, reads out the order (the items and the total) and asks whether to confirm it. It then reads back the delivery address and asks the customer to confirm or correct it, thanks them, and ends the call.

The voice speaks the way people in Bangladesh actually talk: Bangla, English, and the mix in between. You can listen to any call afterwards; every one is recorded.

The call is tried again on a schedule. The number of attempts is set per account, up to 10. If nobody answers on any attempt, the order is reported as a hold with the reason "no answer", so a person can decide what to do. Unanswered calls are not charged.

The agent records what the customer said and reports the order as a hold, with a reason (cancelled, modified, wrong number, and so on) and a one-line summary such as "the customer placed the same order twice by mistake". Your staff review holds; the service never cancels an order on its own.

A corrected address is reported separately: the address you sent is never overwritten, and the thana and district the customer said are returned beside it.

Most confirmation calls finish in under a minute. A call that passes 2 minutes without a clear decision is ended and reported as a hold, so a confused conversation cannot run up your balance.

A local Bangladeshi number. Calls go out through a Bangladeshi carrier, so the customer sees a number they will actually pick up, not a foreign one. Accounts on the service can be given their own dedicated number, which customers can save and call back; a call back is answered with a short recorded notice that a staff member will follow up.

Bangla first. It also understands English and the everyday mix of the two, and it hears a Dhaka address the way a courier would: thana, area, road and house.

Your system sends each order to one endpoint, and receives the result on a webhook when the call ends. Both are documented on the docs page with a working example. Most teams wire it up in an afternoon.

Before any real customer is dialled, you get a staging assistant pointed at your own phones, so you can run the whole loop yourself.

To connect a store to the API, yes, for about an afternoon. If your orders live somewhere without an API, message us and we will look at what fits.

Our team configures the assistant for your business: the greeting, the questions it asks, the voice, and how it handles your kind of orders. We keep tuning it as your calls come in. Tell us what should change and we change it; there is nothing for you to install or maintain.

Yes. Upload your documents and policies, and customers can start a browser voice call or a text chat with the same assistant. Its answers come from what you wrote, with the source shown. On an order-confirmation phone call, the agent answers from the order details you sent with the request.

You buy minutes in advance and they are used by the second, only while a customer is on the line. Order-confirmation calls cost ৳4 per minute; other requirements are priced to fit. Signing up gives 2 free minutes, with no credit card. The dashboard shows a live ledger of every call and top-up, and your webhook receives a warning when the balance runs low. When it is empty, calls wait until you top up.

Every call is recorded so a disputed order can be checked. Recordings are kept for 90 days and then deleted. The one-line note and the result stay with the order. Telling your customers that calls are recorded is your responsibility as the business making the call.

Yes. Each business is its own organization with its own members, roles, assistants, balance and call history. API keys are issued per environment and can be revoked one at a time. An agency running several clients keeps each one in its own organization.

From Dhaka, Bangladesh, with calls placed through a Bangladeshi carrier. The team that builds and tunes it is in Dhaka too.