Put your link to work
Where to drop your Parsley link across cold email, LinkedIn, post-call recaps, and your signature, so prospects start conversations on their own time.
Your agent is trained and tuned, and you have a hook ready. Now your link needs traffic. Parsley works anywhere you already reach prospects: instead of sending them to a static page, you send them to a conversation. Lead with the hook from the previous step, and here is where the link earns its keep.
Cold email
Replace the usual "book a call" link with your Parsley link. A prospect who is not ready to talk to a person will often happily ask an agent a few questions first. You capture intent from prospects who would otherwise have ignored a calendar invite.
LinkedIn is where this link does some of its best work, so it gets its own step. Your Parsley link can live right on your profile, where every prospect who looks you up finds it without you lifting a finger, as well as in DMs and InMail. The next step, Add Parsley to LinkedIn, walks through every placement.
Post-call recap emails
This one is underrated. After a first call, drop your link into the recap. The buying committee members who were not on the call can now ask their own questions, and you capture intent from people you have not even met yet. It is often richer signal than a cold touch, because these prospects are already engaged.
Email signature
You built your signature with your hook in the previous step, so your link already travels on every message you send, not just the ones you remember to add it to. It is a passive, always-on capture point.
Pick the channel that fits your motion
You do not need all of these at once. Start with the channel you already use most:
- Heavy on LinkedIn outbound? Put your link on your profile first (the Featured section), then use it in DMs and InMail.
- Running email sequences? Swap the CTA in your best-performing email.
- Doing lots of first calls? Start with recap emails.
Once the link is out there, prospects will start conversations. Before you send it widely, run a test. That is the next step.
