Skip to content
NewSee how

Read Your Credit Runway & Usage History

See how long your credits will last, what's consuming them, and per-campaign and per-workspace usage. Plus export the full history to CSV.

Tutorials
Analytics
min read
5 min
steps
7 · Beginner

  1. Two views: runway vs. history

    The Overview tab answers “how long will my credits last?”; the Usage tab answers “where did they go?” Both live on the Billing page.

  2. Read the Credit Runway widget

    On Billing → Overview, the Credit Runway widget forecasts how many days or months of sending your credits will cover at your current burn rate, and flags tight or danger states with a top-up button. Before you've sent anything, it prompts you to start sending campaigns first.

    Read the Credit Runway widget

  3. Understand the runway states

    Four states (healthy, comfortable, tight, and danger) compare your forecasted runway against your plan's renewal date, shown as a “Plan renews in N days” line.

  4. Check your balance breakdown

    Your total balance is org (plan) credits plus top-up credits. Top-ups add straight into the same pool as your plan's monthly grant.

  5. Open the Usage tab & pick a range

    Go to Billing → Usage and use the date-range preset filter. Figures shown are net of refunds, and timestamps are in UTC.

  6. Read the breakdowns

    Summary cards for Total Consumed, Daily Average, and Action Types, plus a daily consumption chart and a by-action-type chart. Two tables (By Campaign and By Workspace) show you exactly where credits are going.

  7. Export to CSV

    Export the full dataset (history, by-action, or by-campaign) for finance review or deeper analysis outside the app.

Pro tips

  • Runway is gross spend, refunds excluded

    A refund-heavy week won't make it look like you've stopped spending: the forecast tracks your gross burn rate.

  • Tight or danger means act now

    Both states mean you'll likely run out before renewal: the widget's Top up credits button is the one-click fix.

  • Usage numbers are UTC and net of refunds

    If a number looks off versus your local day, that's the timezone, not a bug.

  • Use By Campaign to spot the biggest consumer

    One runaway campaign can burn most of a workspace's credits before you notice: check this table before the whole balance drains.

Frequently asked questions

Where do I see how long my credits will last?

Billing → Overview → Credit Runway widget.

Why does the runway say Start sending campaigns…?

There's no usage yet: the forecast needs a burn rate to calculate runway from.

What do healthy/comfortable/tight/danger mean?

Forecast bands comparing your runway to your renewal date. Tight and danger prompt a top-up.

What's the difference between org credits and top-up credits?

Org credits are your plan's monthly grant; top-up credits are one-off purchases. Both add into a single total balance.

Why don't the usage numbers match my local calendar?

They're shown in UTC and net of refunds.

Can I see usage per campaign or workspace?

Yes: the Usage tab has By Campaign and By Workspace tables.

Can I export my usage?

Yes: CSV export for history, by-action, or by-campaign.

The date range says charts are clamped: why?

Very wide ranges show only the most recent window in charts; use the CSV export if you need the full all-time record.

Analytics

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

Start your $1 trial See pricing

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for 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 ↗