company logo

Help center

Go to GarbaLogin
Trust CenterProduct UpdatesHomepage
All collectionsBillingAI Credits in Garba

AI Credits in Garba

How AI credits work in Garba

AI Credits cover the work you ask Garba’s AI to do, from answering questions to running agents and drafting content. Credits are shared across your account, so your team uses one common balance.

What uses AI Credits?

Credits are used when you ask Garba to produce something, including:

  • Ask Garba: Questions asked in the web app, Slack or Teams.

  • Agents: Each agent run, plus requests made in the builder chat when creating or refining an agent.

  • AI drafts and edits: For example, drafting a follow-up email or asking AI to rewrite selected text.

What doesn’t use AI Credits?

Garba’s built-in meeting processing and background analysis don’t use credits. This includes:

  • Meeting recording and transcription

  • Meeting summaries and insights

  • Deal scoring

  • CRM sync

  • Built-in helpers, such as suggested questions and chat titles

Recording more meetings does not, by itself, use more credits.

How many credits does a request use?

The cost depends on how much work the AI needs to do, including how much data it reads and how many steps it takes.

A simple question about one meeting typically uses fewer credits than a question that searches many meetings. Similarly, a short agent run typically uses fewer credits than one that works through your entire pipeline.

Typical usage today:

  • Ask Garba question: About 10–25 credits

  • Agent run: About 10–35 credits

  • Meeting recording, transcription, summaries, insights, deal scoring and CRM sync: 0 credits

These are typical ranges, not fixed prices. More complex requests may use more credits.

Can one request use up our entire balance?

Each request is capped at 500 credits, which limits how much any single request can consume.

This is a maximum, not the usual cost. Most typical questions and agent runs use substantially fewer credits. A request could still use your remaining balance if fewer credits are available.

Are credits shared across our team?

Yes. Credits are pooled across the account rather than allocated separately to each user.

Ask Garba, agent runs and AI drafts and edits all draw from the same shared balance.

When do credits reset?

Your included credits reset on the first day of each calendar month at 00:00 UTC.

Admins can see the next reset date under Settings → Account → AI credits.

Do unused credits roll over?

No. Unused credits do not roll over. Your included credit balance resets at the start of each calendar month.

What happens when we run out of credits?

When your account runs out of AI Credits, Ask Garba becomes unavailable and agent runs pause. Your team can use them again once more credits are added or your included credits reset at the start of the next calendar month.

Features that don’t use credits, including meeting recording, transcription, summaries, insights, deal scoring and CRM sync, continue as usual.

How can we get more credits?

Contact Garba support if your team needs more AI Credits.

Where can I see our credit usage?

Admins can track usage under Settings → Account → AI credits, including:

  • Credits used and remaining

  • The next reset date

  • Usage split between Ask Garba and agents

  • The users and agents consuming the most credits

  • A log of every request that spent credits

Why are credits being used when no one is chatting with Garba?

Agent runs also use credits. If an agent runs without someone actively chatting with Garba, that run still draws from your account’s shared balance.

Admins can check the request log to see what used the credits.

Do follow-up emails use credits?

Yes. Asking Garba to draft a follow-up email uses credits. Asking AI to edit that draft also uses credits.

Meeting summaries and CRM sync do not use credits.

How can we make our credits go further?

Keep requests focused on the information you need. For example, specify a company, deal or time period when it’s relevant.

For agents, keep the scope and frequency aligned with the task. A focused run typically requires less work than a broad review of your entire pipeline.

Admins can use the usage breakdown and request log to understand where credits are going and identify requests or agents worth adjusting.

Did this answer your question?
😞
😐
😁