Aller au contenu
NouveauDécouvrir comment
Correction

Import summary and billing polish

The import summary now reports how many contacts were actually added, and billing errors explain themselves instead of failing silently.

Three small friction points removed from import and billing. None of them are dramatic features — but each one is the kind of thing that catches you off guard at the worst moment, usually when you're trying to move fast and the number you see doesn't match what you expected.

Small fixes that matter

What changed

Import summary now shows contacts added

When you import a list, the summary screen previously reported how many contacts were processed — which sounds useful until you realize it includes duplicates, skipped rows, and records that didn't actually make it into your list. The number you actually care about is how many new contacts were added and are ready to receive campaign email. Those are very different figures when your import includes rows that already exist in your account or fail validation.

The summary now shows the contacts-added figure directly, so you can confirm a list grew by the amount you expected without doing mental arithmetic or cross-referencing against the contacts table. When a campaign depends on a specific list size, knowing the real number at import time prevents surprises later — like launching a campaign and finding it has half the audience you planned for.

Billing errors explain themselves

If you don't have permission for a billing action — adding a payment method, adjusting a plan, managing credits — you previously got a generic error with no indication of what went wrong or who could fix it. That error now carries a plain-language message describing the permission gap, so you know immediately whether to adjust your own settings or loop in the workspace owner.

For small teams where billing permissions aren't always obvious, the difference between a confusing dead end and a clear next step saves real time. You stop assuming something is broken when it's actually a permissions question, and the person who can fix it gets involved right away rather than after a round of troubleshooting.

Credit top-ups start at the payment provider minimum

Credit top-ups now enforce a minimum amount that matches the payment provider's floor. Previously, it was possible to enter a smaller amount that would fail at checkout — completing the form, hitting confirm, and then discovering nothing happened. The floor is now enforced at the point of entry, so the top-up you submit is one that will actually go through. This matters most when you're topping up before a large send and can't afford to discover a failed transaction after the fact.

Where to look

Your Billing page now shows credit balance and runway side by side, so you can tell at a glance whether your credits will last until renewal. The goal with all three fixes is the same: the number you read is the number you can act on, without a second-guessing step in between.

Toutes les nouveautés

Une prospection qui continue quand vous vous déconnectez.Leads, emails, relances et réponses, gérés.

Connectez des boîtes illimitées et laissez les agents IA trouver les leads, écrire chaque email et relancer. Ou envoyez vos propres modèles en mode manuel. À partir de $29/mois.

$1 pour 3 jours · Annulez quand vous voulez · Sans engagement

Installer avec l'IA

Votre agent de code installe la CLI et les skills FirstSales pour vous.

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