Billing & plans

CommSync bills at the workspace (org) level — one Stripe subscription per org, with the subscription quantity equal to your seat count. The owner is the only person who can change the plan or seat count; everyone else sees read-only billing state in Settings → Billing.

Seats scale every limit

Plans

CommSync has three tiers, each priced per seat per month. Channels, storage, and included AI credits scale linearly with your seat count. Power's channel cap is unlimited regardless of seat count. Webhook endpoints and Agents are flat per-tier caps that do not grow with seats (see the notes below the table).

	Starter	Pro	Power
Price	$25/seat/mo	$50/seat/mo	$100/seat/mo
Channels per seat	5	15	Unlimited
Storage per seat	5 GB	25 GB	100 GB
Included AI credits per seat / mo	$2	$10	$40
Webhook endpoints per user	1	3	10
Agents	0	1	5

The 7-day free trial

Every new workspace automatically starts a 7-day free trial of the Power plan the moment CommSync creates it — no card required.

• Full access, top tier. A workspace on trial runs on Power: unlimited channels, all AI features, agents, and team members.
• CommSync holds nothing back during the trial.
• CommSync charges nothing during the trial.
• There is no card on file, so there is nothing to charge — and no surprise conversion at the end.
• Add a card whenever you are ready.
• Open Settings → Billing and pick a plan (Starter $25, Pro $50, or Power $100 per seat per month).
• Stripe Checkout collects your card.
• Your paid plan starts the day you add the card, on a normal 30-day billing cycle from that day.
• If the trial ends without a card, the workspace is paused: syncing and AI stop, but your data stays safe.
• CommSync keeps the workspace for 30 days after the trial ends.
• Add a card any time in that window, and everything picks back up where it left off.
• After the 30-day retention window, a workspace still without a card is permanently deleted.
• CommSync deletes its channels, threads, messages, and attachments along with it.
• Your account and sign-in always survive — you can sign back in and start a fresh workspace.
• CommSync reminds you. CommSync emails you before the trial ends and again before any deletion, so nothing disappears without notice.
• Where to see it. During the trial, Settings → Billing shows a status pill that reads Free trial.
• A banner there also shows the trial's end date and the number of days left.

AI credits

CommSync prices every AI feature in AI credits, a dollar-denominated allowance. That includes label classification, inbox filing, the Daily Brief, Ask, Agents, writing tools, thread titles, and the semantic-search index. You always know what AI costs because CommSync prices it in dollars, not opaque token counts.

Included credits

Each plan includes AI credits every month: $2 per seat on Starter, $10 per seat on Pro, $40 per seat on Power. Like channels and storage, the pool is org-wide — a 4-seat Pro workspace shares $40 of included credits each period.

• The pool refreshes at the start of each billing period. Unused included credits don't roll over.
• Every AI action draws credits that match its actual model usage at CommSync's usage-based rates.
• Light actions (a labeled message, a filed sender) cost fractions of a cent.
• Heavier ones (a long Ask research session, an agent conversation) cost more.
• The billing page shows exactly how much of the pool the period has used.

Credit balance and top-ups

When the included pool runs out mid-period, AI does not stop. Usage continues automatically from your workspace's credit balance, made up of credits you have purchased. The owner can buy one-time packs of $5, $10, $25, or $100 (or a custom whole-dollar amount from $5 to $500) in Settings → Billing. Purchased credits never expire, and CommSync draws them only after the period's included credits run out.

Auto top-up

To never think about balances again, the owner can enable auto top-up: "when my balance drops below $X, top up $Y." A monthly safety cap (default $100/month) bounds how much auto top-up can ever charge, so a runaway week cannot surprise you.

• Auto top-up charges a saved card.
• A one-time top-up automatically saves your card; you can also add one via Manage in Stripe.
• If an automatic charge fails 3 times in a row, auto top-up switches itself off.
• The owner gets an email. Update the card and re-enable auto top-up in Settings → Billing to pick back up.

When credits run out

If both the included pool and the credit balance reach zero, AI features pause. Messages keep flowing, sync continues, and you lose nothing; the inbox works exactly as before. AI resumes at the next period refresh, or the moment a top-up lands. Members who hit the pause see a prompt to notify the owner; the owner sees the top-up controls directly.

Storage add-on

Need more room, but do not want to change plans or add seats? The owner can add +50 GB storage blocks at $5/month each (up to 40 blocks) in Settings → Billing.

• Blocks join your subscription and prorate immediately, just like seat changes — no separate invoice or checkout.
• The extra space joins the org-wide storage pool on top of your plan's per-seat allowance.
• You can reduce or remove blocks at any time, unless current usage exceeds what the reduced cap would hold.
• In that case, CommSync asks you to free up space first.
• The "Free up space" tool on the billing page lists the largest threads.
• This way, no cap ever strands you.

Seats and how new members affect cost

Seats grow automatically when you add members, and they never auto-shrink when you remove them.

How seat growth works

When you invite a member and they accept, CommSync bumps the Stripe subscription quantity to match the new member count. It also charges a prorated amount for the rest of the billing cycle immediately. This means:

• If you invite a third member to a 2-seat workspace, you get an immediate partial charge for the third seat.
• A live "you'll be charged $X now" preview appears in the seat picker before you confirm.

Why seats do not auto-shrink

If you remove a member, your seat count does not automatically lower. This is intentional:

• Auto-shrinking seats risks a silent drop of the org below its channel or storage cap mid-cycle.
• A drop like that blocks new channel links until the next period.
• Auto-shrink would also generate prorated credits on every member removal.

To reclaim a seat, go to Settings → Billing → Seats and lower the quantity. CommSync applies the unused seat credit to your next invoice.

Tier and seat changes

Both tier and seat changes are prorated immediately — you never have to wait until the next billing period. Upgrades charge the prorated rest of the current period right away; downgrades apply a prorated credit to your next invoice.

How CommSync enforces limits

The limits engine checks each cap at the moment you try to use a resource. If you hit a cap, CommSync does not break data you already have — it blocks new additions until you upgrade or free up space.

Resource	What triggers the check	Behaviour at the limit
Channels	You add an email account or phone number	The upgrade prompt opens so the owner can bump tier or seats
Storage (soft warning)	The pool reaches 80%	Usage banner turns amber; no functional impact
Storage (historical sync pause)	The pool reaches 80%	Historical email and SMS import pauses; live messages continue so you never lose a message in flight
Storage (attachment cap)	The pool reaches 100%	CommSync skips new attachment bytes (the message body still lands); banner turns red
AI credits	Each AI feature run	AI features pause when both the included pool and the credit balance are empty. They resume at the next period refresh or as soon as a top-up lands. Messages and sync are unaffected
Webhook endpoints	You create a new endpoint	Blocked once that user's own endpoint count reaches the per-tier cap (1 / 3 / 10) — the cap is per user, not shared across the org
Agents	You create a new agent	The org's agent-count cap (0 / 1 / 5) blocks creation. There is no monthly cap on replies. Agent replies draw from the workspace's AI credits like every other AI feature, and they pause only when credits run out

What non-owners see when they hit a cap

When a member or admin hits a cap, the upgrade modal prompts them to notify the owner. Only the owner sees the actual upgrade and seat controls, which avoids a confusing 403 error after they click "Upgrade."

Personal vs team workspaces

Every account starts as a Personal workspace — a single-seat org with no invite flow. Personal workspaces behave identically to Team workspaces for billing and limits; they simply cap out at one seat.

To invite teammates, generate join codes, and add extra seats, open Settings → Team and click Upgrade to Team. No data moves — the transition is instant.

What appears on the billing page

Settings → Billing gives you a live view of your workspace's billing state, refreshed every 60 seconds.

Card	What you see
Plan	Tier name, status (Active, Free trial, Past Due, Canceled, Incomplete), per-seat price, seat count, period end (or trial end) date
Seats	Add or remove seats with a prorated cost preview. Owner-only controls.
Usage	Channel count, storage, and AI credits — each shown as a ring with soft-warn amber at 80% and red at 100%
AI credits	Included credits used this period, purchased credit balance, one-time top-up packs, and the auto top-up toggle. Owner-only controls.
Storage add-on	Add or remove +50 GB blocks with prorated billing. Owner only.
Plan switcher	Three plan cards with upgrade / downgrade CTAs. Owner only.
Customer Portal	Opens the Stripe-hosted portal to update your card or view past invoices. Owner only.
Free up space	Lists the largest threads in the org for bulk deletion when storage is high

Cross-workspace channel uniqueness

A channel value — an email address or phone number — can link to only one workspace globally. If you try to link a channel that another workspace already owns, you will see:

"This channel is already linked by [Workspace name]. To use it here, both teams need to be in the same workspace."

The fix is to remove the channel from the other workspace, or to consolidate both teams into one. See Roles & permissions for how to manage team members and Team settings for workspace management.