All notes
Workflows 20 January 2026 2 min read

The personalisation tokens that actually move reply rates

First name and company name are noise at this point. The tokens worth enriching for are the ones that require actual research.

{{first_name}} and {{company_name}} are mail merge. Everyone receiving your sequence knows their own name. Seeing it in a subject line signals automation.

The tokens that move reply rates are the ones a recipient can tell required actual knowledge of their situation.

Why do tech stack tokens move reply rates?

Knowing that a prospect uses Salesforce + Outreach + Gong lets you frame your message around the specific integration context they’re already in. “You’re running Outreach on top of Salesforce. Here’s where that creates routing friction” is a claim specific to their setup, and specificity of that kind reads as research rather than automation.

How do you use hiring velocity as a personalisation token?

Hiring velocity tokens quote growth the prospect recognises: “You’ve added 8 SDRs in the last 60 days” is a number they know is correct, and it tells them you’re paying attention to their growth. Pair it with something relevant to that growth signal rather than leaving the number standing on its own.

Why do recent company events make good outreach triggers?

Recent company event tokens reference a funding round, product launch, new market entry, or executive hire. The specificity creates credibility. The timing creates relevance. Together they create a natural reason for outreach that doesn’t feel manufactured, and the event answers the question of why you’re writing now.

What counts as a shared context token?

Mutual connection and shared context tokens draw on what you have in common: the conference they spoke at, the community they’re active in, the tool they’ve publicly endorsed. Each one is a connection point that signals you exist in the same world.

How do you build personalisation tokens in Clay?

Clay pulls and formats the token data at the account and contact level: a column per token, clean output, no truncation issues. The sequence template has a slot for each one, and Claude API handles the cases where raw data needs shaping into a sentence rather than dropping in verbatim.

How many personalisation tokens should each email use?

Pick the two or three most relevant tokens for each account and let the rest inform the message angle without showing up explicitly. The trap is over-templating: if every email in your sequence uses all six tokens in a visible formula, it reads as a checklist.

Part of the field guide The 2027 ABM Playbook →

Keep reading