For sales teams and founders doing cold outreach

Cold emails and follow-ups that don’t read like one sequence

You send first touches and follow-ups to many people. Cold email templates and AI drafts reuse one structure, so from the prospect’s side the emails look identical, and a reply to an objection can ignore what the prospect actually said.

Unsame changes the approach and form (such as the opening or length) your AI uses each time you write the same kind of thing. Your AI writes the words; Unsame writes nothing.

Start free See a real example

A real example

One input, three takes.

A take is one version of the text. Below, a real input runs through the starter template three times, and a real model writes each take from the protocol (the short instruction Unsame returns). Voice and rules stay the same; the approach and form change. Beside each take is what the same model wrote from the same input with no protocol.

Written by

Cold outreach

First touches and replies to prospect responses.

Input

Prospect: Priya Raman, VP Support at Northline Logistics. Trigger: she posted on March 4 that they are moving to a new helpdesk this quarter. We sell ticket-triage automation.

Facts given to both

  • customer of similar size: Marlow Freight, 35 agents, cut first-response time from 4 h to 55 min in 6 weeks with our triage automation
  • our product routes each ticket to the right queue and drafts a reply from the help center within 10 seconds of arrival
  • one-page asset: Helpdesk migration checklist for support leads, https://example.com/helpdesk-migration-checklist

= Same every run

Situation
first touch with a trigger
Engage with
Trigger: she posted on March 4 that they are moving to a new helpdesk this quarter.Prospect: Priya Raman, VP Support at Northline Logistics.We sell ticket-triage automation.
Always
use at least one provided fact about the prospect verbatim: name, role, event or date
Voice
plain, specific, written like one colleague to another
Never
invent a fact, number or customer not given in the input, open with 'hope you are well' or an intro of the seller's company, attach a pitch deck to a first message, use em dashes (—) or stock phrases like "here's the thing", "let's dive in" or "game-changer"

Plain prompt · Claude, no protocol

With Unsame · a varied play each run

  1. Run 1
    Plain prompt

    Subject: Ticket routing on Northline's new helpdesk Hi Priya, You posted on March 4 that Northline Logistics was moving to a new helpdesk. I'm curious how ticket routing has held up since the switch, and whether your team is still sorting tickets by hand. We build…

    With Unsame

    trigger_observation

    • cta reply_yes_no
    • length short_paragraph
    • opener question

    Priya, when Northline Logistics switches to the new helpdesk you mentioned in your March 4 post, who on your team is rebuilding the routing rules? That job usually lands on support mid-cutover, and tickets tend to sit in the wrong queue while agents get used to the new tool. Our…

    How this play was written

    connect the event, with its date and source in the prospect's terms, to the one problem it usually creates for a team like theirs

    Situation: first touch with a triggerEngage with:- Trigger: she posted on March 4 that they are moving to a new helpdesk this quarter.- Prospect: Priya Raman, VP Support at Northline Logistics.- We sell ticket-triage automation.Use:- our product routes each ticket to the right queue and drafts a reply from the help center within 10 seconds of arrival- one-page asset: Helpdesk migration checklist for support leads, https://example.com/helpdesk-migration-checklist- customer of similar size: Marlow Freight, 35 agents, cut first-response time from 4 h to 55 min in 6 weeks with our triage automationApproach: connect the event, with its date and source in the prospect's terms, to the one problem it usually creates for a team like theirsForm: length: short_paragraph; opener: question; cta: reply_yes_noWrite: skip the first wording that comes to mind; Form sets the length, opening and ending.Always: use at least one provided fact about the prospect verbatim: name, role, event or dateVoice: plain, specific, written like one colleague to anotherNever: invent a fact, number or customer not given in the input, open with 'hope you are well' or an intro of the seller's company, attach a pitch deck to a first message, use em dashes (—) or stock phrases like "here's the thing", "let's dive in" or "game-changer"
  2. Run 2
    Plain prompt

    Subject: Ticket triage after the Northline helpdesk move Hi Priya, You posted on March 4 that Northline Logistics was moving to a new helpdesk this quarter. That was a while back, so you may already be settled on the new system, or still working through the last…

    With Unsame

    question_led

    • cta soft_calendar
    • length two_lines
    • opener observation

    Priya, your March 4 post said Northline Logistics is moving to a new helpdesk this quarter: during the cutover, who will own sorting incoming tickets into the right queues? I ask because that's the step our triage automation handles, and it helped Marlow Freight's 35 agents cut…

    How this play was written

    centre the message on one question about a concrete problem in their role, and say why we ask

    Situation: first touch with a triggerEngage with:- Trigger: she posted on March 4 that they are moving to a new helpdesk this quarter.- Prospect: Priya Raman, VP Support at Northline Logistics.- We sell ticket-triage automation.Use:- our product routes each ticket to the right queue and drafts a reply from the help center within 10 seconds of arrival- one-page asset: Helpdesk migration checklist for support leads, https://example.com/helpdesk-migration-checklist- customer of similar size: Marlow Freight, 35 agents, cut first-response time from 4 h to 55 min in 6 weeks with our triage automationApproach: centre the message on one question about a concrete problem in their role, and say why we askForm: length: two_lines; opener: observation; cta: soft_calendarWrite: skip the first wording that comes to mind; Form sets the length, opening and ending.Always: use at least one provided fact about the prospect verbatim: name, role, event or dateVoice: plain, specific, written like one colleague to anotherNever: invent a fact, number or customer not given in the input, open with 'hope you are well' or an intro of the seller's company, attach a pitch deck to a first message, use em dashes (—) or stock phrases like "here's the thing", "let's dive in" or "game-changer"
  3. Run 3
    Plain prompt

    Subject: Triage on the new helpdesk at Northline Hi Priya, I saw your March 4 post about Northline Logistics moving to a new helpdesk. Whether the switch is done or still underway, it's usually a good moment to rethink how tickets get sorted, since queues and routing rules are…

    With Unsame

    peer_proof

    • cta interest_question
    • length three_short_paragraphs
    • opener event

    Hi Priya, Your March 4 post about Northline Logistics moving to a new helpdesk this quarter caught my attention. A migration is a natural moment to rethink how tickets get routed, so here is a one-page Helpdesk migration checklist for support leads that might be handy:…

    How this play was written

    name a customer of similar size and role given in the input, state one result as a number with a time frame, and say what changed

    Situation: first touch with a triggerEngage with:- Trigger: she posted on March 4 that they are moving to a new helpdesk this quarter.- Prospect: Priya Raman, VP Support at Northline Logistics.- We sell ticket-triage automation.Use:- our product routes each ticket to the right queue and drafts a reply from the help center within 10 seconds of arrival- one-page asset: Helpdesk migration checklist for support leads, https://example.com/helpdesk-migration-checklist- customer of similar size: Marlow Freight, 35 agents, cut first-response time from 4 h to 55 min in 6 weeks with our triage automationApproach: name a customer of similar size and role given in the input, state one result as a number with a time frame, and say what changedForm: length: three_short_paragraphs; opener: event; cta: interest_questionWrite: skip the first wording that comes to mind; Form sets the length, opening and ending.Always: use at least one provided fact about the prospect verbatim: name, role, event or dateVoice: plain, specific, written like one colleague to anotherNever: invent a fact, number or customer not given in the input, open with 'hope you are well' or an intro of the seller's company, attach a pitch deck to a first message, use em dashes (—) or stock phrases like "here's the thing", "let's dive in" or "game-changer"

Setup

Set it up in 4 steps.

  1. 01

    Sign up free

    100 credits a month, no card.

  2. 02

    Pick the matching template

    Start from “Cold outreach”. It is a ready-made playbook: a list of approaches for first touches and replies to objections, plus your voice and rules.

  3. 03

    Connect your AI

    Use Claude, Codex or another app that supports MCP (the standard way AI apps connect to outside tools).

    How to connect
  4. 04

    Paste the “Use this goal” prompt

    Open your goal, copy its “Use this goal” prompt into your connected AI chat, then give it your input. Your AI writes the text.

Questions

Fair questions.

Will every email in a sequence still say the same thing?

The facts stay the same: your product, your proof and what you know about the prospect. What changes is the approach and the form (such as the opener, length and call to action). Your AI still writes the words, so check each email before you send it.

Will it invent facts about the prospect?

The template tells your AI to use only the facts you provide and never to invent a name, number or customer. Your AI still writes the text, so check each email before you send it.

Does it handle replies, not just first emails?

Yes. The template has situations for first touches and for prospect replies such as “we already use a competitor” or “send me more info”, each with its own approaches.

Try it on your own input.

The free plan needs no card. Your model key stays with you.

Other use cases: Threads posts and repliesX posts and repliesSupport replies

Start free How to connect