Skip to content
NewSee how

Changelog

What's new in FirstSales, written so you can use it today.

Every new feature, improvement and fix we ship, newest first. Each update says what changed, why it matters for your outreach and where to find it in the app. No release-note jargon, and fixes are listed too.

Start your $1 trial See pricing

$1 for 3 days · Cancel anytime · No contract

  • 01

    Every update in plain English

  • 02

    New, improvement and fix, clearly marked

  • 03

    Each update has its own page

  • 04

    Follow along by RSS

Latest

The newest updates, in plain English.

The six most recent changes to FirstSales. Each one says what changed and what it means for your outreach, with a link to the full write-up.

176 updates since May 29, 2026: 54 new, 64 improvements, 58 fixes

Every update

The full record, month by month.

Every published update, newest first. Scan a month to see what moved, or open any line for the full write-up.

October 2026

13 updates

September 2026

14 updates

August 2026

42 updates

July 2026

50 updates

June 2026

52 updates

May 2026

5 updates

Follow the changelog by RSS
Why a changelog

Software that changes quietly is hard to trust.

Outreach tools change all the time. When nobody tells you what changed, you find out the hard way, in the middle of a campaign.

Features you never hear about

A new option lands in a menu you rarely open. You keep doing things the slow way because no one told you there is a better one.

Changes that surprise you

A screen moves or a default changes, and you lose ten minutes working out whether something is broken or simply different.

Fixes nobody admits to

A bug you reported goes away without a word. You are left wondering whether it is really fixed or will come back next week.

How it works

One place for every change, the moment it ships.

We write an update for each change we ship, so you can see what is different without hunting for it.

  1. 01

    We ship a change

    A new feature, an improvement to something you already use, or a fix for something that was wrong.

  2. 02

    We write it up in plain English

    Each update says what changed, why it matters and where to find it, in words a busy founder can read in a minute.

  3. 03

    You see it where you already are

    The header shows a what's-new bubble when there is something you have not seen. Open the changelog and you are caught up.

What you get

A changelog written for the people who use the product.

Not a list of version numbers. Each update is short, clear and tells you what to do next, if anything.

  • Plain-English updates

    Every update starts with what you will notice, not with how we built it. If a change needs you to do something, the update says so.

  • Clearly marked

    Every update is tagged as new, improvement or fix, so you can tell at a glance whether it is something to try or something that now works properly.

  • A page for every update

    Each update has its own address with the full write-up. Send the link to a teammate who asked about the change.

  • Fixes included

    We list fixes, not just launches. If something was wrong, the changelog says what was wrong and what works now.

  • A what's-new bubble

    The site header shows how many updates you have not seen yet. Opening this page clears it, so the next bubble only counts what is new since.

  • RSS for your reader

    Follow the changelog in any feed reader, or pipe it into a team channel, and get each update as soon as it is published.

Ways tokeep up

Check in when you like, or let the updates come to you. Everything below is drawn from the real changelog.

  1. Header

    A bubble when something is new

    The what's-new link in the site header shows a small count when updates have been published since your last visit. Open it to see the newest titles at a glance. Visiting the changelog marks everything as seen in your browser, so the count starts again from zero.

    • Unread count. Only updates since your last visit.
    • Newest first. The latest titles, one click away.
    • Clears on visit. Opening the changelog catches you up.
  2. Update

    Every update has its own page

    Each update opens on its own page with a category, a date, a short summary and the full write-up. The summary tells you what changed in a sentence or two. The write-up covers the details: what you will see, where to find it and anything you need to do.

    • Category and date. New, improvement or fix, and when.
    • Short summary. What changed, in a sentence or two.
    • Shareable link. Send it to whoever asked.
  3. RSS

    Follow along by RSS

    The changelog is also an RSS feed. Add it to your feed reader, or connect it to a team chat tool that reads RSS, and each update arrives as soon as it is published. No account and no email signup needed.

    • Any feed reader. Standard RSS, nothing to install.
    • Team channels. Post updates where your team talks.
    • No signup. Subscribe without giving an email.
  4. History

    See how the product moves

    The full record is grouped by month, so you can see what changed while you were away. Coming back after a few weeks? Start at the month you left and read down. The counts here are taken straight from the published updates.

    • Grouped by month. Pick up where you left off.
    • Counted from the feed. Real updates, nothing typed in.
    • Every line links. Open any update for the details.
Reading the changelog

How to get the most out of each update

A few habits that turn the changelog from something you skim into something that saves you time.

  1. 01

    Start with the category

    New means there is something to try. Improvement means something you already use works better or faster. Fix means something that was wrong now works. The tag tells you how much attention the update needs before you read a word.

  2. 02

    Read the summary first

    Every update has a one or two sentence summary. Most of the time that is all you need. Open the full write-up when the change touches a part of the product you rely on every day.

  3. 03

    Look for anything you need to do

    Most updates need nothing from you. When one does, such as a new setting to turn on or a record to add to your domain, the write-up says so plainly and shows where to go.

  4. 04

    Catch up by month after time away

    If you have been away for a few weeks, open the full record and start at the month you left. Reading the titles alone gives you a quick picture of what is different.

  5. 05

    Share the update, not a screenshot

    When a teammate asks how something works now, send them the link to the update. It keeps the explanation in one place and stays accurate if the write-up is updated later.

  6. 06

    Tell us when something is unclear

    If an update leaves you with a question, ask us from the app or through the contact page. Clear updates are part of the product, and questions help us write better ones.

Staying up to date

in a minute a week

A short routine that keeps you and your team current without reading every word.

  • Check the what's-new bubble when it shows a count
  • Read the titles of the newest updates
  • Open the full write-up for anything tagged new
  • Check fixes for anything you reported
  • Look for updates that ask you to change a setting
  • Try one new feature on your next campaign
  • Share relevant updates with your team
  • Add the RSS feed to your reader or team channel
  • After time away, read the month you missed
  • Ask us about anything that is unclear
“If you are looking to fix your sales pipeline, you should definitely try [it]. My open rate has increased drastically. The UI and UX are easy to understand, even for a beginner like me.”
Pooja Dhole@ThisIsPoojaD · X
What people say

From people who use it

Real words from real users. No paid reviews.

“One of the biggest pains in cold email is making sure that you have your DNS setup correctly. Firstsales has created a system to make sure you have done this correctly.”

Mike O

Trustpilot review

Trustpilot

“I've been using FirstSales.io for several months now, and I can confidently say it has revolutionized how I approach lead generation and customer acquisition.”

Paweł Stelmach

Small business owner

Trustpilot

“His honest and insightful feedback helped us transform @synchrowork when we started on LTD to what we are building now.”

Sushant Kumar

@sushantkr49

X
Read all reviews
Before and after

Finding out what changed by accident, or from the changelog

The same product, the same changes. One way you stumble on them. The other way you hear about them first.

Without a changelog

Changes you discover by surprise.

  • New features go unnoticedYou keep doing it the slow way.
  • Moved screens confuse youIs it broken, or just different?
  • Silent fixesNo way to know it is really fixed.
  • Questions to supportWaiting on an answer to “what changed?”
  • Team out of stepEveryone learns at a different time.
  • No historyHard to see what moved while you were away.
With the FirstSales changelog

Every change, written up.

  • New features, announcedEach one with where to find it.
  • Changes explainedWhat moved, and why.
  • Fixes listedWhat was wrong, and what works now.
  • Answers in one placeA page for every update.
  • Team in stepShare a link or the RSS feed.
  • A full recordEvery update, grouped by month.

Learn more

Questions,answered plainly.

Can’t find yours? Write to us.

01What is the FirstSales changelog?

It is the public record of every new feature, improvement and fix we ship to FirstSales, newest first. Each update has a short summary and its own page with the full write-up.

02How do I know when there is a new update?

The what's-new link in the site header shows a count of updates published since your last visit. You can also follow the RSS feed at firstsales.io/changelog/rss.xml.

03What do New, Improvement and Fix mean?

New is a feature that did not exist before. Improvement is a change that makes something you already use better. Fix is a correction to something that did not work as it should.

04Why does the what's-new count go back to zero?

Opening the changelog marks every update as seen in your browser. The count then only includes updates published after your visit. It is stored in your browser, so a different browser or device keeps its own count.

05Do I need to do anything when an update ships?

Usually not. Updates apply to your account on their own. When an update does need something from you, such as a new setting or a DNS record, the write-up says so and shows where to go.

06Can I subscribe without an account?

Yes. The RSS feed is public. Add firstsales.io/changelog/rss.xml to any feed reader or to a team chat tool that reads RSS.

07Can I link to a single update?

Yes. Every update has its own page and address, so you can send a teammate straight to the change they asked about.

08Where do I ask about an update?

Ask us from inside the app or through the contact page. If an update is unclear, tell us and we will improve the write-up.

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.

Start your $1 trial See pricing

$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.
Developer docs ↗npm: @firstsales.io/cli ↗GitHub: firstsales-skills ↗