# Understanding Your Usage Source: https://docs.lindy.ai/account-billing/usage How your team shares one pool of credits, why Lindy pauses on a heavy task, and what to do when you need more ![One pool, whole team: shared credit usage with Set credit allocations, Pause routines, and Add credits controls](https://mintcdn.com/lindyai/F-SvcxBkVWXpo_v2/lindy-brand-assets/teammate/usage-credits-topups-banner.jpg?fit=max\&auto=format\&n=F-SvcxBkVWXpo_v2\&q=85\&s=2d397da98d8c89a08b9d7b2e608c2630) Credits cost **\$0.01 per credit on base plans**. Your whole team draws from **one shared pool of credits**. Every seat adds to it, and every Lindy your team works with spends from it: the shared Lindy out in your channels, and the private Lindy in each person's DMs. This page covers what actually uses credits, why Lindy sometimes pauses to check in, and what to do if your team needs more. For seats, pricing, and trials, see [Lindy Teammate Billing](/teammate/lindy-teammate-billing). ## Usage Warning: Why Am I Seeing This? Lindy paused a task because it's using significantly more resources than usual. This is a **protection for your team**, not an error. When a task starts drawing more from the pool than expected, Lindy stops and checks in before continuing. It asks right where you delegated the work: in the Slack thread if you @mentioned it in a channel, or in your DM if you asked there. You can **continue** (the task finishes normally) or **stop** (no additional credits are used). If you stop, the thread stays open and you can pick it back up later. > [!TIP] > > You're not doing anything wrong. The warning just makes sure your team stays in control of a pool everyone shares. ## Credit Usage by Feature Credits pay for the work Lindy does. What follows is a general sense of what each kind of work draws from your pool. ### Your team's Lindy, in your channels Shared with the whole team, drawing on your approved team sources. This is where most of a team's credits go, because everyone @mentions the same Lindy. | What Lindy does | Credit impact | | - | - | | Answering a question from approved team sources | Low | | Pulling a report or a lookup from a connected tool | Low | | Drafting a client update, summary, or document | Moderate | | Team routines, priced by how often they run | Moderate | | Deep research across channels and Drive folders | **Varies** | ### Your personal Lindy, in your DMs Private to each person, and much lighter. These run on their own to keep you ahead of your day. | What Lindy does | Credit impact | | - | - | | Daily brief | Very low | | Email alerts on time-sensitive mail | Very low | | Open-loop nudges when an ask goes unanswered | Very low | | Meeting prep briefings | Very low | | Catch-up summaries when you're @mentioned in a busy channel | Low | | Meeting recaps and notes | Low | | Ad hoc research you delegate in a DM | **Varies** | | [Phone calls](/features/phone-line) | **From 25 credits per minute** | Your Lindy's phone number itself is a separate monthly fee, billed with your plan. > [!NOTE] > > Both Lindys spend from the same pool. A busy channel where the whole team @mentions Lindy will move the number faster than any one person's DMs. Your monthly plan credits reset at the start of each billing cycle and do not roll over. Purchased top-up credits remain available until you use them. ## Checking your usage To see your workspace's total, go to **Settings → Billing** and scroll to the usage section. To see it person by person, open **Settings → Members**. The **Credits** column shows what each teammate has drawn this cycle, and sorting by it is the fastest way to find out where your pool is going. ## Spend caps per teammate Admins can cap how much any one person draws from the shared pool. It's the main tool for keeping one heavy user from spending the team's month. ![Setting a per-teammate credit limit from the Members table](https://mintcdn.com/lindyai/oT4AsoFsQDHf5ck7/lindy-brand-assets/teammate/edit-credit-limit.png?fit=max\&auto=format\&n=oT4AsoFsQDHf5ck7\&q=85\&s=dfe4742e33c017ed381255d83746d6ee) In **Settings → Members**, click the **⋯** menu on a row and choose **Edit credit limit**. Once the limit is reached, Lindy pauses further credit-using actions for that person. A task already running can finish and take usage beyond the cap. Without a cap, that teammate can use the available workspace balance. ## What Happens When Your Team Hits the Limit? 1. **Lindy pauses credit-using work** when the pool runs out. Admins can buy a top-up or change plans if the team needs more credits before the next reset. 2. **Work can continue once credits are available again**, whether from a top-up, a plan change, or the next billing cycle. 3. **Your monthly plan credits reset at the start of each billing cycle.** Unused plan credits do not roll over; purchased top-up credits remain until used. > **What if we need more before the pool resets?** > > Admins have two options: > > 1. **Buy a top-up**: extra workspace credits, with current pricing shown in **Settings → Billing**. Purchased top-up credits remain available until you use them. > 2. **Change the plan**: review the available plans in **Settings → Billing** and choose one that fits your team's usage. > **Does adding a teammate add credits?** > > Yes. Credits belong to the workspace, not to each person, and every seat adds its tier's allotment to the pool. See [Lindy Teammate Billing](/teammate/lindy-teammate-billing). > **Can I try Lindy for free?** > > New users can start with free credits, no credit card required. The free credits last 7 days. If your team is regularly hitting the limit, [reach out](mailto:support@lindy.ai) and we'll find the right fit. ## Credit Optimization To make your team's credits go further, try these adjustments. > **Scope your team sources tightly** > > The shared Lindy searches everything you've approved. Point it at the channels and Drive folders that actually hold your team's answers, not at the whole workspace. > > Open **Settings → Lindy Teammate → Team sources** and prune anything stale. A narrower set of sources is cheaper to search and gives better answers, so this is the rare lever that improves quality and cost at once. > **Review team routines monthly** > > Team routines run on their own schedule whether or not anyone reads the result, and a workspace-wide routine spends for the whole team every time it fires. They're the easiest thing to set up and forget. > > Open the **Routines** page from the left sidebar and review both the **Team** and **Personal** tabs once a month. Flipping a routine off stops it without removing it, so you can turn it back on whenever you want. See [Routines](/teammate/routines). > **Start a new thread for a new topic** > > Every message in a thread re-reads everything above it, so a long-running thread gets more expensive with each turn. This matters more in a busy channel than in a DM, because the whole team keeps adding to it. > > Starting a fresh thread for an unrelated topic keeps every conversation lean. You lose nothing: what Lindy knows from your team's sources carries across every thread. > **Batch related asks into one thread** > > The flip side of the same rule. One thread per topic is the goal, not the fewest threads possible. > > If your team has five questions about the same account, ask them in one thread instead of opening five. If the next question has nothing to do with the last one, start fresh. > **Be specific about what you delegate** > > Deep research is the row in the tables above whose cost genuinely varies, and vagueness is usually the reason. A precise brief tells Lindy when it's done; an open-ended one doesn't. > > * **Costs more**: "@Lindy research Acme." > * **Costs less**: "@Lindy give me five bullets on Acme's funding history and their last two product launches." > > The same goes for length. If you want a short answer, say so. > **Pick the right model** > > Advanced models earn their cost on hard reasoning and analysis. Routine work like summarizing, drafting, and lookups runs well on a cheaper one. > > Switch the model from the dropdown below the taskbar, then select **Set as default** to apply it to new conversations. > **Remove seats you aren't using** > > A seat stays billed until an admin removes it, and you keep it through the end of the current cycle with no mid-cycle proration. When someone leaves the team, remove them in **Settings → Members**. > > If a removed person @mentions Lindy again, it tells them it can't help and pings an admin. It won't quietly re-add them. > **Check usage weekly** > > A quick look at **Settings → Billing** once a week turns an end-of-month surprise into a small adjustment you make on a Tuesday. Sorting **Settings → Members** by the **Credits** column is how you notice one person or one routine burning more than you expected. > [!TIP] > > You don't have to catch all of this yourself. If a single task starts running unusually heavy, Lindy pauses and checks in before continuing. See [Usage Warning](#usage-warning-why-am-i-seeing-this) above. ## Relevant Docs > **[Lindy Teammate Billing](/teammate/lindy-teammate-billing)** > > Seats, trials, top-ups, and your shared credit pool > **[Set up Lindy](/teammate/setup)** > > Get Lindy into your team's Slack and connect your tools # Export Docs for LLM Source: https://docs.lindy.ai/export-full-docs # Ad Hoc Tasks Source: https://docs.lindy.ai/features/ad-hoc-tasks Delegate research, knowledge lookups, and on-demand tasks to Lindy