System credits and usage

Some of what Unobits does costs real money to run — AI models, outbound messages, phone-network calls, moving large files. That work is metered in system credits. Each plan includes a monthly pool, and you can buy more when you need it. Ordinary use of the workspace — opening records, editing projects, writing documents — is not something you need to think about.

The monthly pool#

The pool refreshes each billing month. Credits are shared by the whole organization — not per person — so it does not matter who sends the campaign or runs the automation.

What draws on credits#

Different kinds of work draw different amounts — an email costs far less than an SMS, and a short AI answer far less than a long research task. The exact weights can change as Unobits' own costs change, so rather than memorizing them, look at what your organization actually spent in Admin → Usage.

When credits run low#

• Top up. In Admin → Billing, buy a top-up pack. Each pack adds 500,000 credits for US$10. Purchased credits are used after the monthly pool runs out and are shown as your purchased credit balance.
• Reach waits rather than fails. If a campaign runs out of credits, its next sends are rescheduled until credits are available — nothing is dropped, and you are not charged for sends that did not happen.
• AI work stops with a clear message. When there is no allowance left for a request, Donna or the automation step says so rather than failing silently.

See what used your credits#

Admin → Usage shows, for the current cycle:

• total credits used against the pool, and the purchased balance,
• Where credits went — broken down by what spent them (campaign sends, research, AI, calls …),
• Who's using the most,
• storage used against your allowance, and seats in use.

See Usage and resources.