Saltar al contenido
NuevoVer cómo
Nuevo

Alert Center

A single place in the app for everything that needs your attention: domain issues, connector problems, and sending health.

Deliverability problems are quiet. A sending domain that loses authentication doesn't send you a notification. A connector that stops signing mail doesn't throw an error you'd see in your inbox. A warmup mailbox that's been flagged by a provider keeps showing as active while your sender reputation erodes. These problems used to surface across different corners of the app — or not surface at all until something stopped working and you went looking. The Alert Center changes that.

Never miss a problem

The Alert Center collects actionable alerts in one place, with a bell in the sidebar showing what's unresolved. Domain issues, connector problems, and sending health warnings are gathered in one view, prioritized, and linked directly to the fix.

How to use it

  1. Click Alerts in the sidebar — the bell shows the count of unresolved items at a glance.
  2. Filter by category (mailboxes, AI, campaigns, billing) or by severity to focus on what matters most right now.
  3. Each alert names the affected domain or connector and links straight to the relevant settings page or fix flow — no hunting through menus to find where to act.
  4. Resolve or snooze alerts as you work through them. Resolved alerts stay in history so you have a record of what happened and when.

Why early detection matters for inbox placement

The economics of cold outreach are simple: emails that land in spam don't get read, don't get replied to, and don't book meetings. The factor that determines whether your email lands in the inbox or spam is your sender reputation, and sender reputation degrades silently. You don't notice it in the moment — you notice it weeks later when your open rates have fallen and your reply rate has collapsed.

Fixing a connector problem on day one of an issue is fundamentally different from fixing it on day fourteen. In the first case, the damage is contained. In the second, a week or more of sends may have already landed in spam, your domain's reputation has taken a hit with the major providers, and recovery takes time you don't have if a campaign is live.

The Alert Center changes that timeline. Instead of discovering a problem retroactively in your bounce rate or reply data, you see a named, actionable alert the moment the system detects an issue. The alert tells you what's wrong, which domain or connector is affected, and links you directly to the place in settings where you can fix it.

Severity and categories

Alerts are grouped so you can triage quickly. Billing issues that might interrupt sending, campaign blockers, mailbox health warnings, and AI-related notices each have their own category. Severity levels let you scan for critical items first without reading through informational notes to find them. The ones that can stop your campaigns cold are immediately visible at the top.

Todas las novedades

Prospección que sigue cuando te desconectas.Leads, emails, seguimientos y respuestas, resueltos.

Conecta buzones ilimitados y deja que los agentes de IA busquen leads, escriban cada email y hagan seguimiento. O envía tus propias plantillas en modo manual. Desde $29/mes.

$1 por 3 días · Cancela cuando quieras · Sin contrato

Instalar con IA

Tu agente de código configura la CLI y las skills de FirstSales por ti.

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.