Understand usage capacity and entitlements

Four related concepts

Access is enforced by the server, not by hiding buttons alone. A capability can be unavailable because the subscription is not entitled, the plan catalog is not configured, a usage policy blocks further consumption, or a workspace role lacks permission.

What counts as a campaign or automated send

Individual customer conversations are included under fair use. A human-sent email or WhatsApp message from an Inbox, customer record, deal, or reviewed quote does not reduce the campaign-send allowance. Provider rules, consent, daily sending limits, and provider charges still apply.

A campaign submitted successfully to 1,000 recipients uses 1,000 sends. The number of campaigns is not limited; the shared monthly delivery allowance is. Included capacity from paid users is pooled at the organization level, so one workspace can use more of the pool when another uses less.

WRKZY does not turn on automatic message overages. An Owner or Admin must explicitly confirm an add-on or plan change. Meta, WhatsApp, Google, Microsoft, and other connected providers can independently apply messaging windows, recipient limits, throughput restrictions, fair-use rules, or fees.

Review capacity

1. Open Settings → Billing & usage.
2. Read Current plan, status, period/trial/grace dates, and currency.
3. Review available meter summaries.
4. For campaign and automated sends, compare consumed, included, remaining, and reset date. Confirm that a suspected event was a successful campaign, sequence, or automated recipient delivery—not an individual conversation.
5. For AI credits, compare consumed, included, remaining, reset date, overage, and projected charge.
6. Expand How AI credits are calculated to read action weights and the displayed policy version. Failed actions use zero customer credits according to the UI.
7. If available, compare plan capacities for users and workspaces in the live catalog.
8. Record which business process owns each approaching limit.

Do not copy capacity numbers into permanent documentation without a plan key, currency/region where relevant, and effective date; the live catalog is authoritative.

Manage AI overage deliberately

Owners and Admins can enable automatic AI overages with a monthly spend cap when that control is active in Billing & usage. Choose a cap from an approved budget and expected business value. If the control is unavailable or read-only, review the visible plan state or contact WRKZY Support instead of assuming overage is enabled. Verify the saved message and revisit projected charge after real usage.

Disabling overage limits future paid continuation; it does not erase usage already recorded.

Respond to approaching capacity

• For user capacity, remove or disable obsolete access only after reassigning work.
• For workspace capacity, review whether each workspace represents a real data/access boundary.
• For campaign-send capacity, reduce duplicate or low-value outreach, move the campaign to the next period, or explicitly approve additional capacity.
• For AI credits, reduce low-value capabilities, improve review workflow, or approve a controlled cap.
• For plan-gated features, compare the live estimate and business need; do not promise an upgrade before confirmation.

Verify effective access

After a subscription or add-on change, wait for entitlement refresh, reload Billing, and test the capability with a safe action. If the plan says entitled but the application remains blocked, preserve both billing status and the feature error.

Recovery

If usage appears wrong, note meter key, policy version, period, included/consumed values, and one safe example action/time. Do not infer billable events from UI clicks; use the recorded meter. If the public catalog is unavailable, current access remains unchanged and plan selection should pause.