AI Sales Agent

On this page: What it is · What it does · Set it up · Company type · What you offer · How customers complete · Playground · Channels · Rules · Connections · Publish · The chat card · Requests and orders · How customers pay · Exceptions · Troubleshooting

What the AI Sales Agent is

The AI Sales Agent is the part of your chat agent that sells. It finds your offerings, shows them as cards, answers with their real prices and availability, and helps the customer take the next step: buy on your page, place a request your team confirms, or create the order in your own system. It is included with the chat agent on these plans: Free, Starter, Growth, Scale, Enterprise.

Configure it at AI Sales Agent in the sidebar (company admins and teammates with the Sales access). Everything on the settings page is a draft until you publish a revision.

What the Sales Agent does for your customers

What you do: set it up once

1. Add what you sell on the offerings screen, by CSV, by the offerings feed, or let Find what I sell suggest them from your knowledge.
2. Pick your company type and apply its template (section 1).
3. Choose how each kind completes (section 3): Handled in Central AI to take orders in the chat, Live checkout on your site to hand the basket to your own checkout and follow the order live, On our page to send customers to each offering’s page, or (behind the Advanced switch) Created in our system through the Commerce API. Only what your choice needs appears under it.
4. Add your payment methods and write what customers are told for each (section 5; shown when a kind is Handled in Central AI, or live checkout takes Messenger, Instagram and WhatsApp orders in the chat).
5. Publish (section 6), then try it in the Playground exactly as a customer would.
6. Handle the orders in Requests and orders: accept, record payment, mark done.

1. Company type

Pick the closest type and press Apply template to the draft. It fills in sections 2 to 5 for you; nothing is locked, so change any value afterwards. Applying keeps your rules, and leaves off any social channel you have not connected yet.

2. What you offer

Tick each kind you sell and, if you like, say what your customers call it (for example “Course” for Course intake, up to 60 characters). Each kind links to its offerings. The offerings themselves live on the offerings screen.

3. How customers complete

For each kind you sell, choose where the order, booking or application is made. You can use a different option for each kind, and change it any time; the change goes live when you publish.

Only what your choice needs appears under the options: the live checkout box for Live checkout on your site and the note below for On our page. The Advanced switch shows the Created in our system option and the Connection to your system card.

On our page: where its setting is

On our page has nothing to set up in section 3. Each offering’s Page link (on the offerings screen, edit an offering) is where its card’s button goes, for example “Buy on yoursite.com” (the chat card). An offering without an https:// page link gets no button. While a kind is set to On our page, section 3 shows how many of its active offerings have a page link, with a link to the rest.

The chat does not see the order or its payment afterwards. For that, choose Live checkout on your site: one checkout link and one webhook, see Live checkout.

Try it in the Playground

The Playground (Agent & Chat → Playground) runs exactly the agent your customers meet on your website: the same cards, basket and Confirm. Orders placed there are real and appear in Requests and orders with a Playground label, so your team can tell them from customers’. Reject or cancel them there when you have finished testing; a request is never deleted, so its history stays. With Created in our system, a Playground order also reaches your connected system, so cancel it there too.

4. Where the agent sells

Tick the channels: Website widget, Facebook Messenger, Instagram, WhatsApp. Messenger, Instagram and WhatsApp can be ticked once they are connected on Social Channels. The agent sells there only while the integration is active and has a Meta app secret; the page warns you when it has not.

5. Rules and payment

How the agent behaves, and how customers pay for orders handled in Central AI. Prices and availability always come from your offerings, never from these words.

• Payment methods, shown when a kind in section 3 is Handled in Central AI (or live checkout takes Messenger, Instagram and WhatsApp orders in the chat). Pick one from Add a payment method: cash on delivery, bKash, Nagad, bank transfer, or Online payment. Each one you add has a box for what the customer is told after confirming (your number, your account); the cross removes it. See How customers pay. The agent never takes a payment.
• Online payment is for a payment page you already have: an SSLCommerz, bKash merchant or Stripe payment link. Put it in Your payment link; after the customer confirms, the chat shows a Pay now button that opens it, and your team checks that the money arrived.
• Only a company admin (or a Central AI platform admin) can change the payment methods, the payment link and what customers are told to pay to, and, in section 3, the checkout link and the order webhook secret. Other team members with access to the AI Sales Agent see them read-only, so nobody else can point a customer’s money somewhere new.
• Reduce stock when your team accepts an order (off by default; shown with the payment methods): accepting an order in Requests and orders lowers the stock on your offerings (or the free seats of a course or event) by what was ordered; cancelling it before delivery puts it back. Leave it off if you count stock somewhere else.
• More rules, folded away because they are optional: tone, languages and currency; Never promise and Hand over to a person when (one item per line); refund, cancellation and delivery policy links (https).

Connection to your system (advanced)

Turn on Advanced in section 3 and this card appears right under it; it is needed only for kinds set to Created in our system. Where your shop runs: choose My own website, app or booking system (Commerce API) to connect a system that creates orders; see Commerce API. Only a company admin can change connections.

6. Publish

• Agent on, Find and show offerings and Take orders and requests switch the agent and its abilities.
• Save draft keeps your changes without changing what customers see.
• Publish revision N makes the settings live as version N. Customers already in a conversation keep the version they started with.
• The page shows the published revision, whether the draft has unpublished changes, and the last five revisions (who published, when, on which channels).
• Publishing is refused when no kind is ticked (the agent would have nothing to offer), when a kind is set to Live checkout on your site and there is no checkout link, or when a kind is set to Created in our system and the connection has not passed its test.

The chat card and its page button

When the agent shows an offering, the customer sees a card with its name, price (“catalog price”; the final total comes from you), availability and image. When the offering has an https:// page link, the card has a page button. Its wording depends on the kind and on how that kind completes:

• The host is your page link’s own (lower case, without www.), so the customer sees where they are going. A host longer than 63 characters is left off and the button shows only the verb.
• For any other completion mode, or before you publish, the button is a secondary View details.
• No page link, no button. Offerings from your feed or a connected system also show when they were last updated.

On Messenger, Instagram and WhatsApp the same offerings arrive as a numbered list; see Social channels.

Requests and orders

Requests and orders lists what customers asked for through the agent. Nothing is confirmed to the customer until you accept it. Tabs: Waiting for you, Accepted, Rejected and cancelled, All. On a request you can:

• Accept as it is, or Accept with a change instead: the customer gets the change with a code to accept it (valid 7 days). You can withdraw a change.
• Reject or Cancel.
• Record payment (with its reference, such as a bKash TrxID or a receipt number) and Mark as done.

An order that lives in your own system is shown here read-only.

How customers pay

Central AI never holds money. For requests Handled in Central AI, the customer pays you directly, and the agent tells them how, in your words:

1. In section 5, add each way you accept money and fill in What the customer is told (after confirming). For example, for bKash: “Send Money to 01XXXXXXXXX (bKash Personal). Use your request number as the reference, then reply here with the TrxID.” For bank transfer: your account name, number, bank and branch. Publish.
2. When the customer confirms, their request card says Waiting for your payment: bKash with your instructions and the request number. With Online payment, the card also has a Pay now button that opens Your payment link (your website’s payment page, an SSLCommerz, bKash or Nagad payment link). The customer can also ask “how do I pay?” later and the agent repeats it.
3. After paying, the customer sends the transaction ID (TrxID) or transfer reference in the chat. The agent records it on their request, and the card says Payment sent: the business is checking it. It is never marked paid by the agent.
4. Your team gets a notification, and the request shows Payment reported with the reference the customer sent. Check it in your bKash, Nagad or bank statement, then press Record payment (the reference is already filled in). The customer’s card then says Paid.

Cash on delivery needs nothing from the customer in the chat: the card says it is paid on delivery, and you record the payment when the money is collected.

If you already take payment online (SSLCommerz, Stripe and the like)

For example an education platform whose website sells courses with its own payment gateway. Pick one:

Exceptions

Exceptions lists what the agent could not finish on its own; when it is empty, nothing is waiting for you. Sections include orders to check, quotes and orders your system refused, chat credits held and never settled, events that could not be recorded, customers who could not reach support, messages the agent could not answer or has not processed yet, and customer updates that did not arrive. Depending on the row you can recheck, refund, retry, or mark it as dealt with.

Troubleshooting

“Tick at least one thing you sell before you publish.”

Tick a kind in section 2. Press Save draft to keep the rest of your changes meanwhile.

I cannot choose a social channel.

Connect it on Social Channels first. If the page warns about the channel, make the integration active and give it a Meta app secret.

“Created in our system” will not publish.

Press Test connection in Connection to your system (turn on Advanced in section 3) and publish again once every check passes.

The card shows “View details” instead of “Buy on …”.

That kind is not set to On our page in the published revision. Set it and publish.