Pular para o conteúdo
NovoVeja como
Correção

Smoother sign-in and account setup

A post-login routing race is fixed, destructive deletes now confirm, the email-auth banner hides once you fully pass, and sign-in, signup, and workspace-access controls behave correctly.

Signing in and getting set up should be the parts of the product you never have to think about. A first-load timing issue could mis-route you right after login, a few setup and delete flows were riskier or more confusing than they needed to be, the email-authentication banner kept nagging after you had fully authenticated, and some sign-in errors pointed you in the wrong direction.

What was happening

Right after sign-in, the app sometimes checked your authentication state before it had finished loading — a race that could send you to the wrong place on first load. Several setup flows had rough edges. Destructive actions — deleting a connector, a tracking domain, an offering, or a knowledge base — relied on a risky second click rather than a clear confirmation, so an accidental tap could remove something important. Connecting Telegram used the wrong link and gave no indication that it was waiting on verification. Finishing onboarding did not take you anywhere obvious next. Campaign test, launch and resume actions were not checked against backend readiness before you tried them, so you could attempt an action that was not actually ready. The "strongly recommended" email-authentication banner stayed up even after SPF, DKIM and DMARC all passed. And the sign-in form could hide a missing password behind an "invalid email" error, signup did not ask you to confirm your password, and owners could not adjust an admin's workspace access.

What we fixed

The first-load authentication race is resolved, so you land where you should right after signing in. Destructive deletes now go through a proper confirmation dialog instead of a second click. Telegram uses the correct app deep link and shows a pending state until it is verified. Finishing onboarding now routes you straight to billing. Campaign test, launch and resume are pre-checked against backend readiness, so you only attempt actions that can actually run. The email-authentication banner now hides itself once SPF, DKIM and DMARC all pass. On sign-in and team management: login validates email and password together so a missing password is no longer masked by an invalid-email error, signup asks you to confirm your password, and owners can now edit an admin's workspace access.

Why it matters

Getting into your account and setting it up is now clearer and safer. You do not get bounced to the wrong screen after logging in, you cannot delete something important with a stray click, and the email-auth banner stops nagging once you have genuinely finished. Login errors tell you what is actually wrong, new sign-ups confirm their password up front, and owners stay in control of who can access which workspace.

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.