Zum Inhalt springen
NeuSo funktioniert es
Verbesserung

Filter your credit usage by any date range

The billing Usage tab now lets you scope every chart, action breakdown, and campaign total to any window — 7, 30, or 90 days, a custom range, or all-time — and the numbers reconcile no matter which you pick.

Veröffentlicht
Lesezeit
3 Min. Lesezeit

Your Usage tab already shows where every credit goes — by action, by campaign, by workspace. Now you can point all of it at exactly the window you care about, and trust the totals whichever window that is.

What changed

The date-range control at the top of the Usage tab now drives the entire view at once. Pick a preset — 7d, 30d, or 90d — choose All for your account's full lifetime, or open the calendar and set a custom range with your own start and end dates. Every widget below updates together: the headline totals, the daily chart, the per-action cost boxes, the by-campaign breakdown, and the by-workspace rollup. They all describe the same window, so the numbers on screen always add up to each other.

Each action also shows what it actually costs. The per-action boxes list the unit price, how many times the action ran, and the credits it consumed in the selected window — drawn from the live pricing catalog, so what you see is the real cost of each action, not an estimate.

All-time, without the wait

An all-time view can span millions of events, so the on-screen charts focus on your most recent activity and tell you so plainly: a short note explains that the charts show the most recent window and points you to the export for a detailed CSV record. Your CSV export follows the selected range, including All for all-time history, up to the export row limit; if the file is truncated, the CSV says so instead of silently pretending it is complete.

More reliable, end to end

Picking All — or any multi-year custom range — used to be able to fail with an error. That's fixed. Every preset and every custom range now loads cleanly, including the widest ones. And invalid inputs (an end date before the start date, or a date that doesn't exist on the calendar) are now rejected clearly instead of quietly returning numbers for the wrong window — so a total on screen is never subtly off.

How to use it

  1. Open Settings → Billing → Usage (or the Usage tab on the billing page).
  2. Use the range control at the top: tap a preset, choose All, or open the calendar for a custom start and end.
  3. Read the totals — every chart and table below reflects that exact window.
  4. Need a detailed CSV? Use Export on the consumption history for a full-precision file for the selected range, including all-time; if the row limit is reached, the CSV is marked as truncated.

Why it matters

Credit transparency only helps if you can ask the right question: what did last week cost me? Which campaign burned the most this month? How much have we spent since we started? A single, consistent range control across the whole tab lets you answer all three without second-guessing whether two numbers on the same screen are measuring the same thing. Nothing to set up — the improved range filtering is live across the Usage tab now.

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.

Starte deine $1-Testphase Preise ansehen

$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.
Developer docs ↗npm: @firstsales.io/cli ↗GitHub: firstsales-skills ↗