Usage and limits

Every plan comes with limits: how many workspaces, members and live surveys you can have at once, and how many responses, AI credits and emails you can use each month. They belong to the organization and are shared by all its workspaces. Organization settings → Usage shows where each one stands and where your usage comes from, so you can act before something stops.

Open the Usage tab

1. Open the account menu at the bottom of the sidebar and choose Organization settings.
2. Choose the Usage tab. It reads the same from whichever workspace you open it in.

What it shows, from top to bottom: anything Paused over your plan, one tile per limit, a notice when responses are waiting for AI, Responses by month, and Where usage comes from.

Read the limit tiles

Each tile shows one limit: what you have used, of what your plan allows, and a bar. The monthly allowances — responses, AI credits, workflow runs, emails and messages — come first, because they are what runs out; then the counts that stand, like workspaces and members.

• Healthy. Under 80% used.
• Close to limit. 80% or more. Polzy also shows a notice at the top of the page, so you hear before it stops anything.
• At limit. All used: what it counts is refused until there is room again.
• Unlimited. The plan has no cap on it, shown as ∞.
• limit. A cap on one thing at a time, such as questions in one survey or API requests a minute: there is no running total.
• Plan … · Packs: … left or Add-ons +… Under a tile when you bought more on top: the plan's share, then what packs still hold or what add-ons added.

The Usage tab shows a tile for every limit, also for features your plan does not have yet.

Every limit, plan by plan

All limits are counted across every workspace in the organization. Monthly allowances start again each month, counted from the day your current paid plan started, on yearly plans too. — means the plan does not have the feature the limit counts.

Solo can also be bought with 5,000 or 10,000 responses a month, Team with 20,000, 30,000 or 50,000, and Business with 50,000, 75,000, 100,000 or 150,000. AI credits go up in steps too: Solo to 3,000, 5,000 or 10,000 a month, Team to 10,000, 20,000 or 40,000, and Business to 25,000, 50,000 or 100,000. You choose both in the order summary when you change plan. Enterprise starts at twice Business's limits, and its contract sets anything above them, priced per unit; its AI credits, emails and messages are never unlimited. What each plan includes besides limits is in Change your plan.

What each limit counts

• Responses per month. Each completed response, on any survey in any workspace.
• AI credits per month. What Polzy's AI spends: reading responses, Ask Polzy, summaries, drafts. A credit is a fixed amount of AI model cost, whichever model spends it. The safety check on written answers costs you nothing.
• Emails a month. Each recipient of an email sent through Polzy's own sender: invitations, reminders, thank-yous, workflow emails and replies in a conversation. Email through your own email provider, invitations to your own team and Polzy's own mail are not counted.
• SMS and WhatsApp messages per month. Each SMS segment sent from Polzy's own number: 160 characters, or 70 once a text holds an emoji or a letter outside the basic Latin alphabet, such as Arabic. Your own SMS provider's messages, Slack and Teams are not counted.
• Workflow runs per month, Active workflows. One run is one trigger firing end to end; a test run is free. Active workflows are those switched on.
• Surveys live at once, Campaigns live at once. Published surveys, and active campaigns.
• Themes, Message templates. Your active themes, and the message templates you made — Polzy's default templates are free.
• Members, Contacts. Members are people who sign in: each one uses a seat in every workspace they belong to, whatever their role. Contacts are people you survey who never sign in.
• Workspaces. Every workspace in the organization.
• Questions per survey, API requests per minute. The most questions one survey can hold, and the most requests one API key can make a minute.

When you reach a limit

Nothing you have collected is ever deleted because of a limit. What happens depends on the limit:

Admins are told in the app and by email at 80% and at 100% of the month's emails.

Paused over your plan

When your limits go down — you cancelled, a trial ended, an invoice stayed unpaid, or your plan was lowered — everything above the new limits is paused, never deleted. Paused over your plan at the top of Usage lists it, grouped by limit, with how much room each limit has.

• Which ones. The most recently used are kept active, up to the limit; the rest are paused, each marked Paused · over plan. The Owner's own seat is never paused.
• What paused means. A paused workspace is read-only: everything opens and exports, but its surveys take no responses, its campaigns send nothing and its workflows do not run. A paused survey shows as closed, a paused campaign or workflow does nothing, and a paused member can still sign in and view.
• Bring back. Choose Bring back beside an item when its limit has room. If it is full, pause another one first, or raise the limit — with an add-on or a bigger plan. When the limit rises, paused items come back by themselves, most recently used first.

Responses waiting for AI

When the month's AI credits are spent, new responses are still collected, but AI does not read and score them. Usage then shows … responses are waiting to be read by AI. They are read as soon as credits return: with a credit pack, with pay as you go, or when the month starts again. Safety checks on written answers keep running all the time.

Where usage comes from

• Responses by month. One bar per month, this month darkest, with a dashed line at your plan limit when it is near the bars. When it is far above them, the limit is written in the corner instead.
• Responses by workspace. This period's responses per workspace. An admin who is not the Owner sees their own workspace and All other workspaces as one line.
• AI credits by feature, this month. The features that spent the most credits across the organization this month, such as Reading responses, Ask Polzy or Comment analysis.

The AI spending cap

With pay as you go on for AI credits, on Business and Enterprise, AI keeps working past the plan's credits and packs, and each extra credit is invoiced at the end of the month. The spending cap is how far it may go in one month. It is set on Billing, in the AI spending cap card, which appears only while pay as you go for AI is on.

1. Open Organization settings → Billing and find AI spending cap.
2. Under Cap, in credits, type the most credits AI may use in one period. It cannot be below your plan's monthly credits.
3. Choose Save cap. Use the default goes back to the default.

Until you set one, the cap is three times your plan's monthly credits. Admins and the billing contact are warned at 80% of it. At 100%, AI features pause with AI is paused: your spending cap is reached until the next period, or until an admin raises the cap; everything else keeps working.

Make room

• Buy a pack or an add-on. More responses, AI credits, emails, messages, workspaces or contacts, without changing plan — see Add-ons, packs and pay as you go.
• Change plan. A bigger plan raises every limit at once; a larger step of Responses per month or AI credits per month raises those two every month, on the plan you have — see Change your plan.
• Free what you no longer use. Close a survey, end a campaign, switch off a workflow, archive a theme, remove contacts or members.
• Send through your own provider. On Team and up, email through your own email provider is not counted; on Business, nor is SMS through your own SMS provider. See Channels.

Troubleshooting

Good to know

• Monthly allowances reset on the same day each month, the day your current paid plan started. On Free, they count from the day the organization moved to Free.
• Packs are used after the plan's own allowance, the one that expires soonest first, and last 12 months.
• When AI runs on your own model key (Enterprise), it spends no Polzy credits; the token ceilings you set under workspace Settings → General apply instead.