Loading
Because the widget captures a name and an email and passes them on. Sales receives a lead with no idea what the person asked, so the first call starts by re-asking what they already told a machine.
The conversation, which is the most useful qualification data available, is discarded at the moment of hand-off.
A qualified conversation becomes a lead in Flow with the whole exchange attached, plus the page they were on and the question they arrived with.
Analytics reports what people asked, what was answered, what triggered handover and what converted — by topic rather than by session count.
The first sales call starts informed. What they asked, what worries them and what they were told are all on the lead.
The reporting also becomes a product and content backlog: the questions asked most often that the assistant could not answer are the next articles to write.
It will not qualify a lead on its own. It records what was said and passes it to a person; deciding whether it is worth pursuing is sales' judgement.
It also does not track individuals across the web. It knows what happened in the conversation, not who somebody is elsewhere.
Nothing here is an integration. Each line is two products reading the same record from different sides.
A qualified conversation becomes a lead in Flow with the whole exchange attached, plus the page they were on and the question they arrived with.
The first sales call starts informed. What they asked, what worries them and what they were told are all on the lead.
It will not qualify a lead on its own. It records what was said and passes it to a person; deciding whether it is worth pursuing is sales' judgement.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.