Bot settings

Model

• Fast — best for most support queries. Quick, cheap, accurate on grounded answers.
• Quality — deeper reasoning for complex or nuanced questions. Slower.

Language

Sets the bot's default reply language and the widget's built-in translation. If a customer writes in a different language, the bot follows theirs. Chat works in 18+ languages; voice currently covers English and 11 Indian languages — see Voice.

Conversation memory

How many previous exchanges the bot considers when replying (0–6). Higher means better follow-up questions (“and how much does thatcost?”), at slightly higher cost per message.

Fallback message

Sent verbatim when the knowledge base has nothing relevant. This matters: without a good fallback, a bot that doesn't know sounds evasive. A good one moves the customer forward — “I don't have that yet. Email [email protected] and we'll sort it out.”

MonGPT never invents answers from general knowledge. If your content doesn't cover it, the bot says so.

Instructions vs. persona

They're separate on purpose:

• Instructions — rules the bot must follow. What to do, what to avoid, how to structure answers. “Always mention the 14-day refund window when discussing returns. Never quote prices for enterprise plans.”
• Persona — tone and voice. “Warm and enthusiastic, like a helpful shop assistant. Simple words. A light emoji now and then is fine.”

User data collection

Ask visitors for their name, email, or phone before or during the chat. Set it to optional (skippable) or mandatory (chat is blocked until submitted). Captured contacts land on your Leads page and trigger an email.

Notification email

Where new leads and “talk to a human” requests are sent. Defaults to your login email; set a shared inbox here if your team handles support together.