Skip to content
NewSee how
Improvement

Know when a signature is on but would send empty

When a sender's signature is switched on but would send empty, you now see a clear amber warning instead of an unsigned email going out silently.

A signature that's switched on should actually sign your emails. Now, when a sender has the signature toggle on but nothing real to append, you'll see a clear amber warning instead of a silent gap.

What changed

The per-sender signature toggle defaults to on, which is what most people want. But "on" only does something if there's actually a signature to add. If a sender has no saved signature content — and no usable fallback from their name, title, or email to build a basic one — then nothing gets appended at all, even though the toggle plainly says it's on.

That was a silent gap. The interface showed the signature as enabled, and the accompanying copy promised a basic fallback signature would stand in. In practice that fallback didn't always materialize, so emails could go out completely unsigned while everything on screen insisted a signature was in place.

Now the interface tells you the truth. When the toggle is on but the signature would render empty, you get a clear amber warning in place of that false promise. The warning only appears when there's a real problem — a sender that's set to sign but has nothing to sign with.

How to use it

  1. Open your senders and look for the amber warning on the signature setting.
  2. If you see it, that sender will send unsigned even though the toggle is on.
  3. Fix it by adding saved signature content for that sender — the signature you actually want on the email.
  4. Or fill in the sender's name, title, and email so a basic signature can be built from them.
  5. Once there's real content to append, the warning clears and that sender's emails will go out signed.

Why it matters

An unsigned cold email reads as careless, and it's exactly the kind of detail you don't notice until a prospect does. The old behavior made that easy to miss: the toggle said "on," the copy promised a fallback, and you had no reason to suspect anything was wrong — right up until messages went out with no signature at all.

Now you find out before you send, not after. The warning points you straight at the sender that would go out blank, so you can add a signature or complete the profile and fix it in seconds. It's a small detail, but it's the kind that protects how every one of your emails lands — and it spares you the awkward discovery that a whole run went out unsigned while the setting said otherwise.

All updates

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for 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.