Pular para o conteúdo
NovoVeja como
Correção

Billing usage loads again for long-standing accounts

Accounts that have been active for a long time can now load their billing usage page again, after a bug prevented it from loading correctly for those accounts specifically.

Billing usage was failing to load for accounts that had been active for a long time. That is fixed, and long-standing accounts can now view their usage the same as any other account.

What changed

The billing usage page is where you check how much of your plan you have used, whether that is credits, sends, or other metered activity. For accounts with a long history, meaning a large amount of accumulated usage data built up over months of activity, this page would fail to load correctly, leaving you unable to see your own usage at exactly the point when that history was most useful to review.

For a newer account, this page loading quickly and correctly is easy to take for granted, since there is not much usage history behind it yet. For an account that has been sending campaigns, running research, and verifying leads for months or longer, that history is exactly what makes the page valuable, since it is the record you would use to spot trends, catch unexpected spend, or confirm that a plan change actually reflects how you are using the product. Losing access to that record hit the accounts that had built up the most reason to check it in the first place.

This is exactly the kind of account where being able to check usage matters most. A long-standing account is more likely to be actively running multiple campaigns and closer to plan limits, which makes not being able to see usage a real operational problem, not just an inconvenience you could shrug off. If you could not see your usage, you were left guessing at whether you were close to a limit, or reaching out to figure out what should have been a simple, direct check.

The underlying cause was specific to accounts with a large volume of accumulated usage history. Newer accounts, with less history to load, were not affected in the same way, which is part of why this issue was tied specifically to how long an account had been active rather than showing up for everyone. The page was trying to load and process a growing amount of historical data, and past a certain point, that process was failing instead of completing.

The underlying issue causing the usage page to fail on accounts with a large amount of historical data has been resolved. Billing usage now loads correctly regardless of how long an account has been active or how much usage history it has accumulated behind it.

This fix was verified specifically against accounts with the longest history in the system, since those were the accounts most likely to expose the problem again if the underlying cause had not been fully addressed. A fix that only worked for accounts with a moderate amount of history would not have been a real fix, so the accounts with the most usage data behind them were the ones this had to hold up against.

How to use it

If you previously ran into an error or a blank state trying to open your billing usage page, try it again. It should load normally now, showing your current usage against your plan, with the full history intact.

If you rely on usage numbers to decide when to add credits or upgrade a plan, and you had been working around this by contacting support or estimating usage manually, you should be able to go back to checking the page directly whenever you need it.

If you have several people on your team checking usage, it is worth confirming with them that the page is loading correctly for everyone now, not just for the person who happened to notice this fix. Usage visibility across a team only works if everyone with a reason to check it can actually see the same accurate numbers when they look.

If your billing usage page still does not load correctly after this fix, that is worth flagging directly rather than assuming it will resolve on its own, since this specific cause has now been addressed and a continued failure would point to something else worth investigating separately.

Why it matters

You cannot manage spend you cannot see, and you cannot plan around a number you are not allowed to check. A billing page that fails to load, especially for the accounts most likely to be actively spending and closest to their limits, forces you to make decisions about credits and plan limits without the information you need to make them well. Restoring this for long-standing accounts closes that gap, and puts the same visibility back in the hands of exactly the accounts that had lost it. Usage transparency should get more reliable the longer you use a product, not less, and this fix brings that expectation back in line with what actually happened for the accounts that had been with FirstSales the longest.

Trust in a billing page is built slowly and lost quickly. An account that could not check its own usage for a stretch of time has every reason to be more careful going forward, and the fastest way to earn that trust back is simply making sure the page works correctly, every time, for as long as an account keeps growing its history with the product. A page you can no longer trust to load is, in practice, no different from a page that was never built, and that is not a standard worth accepting from a page tied to your spend.

This fix applies automatically. There is nothing to reconnect, re-authorize, or re-request; the next time you open your billing usage page, it should simply work, whether that is today or months from now as your account's history keeps growing further past where it stood when this bug first appeared, with no upper bound on how much history the page can handle going forward, no matter how many years your account eventually spans or how much activity builds up behind it.

Availability

This fix is live now for every account, regardless of how much usage history it has accumulated. You don't need to turn anything on or change any settings for it to apply.

Todas as novidades

Prospecção que continua quando você desconecta.Leads, emails, follow-ups e respostas, resolvidos.

Conecte caixas ilimitadas e deixe os agentes de IA encontrarem leads, escreverem cada email e fazerem follow-up. Ou envie seus próprios modelos no modo manual. A partir de $29/mês.

$1 por 3 dias · Cancele quando quiser · Sem contrato

Instalar com IA

Seu agente de código configura a CLI e as skills do FirstSales para você.

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.