Agency prospecting: a specific observation and proof

Use a narrow agency offer that your team can demonstrate. This example offers a keyboard-navigation recording, then a focused review. It avoids claiming a business result the agency has not measured.

The agency, sender and finding are fictional. Replace them with true details and check the contact route’s current expectations. A public address is not blanket permission to send.

Prepare ownership and evidence

Assign one teammate to the prospect before adding them to a campaign. Confirm that no colleague is preparing the same pitch.

The example assumes a published supplier enquiry route and a reproduced keyboard issue in a pricing menu. Keep the evidence privately until the recipient asks for it, unless the contact instructions request it in the initial proposal.

Merge field: firstName, with the fallback there. The agency name, finding and offer are deliberately written in the message rather than supplied by unreviewed automatic fields.

Message 1: make the finding clear

Initial subject: Keyboard review for your pricing menu

Hi {{firstName | there}},

Your site lists this address for supplier enquiries. When I navigate the pricing menu with a keyboard, focus leaves the visible menu before I can reach the plan links.

I work at Northstar Studio. We review and implement small website fixes, and I can send a short recording of this specific interaction.

Would you like to see it?

Maya
Northstar Studio

If you prefer no further messages, reply and I will stop.

Do not claim the issue affects everyone or produces a measured loss. Confirm the observation in the actual environment you describe.

Message 2: explain the deliverable

Hi {{firstName | there}},

The recording would show the keyboard path and where focus becomes hard to follow. It would not require access to your accounts.

If the interaction is already being reviewed, I will leave it with your team. Otherwise I can send the clip here.

Maya

Reply if you would like me to stop contacting you.

Send only when a follow-up is appropriate and no reply, bounce or opt-out has ended the sequence. Do not send a file you have not prepared.

Message 3: close without a handoff trick

Hi {{firstName | there}},

I will close this enquiry after this message.

If a focused keyboard review becomes useful later, you can reply here. I will not keep following up on this offer.

Thanks,
Maya

Another teammate should not begin a fresh version of the same sequence after this close.

Customize the proof before you send it

When the recipient asks for the clip, answer manually:

Hi Alex,

Here is the keyboard recording: [insert the actual permitted link].

It shows [the verified steps] at [the tested page and relevant environment]. We have not reviewed the entire site.

If a focused review would be useful, I can send its scope and what our team would need. No account access is needed to inspect this clip.

Maya
[real agency name]

Replace all square-bracket prompts before sending. The follow-up sequence reference explains why the automated conversation remains with its original sender; a spreadsheet ownership field does not change that behavior.

Check threading and stop behavior

Follow-ups use the original Gmail thread and mailbox, without separately entered subjects. A detected human reply stops that campaign’s remaining steps; automatic replies do not. See Follow-up sequences.

Mark a reply asking to stop as opted out so future campaigns in the Organization cannot treat it as a new prospect. Preview the recipient name fallback and factual finding before launch.

Assign conversation ownership before launch. Use the campaign launch guide to review audience rules and message previews. The observation and service behind the copy must be real.

Check opt-out controls before launch

ColdMerge’s unsubscribe footer and one-click header start off. Review and enable the appropriate controls before sending. A reply asking to stop does not automatically suppress the address across campaigns: choose Mark as opted out manually. That suppression applies across the Organization. See How unsubscribes work for the configuration and recipient behavior.