Skip to content
AnytimeReply

Settings

Prices and currency

Choose which currency the AI quotes when your knowledge lists prices in more than one.

Open the agent's Settings → Prices & currency. It matters when your website or documents list prices in more than one currency.

Modes

ModeWhat the customer gets
As in your knowledgePrices the way your pages and documents write them.
Per customer (smart) (recommended)A currency based on where the customer is from — e.g. Bangladesh → BDT, India → INR, everyone else → USD.
Always one currencyEvery customer gets prices in the same currency.
Show all currenciesEvery price with all the currencies you list: ৳350 / ₹290 / $3.5

How "smart" knows where a customer is from

Set Country → currency pairs and a currency for everyone else, then choose which signals to use:

  • Phone number — WhatsApp: +880 → Bangladesh, +91 → India. The most reliable signal.
  • Website visitor's location — the visitor's country from their IP address (built-in database, nothing sent anywhere).
  • Language the customer writes in — used when there's no number or location, mainly Messenger, Instagram and Telegram. Bangla covers Banglish; Hindi covers Hinglish.
  • Messenger, Instagram & AnyChat, when nothing else is known — pick your local currency if most of your Facebook customers are local.

The order the AI follows

  1. The customer names a currency (taka-y koto?, ₹ me, in dollars) — always wins and is remembered.
  2. A currency they asked for in an earlier chat.
  3. Phone number, then location, then the language they write in.

Websites that change prices by country

If your website shows prices by the visitor's country, switch on My website shows prices by the visitor's country and choose how the site picks the currency: a cookie (e.g. currency=BDT) or a URL parameter (e.g. ?currency=BDT). Retrain your website sources afterwards so every currency's prices are learned.

Prices always come from your knowledge. The AI never converts: if a product only has a USD price, it says the USD price.

Was this page helpful?
Still stuck? Contact us