Leads & demo booking

A lead holds the email, name, role and company, first and last page, UTMs, qualifying answers, the CTA taken, an AI summary, intent and a consent flag. Leads are deduplicated by email per organization, listed in the inbox, and exported to CSV.

Each project can define up to five qualifying questions with quick-reply options. The server asks them once, after the first answered question, and stores the answers on the lead.

A book_demo CTA links to your existing Google Calendar appointment schedule. Google owns the slots, the Meet invite, rescheduling and cancellation. The widget embeds the booking page inside the chat, or opens a new tab on small screens. The agent asks for the email first so the booking ties to the lead, and a demo requested event lands on the conversation.

Leads are written to Mango's own table first, then pushed through an outbox with retries to whatever CRM adapter is plugged in, so a CRM outage never blocks chat. The adapter interface ships with a fake implementation today, and a Twenty CRM adapter is planned.