The problem it solves
A booking form filters out everyone not ready to talk to sales — which is most of the people who would have bought. They wanted to look first, found a calendar, and left. An embedded agent converts that larger group: they explore, they ask the questions they were too early to ask a person, and you get the transcript.Where to put it
Beside your booking CTA
Not instead of it. “Book a demo” for the ready; “See it now” for everyone else.
In outbound
A personalized link that greets them by name beats a Loom nobody watches.
On the pricing page
The highest-intent page on your site, and the one where a demo answers “is this worth it”.
In the follow-up
After a call, send the storyline that covers exactly what they pushed back on.
Set it up
1
Build the demo
Give Inkly your product URL, or capture the logged-in product with an agent. See Build from a URL.
2
Write two storylines
One for the economic buyer, one for the technical evaluator. They want different beats in a different order. See Annotations and storylines.
3
Ground the guide on your objections
Your knowledge docs should answer the five things you lose deals on — pricing, security, migration, integrations, and who you are not for.
4
Set the outcome
A primary CTA and a scheduling action the guide offers when someone shows real intent. See Outcomes.
5
Install it and read the transcripts
The questions people ask an agent are the ones they were too polite to ask you.
For outbound specifically
Add each prospect under Contacts and you get a link per person, with the guide briefed by the private note you wrote about them — a note that never reaches the browser. See Personalized links.What you get back
Who opened it, how long they stayed, which screens held them, where they stopped following the guide, and every question they asked — per person, across every visit. See People.Related
Personalized links
One prospect, greeted by name.
Sessions
Transcript and timeline.