Skip to main content
When a Klipy workspace runs out of tokens, AI actions — accepting suggestions, drafting replies, generating briefs — return a blocked state (SUBSCRIPTION_BLOCKED, reason tokens_depleted). Manual CRM writes stay free: creating or editing a contact, deal, company, task, or note never costs tokens. On pay-per-use with a spending cap, nothing is suspended — overage bills at $0.10 per token instead.

What you’ll see

Trying an AI action in either state shows an error toast — for example “Failed to accept suggestion” — with a description naming the block. The banner offers ways to unblock: upgrading, adding a top-up, turning on pay-per-use, or (on the Free plan) earning free tokens through referrals. This blocked state shows up the moment you try any token-consuming action, not on a single page:
  • Accepting or rejecting an agent suggestion
  • Generating a follow-up draft
  • Creating a deal from a suggestion
  • Generating a meeting brief
Each of these checks the workspace’s token balance first and fails the same way if there’s nothing left. The action doesn’t partially complete: nothing is saved or sent, and the block has to clear before retrying does anything different. Manual work is unaffected throughout this: creating a contact, updating a deal stage, adding a task, or writing a note all still work, since none of these consume tokens.
Screenshot coming soon

Screenshot coming soon: Error toast Failed to accept suggestion, alongside the Settings → Usage You're out of tokens banner

Why it happens

Klipy’s AI actions consume tokens, and every token-consuming action checks the workspace’s subscription state first:
  • Included tokens hit zero, not on pay-per-use → Klipy returns SUBSCRIPTION_BLOCKED (reason tokens_depleted), and every AI action stops working until tokens are available again.
  • Pay-per-use on, under the spending cap → running out of included tokens does not block anything by itself — that’s the point of pay-per-use. Klipy switches to billing overage at $0.10 per token.
  • Pay-per-use on, spending cap reached → this is the only way a pay-per-use workspace gets blocked (reason spending_limit_reached) — a deliberate stop you set, not a surprise. Pay-per-use requires a payment method on file and a spending cap before it can be turned on.
  • Manual CRM writes → never check token balance at all, so they’re never affected by any of this — they’re free regardless of subscription state.

What to do now

1

Check Settings → Usage

Go to Settings → Usage to see exactly why you’re blocked — “out of tokens” versus “spending cap reached” — and how much of your period allowance or cap you’ve used.
Screenshot coming soon

Screenshot coming soon: Settings → Usage, Upgrade, pay-per-use, and referral CTAs

2

Upgrade for more monthly tokens

From the same page, upgrade to the next tier for a larger monthly token allowance. This is the fastest fix if you’re consistently running out before your billing cycle resets.
3

Turn on pay-per-use to stop hitting this again

If eligible, enable pay-per-use with a payment method on file and a spending cap you set. Once it’s on, running out of included tokens no longer blocks anything — usage past the included amount bills automatically at $0.10 per token, up to whatever cap you configured.
4

On the Free plan, earn tokens through referrals

If upgrading isn’t an option right now, the Free-plan banner on Settings → Usage includes a link to earn free tokens by referring teammates.
5

Keep working manually in the meantime

None of this stops manual work: keep creating and updating contacts, deals, companies, tasks, and notes by hand — none of it costs tokens or waits on a block being lifted.

When to contact us

Contact us if you see a SUBSCRIPTION_BLOCKED error while Settings → Usage clearly shows tokens still remaining for the current period, or if pay-per-use is turned on with a spending cap you haven’t come close to reaching and AI actions are still returning blocked. Both are a mismatch between what the usage page reports and what the block is telling you, rather than expected behavior, and worth flagging rather than working around. Reach the Klipy team through Hey Klipy (the floating button, bottom-right of the app) or the “Message the founder” chat in Klipy’s sidebar — both are free. Include:
  • Your current plan tier
  • Whether pay-per-use is on
  • A screenshot of the Settings → Usage banner at the time you hit the block
That’s usually enough for us to tell quickly whether it’s a display lag or an actual account issue. Don’t spend time re-checking the same numbers repeatedly before reaching out — if the usage page and the block message genuinely disagree once, a fresh page load won’t change that, and it’s faster for Klipy to look at the account directly than to keep comparing screenshots on your end.
It’s the error Klipy returns when a token-consuming AI action is attempted on a workspace that can’t currently spend tokens — most commonly because included tokens have run out (reason tokens_depleted) and pay-per-use isn’t on.
No. Manual CRM writes — creating or updating contacts, companies, deals, tasks, and notes — never consume tokens and are never blocked by a token shortage.
Nothing is suspended. Klipy keeps running AI actions and bills overage automatically at $0.10 per token, unless a spending cap is set and has been reached — that’s the only case pay-per-use itself blocks anything.
$0.10 per token, charged once your included monthly tokens are used up. Overage only applies if pay-per-use is turned on for the workspace.
On the Free plan, refer teammates to earn free tokens — the link is on the “out of tokens” banner at Settings → Usage. Otherwise, upgrading to a higher tier or turning on pay-per-use are the ways to keep AI actions running.
Last modified on July 30, 2026