Leads & human handoff

Capturing leads

In Bot settings → User data collection, choose which details to ask for (name, email, phone) and how firmly:

• Optional — a skippable form at the start of the chat. Higher engagement, fewer leads.
• Mandatory — the customer must submit before chatting. Fewer conversations, more contacts.
• Off — no form.

Our advice: start with optional. A mandatory form in front of a support bot turns away the customers most likely to buy — the ones with an urgent question.

Every submission appears on the Leadspage and sends you an email immediately. The form is translated automatically into your bot's language.

Human handoff

The ? button in the widget header lets a customer ask for a person. When they tap it, MonGPT emails you the full conversation transcriptso whoever picks it up already knows the context — no “can you explain again?”

The customer sees a confirmation in their language, and the conversation stays in your dashboard.

Where notifications go

Set Bot settings → Send leads & handoff requests to. It defaults to your login email. Each bot can notify a different address — useful when sales and support are different people.

Wiring leads into your CRM

Email is fine to start, but on the Scale plan you can subscribe to the lead.created and conversation.handoff webhooks and push contacts straight into your CRM the moment they arrive. You can also read leads through the API.

Privacy

Contact details belong to you. If a visitor asks to be removed, delete the lead from your dashboard. MonGPT never uses your customers' data to train models.