Pular para o conteúdo
NovoVeja como
Novo

Catch spammy wording and broken links before you hit send

Your template editor now flags spam-trigger phrasing and broken or risky links as you write. It's all advisory, so you decide what to fix.

Every cold email template you write is competing with a spam filter before it ever reaches a reply. A handful of trigger words, a stray broken link, or a rendering quirk in one client can quietly tank your deliverability and your reply rate, and none of it shows up until the campaign is already running and the damage is done. Now you can catch it while you're still writing, in the same editor you already use to build the template.

What changed

The email template editor has a built-in copilot that reviews your template live as you edit — no extra step, no separate tool to open. It runs two distinct checks in the background and surfaces both directly in the editor:

  • Spam Lint — scans the copy you're writing for spammy words and patterns known to hurt deliverability. This is about the phrasing itself: the kind of language that trips spam filters before a human ever sees the message, quietly capping your inbox placement no matter how good the offer is.
  • Link & Compatibility Check — scans every link in the template for problems, flagging broken or risky URLs, plus rendering and compatibility issues that could make the email look wrong in some inboxes or email clients. A dead link or a mangled layout doesn't just look sloppy — it erodes trust at the exact moment a prospect is deciding whether to reply.

Together, the two checks cover the two most common silent failure modes in outbound templates: words that get you filtered, and links or markup that get you distrusted. Both run continuously as you type, so you see the results update in real time instead of finding out after the fact.

The critical part is how these checks behave: they are advisory only. The product is explicit about this, labeling both checks with the exact wording "Suggestions only — never blocks saving or sending." The copilot points out what it finds, but it never gates your workflow. You can save a template with flagged spam words. You can send a variant with a check still showing warnings. Nothing is locked behind these suggestions — you decide what's worth fixing and what isn't.

How to use it

  1. Open a campaign and go to Workflow.
  2. Open Email Templates.
  3. Choose a template variant and open Edit Variant.
  4. In the editor, review the Spam Lint and Link & Compatibility Check results, labeled "Suggestions only — never blocks saving or sending."

That's the whole workflow — there's no separate scan to trigger and no report to wait on. Because the checks run live inside Edit Variant, you can write a line, see what the copilot flags, adjust the wording or fix the link, and keep moving without ever leaving the editor. If you're iterating across multiple variants for a sequence, you can run through each one the same way: open the variant, glance at both checks, address what matters to you, move to the next.

Why it matters

Spammy phrasing and broken links are two of the quietest ways a good outreach campaign underperforms. Neither one throws an error. Neither one stops your campaign from sending. They just make your emails land in spam folders instead of inboxes, or look broken when a prospect finally does open them — and by the time you notice a dip in replies, you've often already burned your best leads on a bad template. Deliverability problems in particular are hard to trace back to a root cause after the fact, because the symptom you see (lower reply rates) shows up days after the template that caused it went out.

Catching these issues while you write, instead of debugging a deliverability slump after a campaign has been running, means you fix the problem once, at the source, instead of guessing at it later from aggregate metrics. You get the signal at the point where it's cheapest to act on.

And because the copilot only suggests, it never gets in your way. You can ignore a flag you disagree with, ship on your own timeline, and use the checks as a second pair of eyes rather than a gatekeeper standing between you and sending. That matters for a sales team that needs to move fast — the last thing you want is a compliance step that blocks a send while you're racing to get a sequence live before a prospect goes cold.

The result is cleaner templates, fewer surprises across inboxes and email clients, and more of your outreach actually reaching the person you wrote it for — without adding a single extra step to how you already build your campaigns.

Todas as novidades

Prospecção que continua quando você desconecta.Leads, emails, follow-ups e respostas, resolvidos.

Conecte caixas ilimitadas e deixe os agentes de IA encontrarem leads, escreverem cada email e fazerem follow-up. Ou envie seus próprios modelos no modo manual. A partir de $29/mês.

$1 por 3 dias · Cancele quando quiser · Sem contrato

Instalar com IA

Seu agente de código configura a CLI e as skills do FirstSales para você.

Prompt para Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.