Who, plus what they need
A name and an email tell you someone exists. The conversation tells you what to say when you call them back.
A contact form gets you a name, an email and “I'd like more information”. The conversation that happened just before it holds what they actually needed. This page is about what Engage keeps from that today, and what it does not do yet.
Engage captures a lead when a visitor asks to be contacted and leaves their details, and emails it to your team. It does not score a lead, route it or send it anywhere else, and the two columns below are the whole truth about it.
There is no lead scoring, no routing, no CRM sync, webhook or export, and no SMS or WhatsApp alert. These are things we may build, not things awaiting a toggle.
By the time a visitor reaches a contact form they have usually already explained themselves. The form throws that away and asks them to start again.
Below is a sketch, not a screenshot. It shows the context a conversation already contains. A lead today carries the visitor's own message and the conversation it came from; pulling facts like these out of that conversation, as the right-hand panel does, is not built.
We're replacing an old booking system. Can you migrate our existing customer records?
Migrations from an existing platform are covered on our onboarding page — records and history come across, and the team scopes it before any work starts.
Answered from Onboarding → MigrationsGood. We're a clinic with about forty staff and we'd want it done before the new year.
I don't have anything on timelines for a team that size. Someone here would need to answer that properly.
No supporting content — refused rather than guessedA name and an email tell you someone exists. The conversation tells you what to say when you call them back.
A refusal is a gap in your published content. Collected over time those refusals are a to-do list for your website.
Visitors volunteer scale, timing and constraints while they are asking. A form has to demand the same facts up front, and most people leave instead.
Not yet available — when the console can show conversations: Context that survives the handoff
Whoever follows up should not have to ask the visitor to repeat themselves. A lead already names the conversation it came from; reading that conversation in the console is the part not built.
Nothing is counted here, because there is nothing to count yet.
Yes, through the widget on your own website. When a visitor asks to buy, book or be contacted, the widget offers a short form, and a Contact us button is there throughout. The visitor leaves an email address and a message, ticks a consent box, and every owner and admin on your workspace with a verified email address is emailed. The lead is listed in your console, where your team marks it new, contacted or closed. A lead over the plan's monthly allowance is still kept, never turned away. Nothing scores a lead, routes it or sends it to another system.
No. The agent embeds a question in order to retrieve relevant passages. That is retrieval, and it makes no judgement about whether the person asking is a prospect. The one thing it notices is a visitor asking to buy, book or be contacted, and all that does is offer them the form.
Conversations on your own website are kept for your workspace, and a lead names the one it came from. The console has no page for reading them yet. Conversations in a public demo are removed when the demo expires.
We do not publish dates, and the roadmap deliberately excludes them. A CRM sync, a webhook, an export or a text-message alert would each send a visitor's details somewhere new, so none is built until each has been decided on its own. Talk to us if one of them decides your evaluation — it is better to know now.
Point it at your website and ask the questions your customers ask. That part is real, and so is the form a visitor uses to reach you — they are what you would be buying.
Build your agent