Saltar al contenido
NuevoVer cómo
Nuevo

Drill into sender health and goal performance

Click any sender or goal card in campaign analytics to drill into the exact emails, contacts, and booked meetings behind the number.

Your campaign analytics already show how each sender is performing and which goals a campaign is hitting. Now those cards open up — so you can go straight from a summary number to the exact emails and contacts behind it, without leaving the window you're analyzing.

What changed

Sender health cards are now clickable. Click any sender and a drilldown panel opens, listing that sender's emails for the analytics date range you've selected. The list is paginated and has proper loading and empty states, so you always know whether it's still fetching or simply has nothing to show for that window.

The drilldown stays tied to the controls you've already set. It respects the date range and page size you're working in, and it holds onto the active range even if a refresh fails or you close the panel and open it again. You never silently slip back to a different window than the one you're reading, so the emails listed always belong to the exact period on screen.

Campaign goal drilldowns go a level deeper too. When a goal email has an actual booking attached, the drilldown now shows the booked-meeting details alongside it. For goal contacts who reached the goal but haven't booked, those meeting details are left out — so what you see matches what actually happened, with no placeholder meeting where there isn't one.

Metric cards open contact-level modals, turning a count on a card into the list of contacts that make it up.

How to use it

  1. Open a campaign and go to its analytics.
  2. Set the analytics date range you want to look at.
  3. Click a sender health card to open that sender's drilldown panel.
  4. Page through the sender's emails — the list stays scoped to your selected range and page size as you move between pages.
  5. Click a goal to see the contacts behind it, including booked-meeting details wherever a real booking exists.
  6. Click any metric card to open its contact-level modal and read the individual contacts that make up the number.

Why it matters

Sender-level and goal-level numbers tell you that something is happening, but not who or what is behind it. Now the cards are the starting point, not the end of the trail. One click takes you from "this sender sent this much" to the actual emails that sender handled in your window, and from "this goal was reached" to the specific people who booked a meeting. Because the drilldown keeps your date range and page size — even through a failed refresh or a close-and-reopen — every list you open describes the precise window you set out to analyze, so you can act on what you see instead of re-checking it.

Availability

Available now in campaign analytics, for every campaign and every sender on the account.

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.