MonGPT

Bot settings

How your assistant thinks, sounds, and answers.

Model

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

Language

Default language sets the first message and the fallback when nothing else is detected. Chat works in all 24 languages; voice is live in 12 across Asia today, with more rolling out — see Voice.

Language behavior controls switching:

  • Match the visitor (recommended) — the widget auto-detects the page language (from <html lang>, the URL like /jp, or the browser) and greets in it; if the customer then writes in another language, the bot follows theirs.
  • Fixed — always reply in the default language, whatever the visitor writes.

Supported languages is the allowlist the bot may switch into — leave all on, or restrict it (e.g. only English + Japanese). Answers come from your knowledge base in whatever language you wrote it; MonCha bridges the language at answer time, so you don't maintain a separate KB per language. To translate the welcome message and quick prompts per language, use the widget's Localization tab. See Install for per-page overrides.

Conversation memory

How many previous exchanges the bot considers when replying (0–6). Higher means better follow-up questions (“and how much does that cost?”), 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.”

MonCha 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.
  • Persona — tone and voice. Warm and enthusiastic, or precise and formal.

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, “talk to a human” requests, and booking requests are sent. Defaults to your login email; set a shared inbox here if your team handles support together.

Delete a bot

In Bot settings (or the Bots list), delete requires typing the bot name exactly. Once deleted, the widget stops appearing on integrated sites immediately — even if the embed snippet is still on the page. Remove the script when you can; see Install → Uninstall / delete a bot.

Deleting an extra bot does not cancel the paid slot. The slot stays on your subscription until you remove it on Billing. See Plans & quotas → Buy Extra bots.

Active / inactive

Use the Active / Inactive toggle next to Rename on Bot settings to take a bot offline without deleting it. While inactive, the widget stops showing on your website (same as a deleted bot for visitors). Playground, knowledge base, and the rest of the dashboard keep working so you can keep editing. Turn it back to Active and the widget appears again on the next page load.

Something unclear? Tell us.

Start free trial