Billing

Billing in the current product is organization-scoped and entitlement-driven. Plans control access to AI features, voice agents, API access, advanced analytics, and seat limits.

Current billing model

The billing UI currently exposes tabs for:

• overview
• plans
• payment and invoices
• usage

Paid plans are backed by Stripe checkout and portal flows, while plan catalog data is read from Supabase.

Entitlements

Current entitlement fields include:

• included seats and max members
• whether AI is enabled
• whether voice agents are enabled
• whether advanced analytics are enabled
• whether API access is enabled
• usage limits metadata

These entitlements are also enforced by the backend for protected product flows.

Checkout and portal

The app currently uses backend routes for:

• checkout session creation
• customer billing portal session creation
• organization subscription retrieval

That keeps billing permissions and organization context server-authoritative.

Usage

The current billing model also records usage and member counts so the app can show plan consumption and block actions such as inviting additional members when a seat limit has been reached.