Zum Inhalt springen
NeuSo funktioniert es
Verbesserung

Settings, reorganized

Settings pages now live at their own URLs, so you can link directly to any section. Destructive actions moved behind Privacy.

Settings in FirstSales used to load under a single URL, with each section rendered client-side as you clicked through the navigation. The practical consequences were small but persistent: the browser's back button didn't work as expected, you couldn't paste a link to a specific settings page into Slack or a support thread, and destructive controls — account deletion and similar permanent actions — sat alongside everyday preferences with no meaningful boundary between them. This redesign addresses all three.

Find settings faster

Every settings section now has its own URL, which means browser back and forward work the way you'd expect, and you can share a direct link to any section — useful when walking a new teammate through setup or escalating a question to support.

What changed

Each section is now a real page at its own path. The sidebar navigation reflects exactly where you are. The browser history works normally. If you open Settings → Team and then navigate somewhere else, pressing back returns you to the team settings page — not to wherever you were before you opened settings at all.

Destructive controls have been moved behind their own dedicated section under Privacy. This isn't just cosmetic separation: actions in that section now include a grace period before they take permanent effect, which means an accidental deletion is recoverable. For a workspace that may contain weeks of campaign data, active sequences, and carefully imported contact lists, that recovery window matters.

What moved where

  • General — profile, password, and appearance preferences
  • Team — members, invitations, groups, and domain management
  • Organization / Workspace — names and structural settings
  • Privacy — account deletion and other destructive controls, separated and protected by a recovery grace period
  • Tools — workspace-level tools like automatic email cleaning

Why it matters for outreach teams

For founders and small teams running cold outreach, settings changes often happen under time pressure. Spinning up a new workspace before a campaign launch, adjusting team access for a new hire, tracking down which tool is enabled for a specific workspace — these aren't leisurely tasks. A settings structure that respects browser navigation and supports direct links removes friction from those moments. You land where you intend, share what you need to share, and don't lose your place navigating back.

The grace period on destructive actions is worth noting specifically for teams where someone other than the account owner occasionally has admin access. An accidental deletion is no longer an emergency — it's a recoverable situation with a clear path to resolution. That changes the risk profile of giving trusted teammates admin access when the campaign is live.

Alle Neuigkeiten

Akquise, die weiterläuft, wenn du offline bist.Leads, E-Mails, Follow-ups und Antworten, erledigt.

Verbinde unbegrenzte Postfächer und lass KI-Agenten Leads finden, jede E-Mail schreiben und nachfassen. Oder sende deine eigenen Vorlagen im manuellen Modus. Ab $29/Monat.

$1 für 3 Tage · Jederzeit kündbar · Kein Vertrag

Mit KI installieren

Dein Coding-Agent richtet die FirstSales CLI und Skills für dich ein.

Prompt für 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.