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.
Credits are used when you ask Garba to produce something, including:
Ask Garba: Questions asked in the web app, Slack or Teams, and questions about a strategic insight.
Agents: Each agent run.
Building agents: Chatting with the blueprint builder to create or refine an agent.
AI drafts and edits: Drafting a follow-up email for a meeting, planning a follow-up meeting for a company, or asking AI to rewrite a selection in an artifact.
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.
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 5–15 credits
Agent run: About 10–25 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. The Agents list and each agent's run history show what that agent's runs cost on average.
Each request is capped at 500 credits, which limits how much any single request can consume. A question that reaches the cap stops with "Garba stopped: this question reached the spending limit for a single answer", and a narrower question usually fits.
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.
Your account gets a set number of credits each month for every recording licence it has purchased.
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.
Your included credits reset on the first day of each calendar month at 00:00 UTC, and every month starts on its full allowance. Credits used past the limit are never taken from the next month.
Admins can see the next reset date under Settings → Account → AI credits.
No. Unused monthly credits do not roll over: your included credit balance resets at the start of each calendar month. Extra credits from Garba support do not expire at the end of the month.
Yes. Every admin of the account is told twice a month at most: once when 80% of the month's credits are used, and once when they are all used. Each alert lands in the notifications bell and goes out by email, so it can be forwarded to whoever holds the budget. An admin who switched off Notify me outside the app for AI credits under User → Notifications gets the bell alert only.
What stops depends on your account. On some accounts, Ask Garba and other AI features keep working when the credits run out, and only agent runs stop until the credits reset. They still use credits. If yours is one of them, the AI credits page says so under this month's balance, and the 80% and 100% alerts say so too.
On every other account, Garba refuses new AI work until the credits reset, and says why:
Ask Garba, on the web, in Slack and in Teams, answers with a message that the account has used all of its AI credits for this month, the date they reset, and that an admin can see where they went and ask Garba support for more.
AI drafts and edits and the blueprint builder show the same message instead of a result.
On every account, agent runs are skipped until the credits reset. Each skipped run shows as Skipped: no credits in the agent's run history, and the agent starts running again on its own once credits are available. Skipped runs do not count towards pausing an agent for failing.
Work already under way when the credits run out stops before its next step and keeps what it has done so far. An answer shows what it had written, followed by the reason it stopped. An agent run shows as Stopped: no credits.
When an agent that runs on its own schedule or trigger is skipped or stopped because credits ran out, the person it runs for gets one alert the first time that month. A run someone started with Run now sends no alert, because they see the result.
Features that don't use credits, including meeting recording, transcription, summaries, insights, deal scoring and CRM sync, continue as usual.
Contact Garba support if your team needs more AI Credits, or has questions about them: use the card at the bottom of the AI credits page to chat with us, or email [email protected].
Admins can track usage under Settings → Account → AI credits (https://app.garba.ai/setup/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
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.
Yes. Asking Garba to draft a follow-up email for a meeting uses credits. The draft lands in your mailbox, and editing it there does not.
Meeting summaries and CRM sync do not use credits.
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.
