Pooled budget: a census of 143 listings

Credits are a single customer-level balance rather than a per-user allowance: when the organisation's balance reaches zero the service stops for everyone on it.

Source retrieved 2026-09-23

Each tier states one monthly credit figure alongside its sub-account count, so the allowance reads as an account-level pool, but the vendor never says whether credits can be split or capped per sub-account.

Source retrieved 2026-09-27

Consumption is metered per end-user conversation at the agent level rather than against per-user allowances, but no balance, pool or overage mechanics are published.

Source retrieved 2026-10-03

No seat balances exist, but the daemon does track both agents' subscription quota windows jointly and reports drift between the two sides.

Source retrieved 2026-09-01

Budgets exist, but as per-agent action and spend limits designed into the workflow, not as a balance shared across seats.

multiTenantCostGuard pools a dollar budget per tenant with a default for unlisted ones; there is no seat concept to share a balance across.

Source retrieved 2026-09-02

There is no metered balance to pool; seats share access to the same connected runtimes and usage inside a connection is unlimited.

The included conversation allowance is explicitly pooled across the account and the year, unused volume rolls forward two months on monthly plans, and annual pools roll into the next term on renewal.

Source retrieved 2026-09-23

The Team plan tops up a single shared balance each month that members draw from, rather than giving each member a separate allowance.

Source retrieved 2026-10-03

Admin documentation describes one account-level credit balance with per-user consumption visible and cappable, while the plan table quotes the same credits per user per year - so the two vendor pages describe the allowance differently.

Source retrieved 2026-09-10

Consumer plans meter into your own credit pool rather than a team balance; organisations get consumption billed centrally to the Cloud project behind the licence, with no documented per-seat budget cap.

Source retrieved 2026-09-10

One wallet and one subscription set are shared by every key in an account, so multiple project keys draw on the same balance; no cross-user team pool is documented.

Source retrieved 2026-10-03

One workspace balance is shared: teammates draw on the same plan credits, lists and exports, and a contact revealed once is not charged again for anyone else.

Source retrieved 2026-09-26

Credits are held at organisation level and drawn down by whoever uses them, and purchased phone numbers are shared across everyone holding a dialer seat, so there is one balance rather than a per-user allowance.

Source retrieved 2026-09-10

Charges draw on a single account-level balance rather than per-user allowances, and the whole account is suspended when that shared balance reaches zero.

Source retrieved 2026-09-24

Included usage and top-ups draw from one shared team balance; Enterprise adds per-user budget overrides.

Source retrieved 2026-09-02

Everyone with access draws on the same business subscription and one shared usage meter; the documented $100 figure only triggers an invoice rather than capping what the team can spend.

Source retrieved 2026-09-11

Credits and limits sit on the organisation, so everyone with a key draws from one shared balance and one set of caps.

Source retrieved 2026-09-11

Conversation quota, AI spend and storage are metered per workspace rather than per seat, and add-ons apply only to the workspace that bought them.

Source retrieved 2026-09-02

One monthly credit allowance sits at account level and covers unlimited agents plus the included client seats, but the vendor publishes no per-client or per-agent sub-limit for dividing it.

Source retrieved 2026-09-13

Allocations, retention and billing attach to the organization and its projects, not to individual members.

Source retrieved 2026-09-02

Credits and prepaid agent dollars belong to the workspace, and every member shares the same resources and balance.

Source retrieved 2026-09-02

One organization funds every key, with per-workspace monthly spend caps and alerts; the SDK also accepts a per-query maxBudgetUsd.

Source retrieved 2026-09-02

Organisation members draw on providers and billing configured centrally by an admin, and spend is reported per team and per member, but no per-seat budget cap is documented.

Source retrieved 2026-09-12

Review allowances are per developer per hour, not pooled, while pay-as-you-go overage spending runs through one organisation-wide path with a single monthly cap.

Source retrieved 2026-09-15

Credit-based workspace agreements draw from one shared pool; individual plans have per-user rate limits instead.

Source retrieved 2026-09-02

One monthly automated-DM allowance is drawn down by the whole workspace, with overage or top-up credits taking over once it is used, rather than per-user balances.

Source retrieved 2026-09-28

Buyers hold one contracted conversation volume rather than per-seat balances, and low-CSAT conversations are excluded from it; no allocation or sub-budget controls are described.

The published allowance is stated per plan per month rather than per member, so usage is drawn from one plan-level pool, but no per-seat or per-team budget split is documented.

Source retrieved 2026-09-13

Per-seat allocations by default and they do not transfer between members; a shared pool is Enterprise-only, tracked cumulatively across the contract term.

Source retrieved 2026-09-02

Credits sit on the project, not the user, and every member and API key in that project draws from the same balance; usage can be attributed per customer or team by tagging keys and requests.

Source retrieved 2026-09-02

Teams draw from one shared credit pool with no per-member balance, while each full seat also carries its own quota.

Source retrieved 2026-09-02

One pooled balance: message credits, apps and storage quotas belong to the workspace, not to individual members.

Source retrieved 2026-09-02

Each paid seat has its own monthly credits first; a shared workspace pool exists but needs admin-purchased top-ups on Business and is contract-funded on Enterprise, and Free seats cannot touch it.

Source retrieved 2026-10-01

One shared workspace balance for everyone; admins carve it up with billing groups that set credit quotas per team and reject requests once a group is exhausted.

Source retrieved 2026-09-02

On a Scale team the included usage is the sum of the seats and everyone draws from one shared pool, so a heavy user can consume a quiet colleague's share without any per-seat split.

Source retrieved 2026-09-14

Credits sit in one team-level balance that any member or key draws from, topped by the plan's monthly grant and by one-time packs, with a single shared ledger.

Source retrieved 2026-10-03

Teams seats each keep their own Pro rate limits; Business and Enterprise usage is shared across the workspace.

Source retrieved 2026-09-02

Spend pools at workspace level rather than per teammate: outcomes and Operator credits are counted for the whole workspace, with shared alerts and a hard limit you set once for everyone.

Source retrieved 2026-09-18

One team balance funds every member and key, with per-key spend limits to stop a single key draining it; Enterprise pools across teams.

Source retrieved 2026-09-24

Seats are individual and carry unlimited chats, so nothing is shared there; only API and MCP consumption draws on one organisation-wide credit balance that admins monitor.

Source retrieved 2026-09-14

Business and Enterprise pool the included credits across the organisation; the comparison table marks pooled usage Not included on Free, Pro, Pro+ and Max.

Source retrieved 2026-09-02

FlexCredits are pooled organisation-wide, with limits then set per department, user or agent.

Source retrieved 2026-09-02

Team members draw on one shared credit balance on both plans rather than each holding a private allowance, which is what makes unlimited seats workable.

Source retrieved 2026-09-30

One account-level credit balance funds every agent, web call, phone call, and campaign. The other quotas are account-wide too: knowledge base is measured across all agents, contacts across your account.

Source retrieved 2026-09-10

Team storage pools a shared base plus a per-seat allowance, but no shared spend or credit balance is described.

Source retrieved 2026-09-29

On the team tier the subscription and its credit allowance belong to the workspace rather than to each member, so the team draws down one shared balance; individual tiers are single-seat so pooling does not arise.

Source retrieved 2026-09-17

It splits: the included allowance is per seat and resets per seat, while separately purchased top-up credits are pooled across the organisation's licences.

Source retrieved 2026-09-18

Usage is metered at workspace level, not per user: all assistant conversation time accumulates across the month against one bill at the same rate, and no per-seat minute allowance exists on any plan.

Source retrieved 2026-09-26

Teams share one Gateway balance and shared BYOK keys; Enterprise adds sub-org budgets and per-user limits.

Source retrieved 2026-09-02

Fleet's compute allowance is one balance for the whole organisation that resets monthly, and Engine spend limits are set org-wide or per project rather than per seat.

Source retrieved 2026-09-18

The included usage allowance is one organisation-wide balance that resets monthly, not a per-seat grant: 5 LCU on Developer, 25 LCU on Plus.

Source retrieved 2026-09-02

There are no seats to split: credits and AI budget sit at account level and are drawn down identically whether the work is triggered in the app, by the agent or over MCP.

Source retrieved 2026-09-18

One balance for the whole workspace: each seat contributes its allocation, the shared and personal Lindys both draw from it, and admins can cap an individual's draw or leave it unlimited.

Source retrieved 2026-09-19

No per-user balances: allowances pool inside a project. Sharing one plan across projects, and quotas managed at workspace level, are Enterprise only.

Source retrieved 2026-09-02

Plan credits belong to the organization, but API keys and incurred billing stay scoped to the individual user.

Source retrieved 2026-09-02

Team seats share one credit balance rather than each holding its own, so heavy users draw on what lighter colleagues leave unspent before add-on credits are needed.

Source retrieved 2026-09-19

Allowances are account-level (events, CPU hours, tokens, storage) and users are unlimited, so there is one shared balance rather than a per-user budget.

Source retrieved 2026-09-02

Usage is metered against one account-level subscription allowance rather than per user, and the vendor must warn the organisation at ninety percent of that shared limit before overage begins.

Source retrieved 2026-09-03

Business workspaces can set per-user budgets and limits against the shared workspace spend, but the vendor does not publish how the pooled balance itself is allocated.

Source retrieved 2026-09-20

Allowances belong to the workspace, not the person: the plan's monthly AI messages, conversations and channel accounts are shared by the whole team, and running out means buying a pack for the workspace.

Source retrieved 2026-10-03

Rate and token quotas are shared across the whole team rather than allocated per key, so multiple developers draw on one pool on pay-as-you-go.

Source retrieved 2026-09-20

Metering is per instance, not per person: one prepaid Gateway credit balance, one monthly execution quota and one AI-credit allowance shared by every user on the instance.

Source retrieved 2026-09-02

The monthly price is one prepaid balance for the whole account that voice minutes and messages draw from, so team members spend from a shared pot rather than personal allowances.

Source retrieved 2026-09-09

One organisation balance with a monthly hard spend limit that returns 429 when reached, plus per-project spend alerts and project-level rate limits.

Source retrieved 2026-09-02

One gateway is one trust domain: teammates work through its provider credentials, so spend and quota land on that one account, and usage surfaces report per provider account rather than per person.

Source retrieved 2026-09-02

A Zen workspace shares one balance, with a workspace-wide monthly ceiling and separate per-member limits set by an admin.

Source retrieved 2026-09-21

Organisation members draw on one shared credit pool, with an org-wide monthly cap plus per-user budgets admins can override.

Source retrieved 2026-09-21

One balance for the whole workspace: every end-user interaction is drawn from the owner's credits, which is why per-user wallets and access-group limits exist to cap them.

Source retrieved 2026-09-09

Each paid plan carries one monthly credit pool for all of the account's processes, but the vendor never describes per-user allocation or limits within that pool.

Source retrieved 2026-10-03

Conversation volume draws on one account-level Subscription Volume of CX Tokens, but the Wren builder allowance is per person and not shared.

Source retrieved 2026-09-02

Gateway budgets are pooled by scope you choose - project, user or key - rather than per seat; in the OSS harness, SpendLimits can share one spend counter across worker processes.

Source retrieved 2026-09-02

One balance for the whole organisation: everybody shares the plan's Actions and Vendor Credits rather than holding a personal allowance.

Source retrieved 2026-09-22

Team credits sit in one shared balance rather than per-person wallets, with usage tracked per workspace for attribution.

Source retrieved 2026-09-22

A workspace holds one prepaid credit balance that every agent and member draws down in real time, and it blocks all new calls when it empties.

Source retrieved 2026-09-23

The minute allowance belongs to the workspace subscription rather than to any user, so every invited collaborator draws on the same monthly pool and the same overage bill.

Source retrieved 2026-09-09

One workspace-level action balance funds every user; admins can auto-reload it below a threshold under a monthly spend cap, and an admin view aggregates per-user consumption.

Source retrieved 2026-09-03

One fungible org-level credit balance spans teams and channels, with Agentforce 1 Editions bundling 2.5M credits per org per year, and Digital Wallet tracks it and automates internal chargebacks.

Source retrieved 2026-09-03

One monthly credit balance is shared and can be split across several websites from a Manage Credits screen, so a subscription is not tied to a single site or user.

Source retrieved 2026-09-25

One AI credit balance is shared across every client workspace on the account, so a heavy month for one client draws down the same pool as the rest.

Source retrieved 2026-10-03

Team plans pool credits across all seats; purchased credits go into the shared pool and the weekly refresh scales with seats.

Source retrieved 2026-09-03

One account-level minute allowance covers every call and every flow; minutes are billed to the second, with overage at the package's published rate.

Source retrieved 2026-09-03

Allowances belong to the organization rather than to each member, and the Enterprise tier negotiates those organization-level limits, so members draw on one shared audit budget.

Source retrieved 2026-10-03

Minute allowances are quoted once per plan against several agents (250 minutes with three agents on Growth), which reads as an account-level pool, but the vendor never states pooling explicitly.

Source retrieved 2026-09-26

One credit balance for the whole workspace, divided by optional team budgets and personal caps, with the stricter of the two winning on every action.

Source retrieved 2026-09-15

Subaccounts draw on the parent agency's minute balance and share its concurrency total, with optional caps.

Source retrieved 2026-09-03

An organization runs on a single shared balance and payment method for every sub-member, so all agents and users draw down one pot rather than per-user allowances.

Source retrieved 2026-09-09

One prepaid balance per account that all Agent and Browser usage draws from; no per-seat allowances exist.

Source retrieved 2026-09-03

It splits by phase: run-time consumption defaults to a zero tenant allocation and draws from the organisation pool, while the design-time AI and Agentic allowance is sized per seat grade and the docs say plainly it cannot be pooled.

Source retrieved 2026-09-03

Plan credits are allocated per seat on Free through Pro, and only purchased top-ups or the Business workspace allocation are shared across the team.

Source retrieved 2026-09-27

One organization credit balance and one concurrency pool; every inbound and outbound call draws on the same capacity.

Source retrieved 2026-09-03

One balance funds everyone: the organization shares a single topped-up balance, and when it runs out all agent work and cloud resources pause together.

Source retrieved 2026-09-27

One balance serves the whole account: receptionist, calling, AI-calling and translation minutes are monthly totals shared across every active line and teammate.

Source retrieved 2026-09-22

Allowances and limits are account-wide: every API key on a tenant draws on one rate limit, and plan minutes are a single tenant balance.

Source retrieved 2026-09-03

One monthly minute balance serves the whole account rather than individual users, and when it runs out with hard stop active inbound AI calls pause instead of overflowing into overage.

Source retrieved 2026-10-03

One credit pool per workspace, shared across the app and the API/MCP, resetting monthly.

Source retrieved 2026-09-03

Split model: each seat gets its own monthly credit allowance, while purchased top-up credits go into one team-wide pool. Only Enterprise gets a contracted shared pool by default.

Source retrieved 2026-09-03

Subscription grants, top-ups and auto top-ups all land in one balance that every metered operation draws from, with no per-feature buckets.

Source retrieved 2026-10-03

Business pools AI spend under one org-wide limit and a single invoice, but seats carry no bundled credit allotment, so the shared pool is spend, not an allowance.

Source retrieved 2026-09-29

Credits pool across the organisation with admin-set per-user caps from Pro Plus upward, while the Pro tier is listed as per-seat credits only.

Source retrieved 2026-09-09

Resolutions are funded from one account-level pool, not per-seat balances, even though the allowance is sized per seat.

Source retrieved 2026-09-03