Your email promises to show how a sales manager can catch unassigned leads. The prospect clicks. A welcome video starts, followed by a dashboard overview and a menu of features. Somewhere in there is the workflow you mentioned.
Use demo links in cold emails to deliver the specific workflow your message promises, without requiring a meeting first. Use unique contact links when you need recipient-level engagement, and custom topic links when you already know which content matters. Judge the result by useful buyer context and qualified conversations, not clicks alone.
I’d rather send an unglamorous demonstration that answers one real question than a polished tour that asks the buyer to find their own reason to care. The click isn’t the achievement. What happens immediately after it is.
What should a demo link in a cold email open?
It should open a focused demonstration of the task or problem named in the email. The buyer should recognize that connection before you ask them to choose topics, enter details, or learn your product vocabulary.
Consider an illustrative email to a revenue operations lead about lead ownership. The useful opening isn’t your reporting dashboard. It’s an unassigned record, the rule that assigns it, and the resulting owner. Show the starting condition, the action, and the evidence that something changed.
That sounds obvious until you review your actual outbound destinations. Teams often choose the most complete demo because it feels safest internally. But completeness transfers the editing job to the prospect.
A personalized demo link can identify an invited contact, personalize displayed variables, or open selected content. Those are different capabilities. Knowing who clicked doesn’t, by itself, make the content relevant.
Dale, the demo automation platform, supports unique contact links and custom links that open selected branches and topics. One addresses attribution; the other addresses relevance. Decide which problem you’re solving before generating links.
A useful test: finish the sentence, “After watching, the buyer will understand how to…” If your answer is “use our platform,” narrow the destination.
Should you send a public link or a unique demo link?
Use a unique link when you want viewing activity associated with the invited contact. Use a public link when open access matters more than knowing which recipient watched, and consider custom topic links separately as a content-routing choice.
| Link approach | What it solves | What to watch for |
|---|---|---|
| Public link | Provides an openly accessible destination | Viewers are identified only if they complete the details prompt |
| Unique contact link | Associates engagement with an invited contact without another form | Keep the correct contact-to-link mapping when importing into your sender |
| Custom topic link | Opens selected content without the introduction or topic selection | The sender must know enough to choose a useful destination |
A public link isn’t a poor choice. It simply answers a different question. You might learn that a demo is getting attention without being able to connect every viewer to an outreach recipient.
Unique links provide more context, and sharing or forwarding is tracked too. Still, don’t turn contact association into certainty about every action. A forwarded email can travel beyond the person you originally addressed. Read the activity as evidence, not a transcript of someone’s purchasing decision.
The personalized demo link options cover the different sharing routes. Settle the attribution requirement before building your reporting around it.
How do you generate demo links for an outbound sequence?
Use bulk generate when you want a unique link for each prospect and will send through an external email or marketing tool. Use bulk invite when you want the demo platform to email each imported contact their unique link automatically.
This is an easy distinction to miss in a handoff between marketing operations and sales. “Generate the invitations” could mean prepare a spreadsheet or actually send emails. Write down which operation you intend.
- Choose the audience and destination together. Group prospects around a plausible workflow problem, not just a shared job title.
- Review the demo before importing contacts. Check that it delivers the email’s promise and has a sensible next step.
- Upload the prospect sheet for bulk generate. Download the resulting sheet containing each contact’s unique link.
- Map the URL into a dedicated recipient field. Confirm that your sending tool inserts the complete link for the correct contact.
- Run an internal send through the actual sequence. Check the received email, destination, and resulting demo activity, not merely the editor preview.
Protect the original contact-to-link mapping. Sorting one spreadsheet column independently can make the content look fine while attaching the wrong recipient context. That’s a reporting problem you may not notice until a rep follows up.
Also inspect what happens when a merge field is empty. Don’t let a missing URL quietly become an email with a broken invitation. Hold those records for correction.
Demo automation handles part of the workflow, not your outbound judgment. Use an appropriate contact source, respect opt-outs, and follow the rules that apply to your audience.
When should the buyer choose what to see?
Let buyers choose when their priorities are still uncertain. Open specific content directly when the email or previous conversation has already established what they want to inspect.
Suppose a prospect replies, “We already route leads. Reassignment when someone is away is the issue.” That’s a good reason to send a custom topic link. The rep can select the demo, branch, and specific topics, skipping the introduction and topic selection.
A cold job-title match is weaker evidence. A head of sales might care about assignment, forecasting, or coaching. Don’t make them sit through your guess unless the email clearly offers that particular workflow.
A Linear Demo lets viewers rate topics Important / Somewhat Important / Not Important. Important topics play first, with content assembled around those choices. A Branched Demo routes viewers through preset choices such as role, industry, or use case. Branching uses preset answers, not free-text responses.
Use the Linear Demo topic-selection approach when knowing the buyer’s priorities is more useful than forcing a single path.
Build from reusable Pages, each covering a topic or pain point. Add Walkthroughs where clicking through a process helps explain it. Not every Page needs both: sometimes a clear explanation of a rule is more useful than making someone click through several screens.
How do you write a cold email that earns the demo click?
Name a plausible problem, describe exactly what the link shows, and give the reader an easy way to respond. Avoid diagnosing their business from a title or asking for a meeting before they’ve seen anything useful.
Here’s an illustrative email for hypothetical lead-assignment software:
Subject: Lead reassignment when someone is away
Hi [first name],
If new leads wait when their assigned owner is unavailable, this may be relevant.
The walkthrough shows a lead moving to an available rep, with the assignment history visible: [demo link]
Is reassignment something your team is reviewing, or is it already covered?
The wording is deliberately conditional. We haven’t established that this team has an ownership problem. We’re offering something they can inspect, not claiming to have discovered a hidden failure.
“See our platform in action” would be easier to reuse across a large list. It would also make the recipient do more work. Specificity is worth the editing.
I wouldn’t add a calendar link, a webinar invitation, and a separate attachment to this email. Those are competing decisions. Let the message earn the demo view, then let the demonstration offer an appropriate next step.
How much product context belongs in the demo?
Include enough context to understand the workflow, but remove anything that delays the promised answer. If viewers need to know what a routing rule is, explain it beside the action rather than adding a company introduction.
End at a useful decision point: would this fit their process, is there an exception they need to test, or should a colleague review it? Completion alone isn’t the goal.
What should you test before sending demo links?
Test the full handoff from a received email to the useful product moment, on desktop and phone. Then confirm that your team can interpret and act on the resulting engagement.
A responsive player doesn’t make a desktop recording readable. In the lead-assignment example, the proof might be an owner field changing and an activity entry appearing. If both are tiny on a phone, the buyer sees movement but misses the answer.
Pages support an optional vertical video alongside the horizontal version. When mobile video is enabled and uploaded, the platform detects the device and plays the vertical version on phones. Walkthroughs are mobile-optimized, and a separate mobile walkthrough can also be added.
The mobile demo options help with delivery, but the content still needs editing. Check labels, tooltip placement, and tap targets. Prepare recordings externally; there’s no built-in screen recording.
Pre-send checklist:
- The opening content matches the email’s promise.
- Each unique URL belongs to its intended recipient.
- The key product action is legible on a phone.
- Any details prompt has a clear purpose.
- A rep owns follow-up when relevant engagement appears.
Check Dale pricing against the capabilities you need, rather than assuming every plan includes the same sharing and follow-up options. Use the Dale interactive demo to inspect the viewer experience before designing your own.
Which demo activity deserves a follow-up?
Follow up when the activity gives you a useful reason to continue the conversation. Combine content viewed, stated priorities, and account fit rather than treating a click as purchase intent.
A relevant topic rated Important and a related document download give a rep something concrete to address. A replay might signal interest, confusion, or a colleague reviewing the material. Neither establishes budget or timing.
The Buying Intent Signals overview covers topic ratings, rewatches, walkthrough activity, downloads, and sharing. Lead Scoring can help prioritize attention, but inspect the signals behind the score before choosing your message.
Keep that message useful. “Would it help to check how reassignment handles exceptions?” offers a next step. “I noticed you watched this several times” mostly advertises your tracking.
For an initial test, track the journey from sent email to demo viewing, meaningful engagement, reply, and qualified conversation. Define meaningful engagement beforehand, such as reaching the workflow’s outcome. A campaign that generates more clicks but no better conversations hasn’t necessarily improved.
Start with one existing outbound email. Open its destination on your phone, find the first moment that actually delivers the promise, and move that moment closer to the click.