Plans, usage, notifications and SMS
How a team subscribes, what its plan includes and how usage is billed, from self-service registration and Stripe payments to usage alerts, in-app notifications, email delivery and SMS. Browse the feature map or configuration finder.
Availability: Next. Entries that depend on an optional feature, a role or a deployment choice name it in their own Availability line.
Features in this family
- Subscription management
- Current usage and usage history
- Plans and plan limits
- Overage spending cap and notification thresholds
- Change plan or billing interval
- Cancel, undo cancellation or resubscribe
- Payment failure and grace period
- Stripe payments and billing events
- Overage billing
- Custom agreements
- Self-service registration
- Legal documents and consent
- Request and release phone numbers
- Cleanup after cancellation
- In-app notifications
- Notification types
- Usage and overage alerts
- Email delivery
- Send text messages from flows
- Text message allowance and usage
Subscription management
Installations that sell self-service plans show each team its subscription, usage and billing, while installations without it run every team on an unlimited internal plan.
Availability: Requires the Subscription management feature. The My Subscription tab also needs self-service registration to stay enabled.
For: Team administrators, Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Portal and feature profiles | Deployment profile › Subscription management(subscriptionManagement, FEATURE_SUBSCRIPTION_MANAGEMENT) | Release profiles in the Portal |
| Team settings | Settings › My Subscription(subscription) | Open the right team's subscription |
Read more:
- Set it up: Open the right team's subscription
- Reference: Web UI feature conditions
Related features: Current usage and usage history, Plans and plan limits, Self-service registration.
Current usage and usage history
Team Admins see how many minutes, AI tokens and text messages the team has used this month against what the plan includes, and how usage developed in earlier periods.
Availability: Requires the Subscription management feature.
For: Team administrators
| Level | Where to change it | Owner section |
|---|---|---|
| Team settings | Settings › My Subscription › Current Usage(currentUsage, usageHistory) | Read usage and limits |
Read more:
- Reference: Read usage and limits
Related features: Plans and plan limits, Overage spending cap and notification thresholds, Text-to-speech usage over the API.
Plans and plan limits
Each plan defines its price per billing interval, included minutes, tokens and messages, seat limits, overage prices and whether conversation scoring is part of it.
Availability: Requires the Subscription management feature.
For: Team administrators, Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Platform settings | Plan catalogue(includedMinutes, includedTokens, includedSms, maxUsers, maxAdmins, qaScoringEnabled, priceMonthly, priceSemiannual, priceYearly) | Read usage and limits |
Read more:
- Reference: Read usage and limits
- Set it up: Change a self-service plan or billing interval
Related features: Subscription management, Custom agreements.
Overage spending cap and notification thresholds
A team decides how much extra usage beyond the plan it is willing to pay for and at which usage levels it wants to be warned.
Availability: Requires the Subscription management feature.
For: Team administrators
| Level | Where to change it | Owner section |
|---|---|---|
| Team settings | Settings › My Subscription › Subscription Settings(overageLimitCents) | Set overage and notifications |
Read more:
- Set it up: Set overage and notifications
Related features: Usage and overage alerts, Overage billing.
Change plan or billing interval
Team Admins move to another self-service plan or billing interval, and scheduled changes can be withdrawn before they take effect.
Availability: Requires the Subscription management feature.
For: Team administrators
| Level | Where to change it | Owner section |
|---|---|---|
| Team settings | Settings › My Subscription(changePlan, cancelScheduledChange) | Change a self-service plan or billing interval |
Read more:
Related features: Plans and plan limits, Cancel, undo cancellation or resubscribe.
Cancel, undo cancellation or resubscribe
A team can cancel at the end of its period, take the cancellation back before then, or start a new subscription after it has ended.
Availability: Requires the Subscription management feature.
For: Team administrators
| Level | Where to change it | Owner section |
|---|---|---|
| Team settings | Settings › My Subscription › Cancel subscription(cancel, reactivate, createResubscribeCheckoutSession) | Cancel, undo cancellation or return after cancellation |
Read more:
Related features: Cleanup after cancellation, Payment failure and grace period.
Payment failure and grace period
When a payment fails the subscription is paused, calling numbers are suspended, and after a grace period the subscription ends unless billing is restored.
Availability: Requires the Subscription management feature.
For: Team administrators, Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Services and containers | Shared environment(GRACE_PERIOD_DAYS) | Recover from payment or usage blocks |
Read more:
- Troubleshoot: Recover from payment or usage blocks
- Reference: Shared runtime variables
Related features: Stripe payments and billing events, Cancel, undo cancellation or resubscribe.
Stripe payments and billing events
Checkout, invoices and the billing portal run through Stripe, and signed billing events from Stripe keep the subscription state in step.
Availability: Requires the Subscription management feature.
For: Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Services and containers | Web and ops environment(STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STRIPE_API_BASE_URL) | Shared runtime variables |
Read more:
- Reference: Shared runtime variables
- Troubleshoot: Recover from payment or usage blocks
Related features: Payment failure and grace period, Overage billing, Self-service registration.
Overage billing
Usage beyond the plan is priced per minute, per thousand tokens and per message, settled monthly and retried automatically when the overage payment fails.
Availability: Requires the Subscription management feature.
For: Team administrators, Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Platform settings | Admin Settings › Cron Schedules(settle-monthly-overages, retry-failed-overage-payments) | Interpret the job before retrying |
Read more:
- Reference: Set overage and notifications
- Troubleshoot: Recover from payment or usage blocks
Related features: Overage spending cap and notification thresholds, Stripe payments and billing events.
Custom agreements
Platform administrators create versioned custom agreements with their own prices and entitlements and apply a version to a team instead of a self-service plan.
Availability: Requires the Subscription management feature.
For: Deployment operators, Team administrators
| Level | Where to change it | Owner section |
|---|---|---|
| Platform settings | Admin Settings › Custom Deals(customDeal) | Platform administrator: create and apply a version |
Read more:
- Set it up: Platform administrator: create and apply a version
- Set it up: Work with a custom agreement
Related features: Plans and plan limits.
Self-service registration
New customers create their own account by choosing a plan, confirming their email, accepting the legal documents and paying at checkout.
Availability: Requires the Subscription management feature. Registration also needs email and password sign-in to be enabled.
For: Team administrators, Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Services and containers | Web and API environment(FEATURE_REGISTRATION) | Web UI feature conditions |
Read more:
- Set it up: 1. Choose a plan and enter your
- Set it up: 2. Verify your email
- Set it up: 4. Complete checkout and wait for setup
- Set it up: 5. Check the account and team before
- Reference: Web UI feature conditions
Related features: Legal documents and consent, Subscription management, Sign in with email and password.
Legal documents and consent
Users accept the current terms and privacy documents at registration and again when a new version is published, and Team Admins can review what was accepted.
For: Team administrators, Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Team settings | Settings › My Subscription › Legal Documents(legalConsent) | Review legal documents |
Read more:
- Set it up: 3. Review the documents and continue to
- Set it up: Review legal documents
- Set it up: Verify the legal-document catalogue
Request and release phone numbers
A subscribed team can request a phone number from the carrier pool and release it again, and a reconcile job keeps the carrier and platform records aligned.
Availability: Requires the Subscription management feature.
For: Team administrators, Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Services and containers | Ops environment(TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN) | Recover from payment or usage blocks |
Read more:
- Troubleshoot: Recover from payment or usage blocks
Related features: Cancel, undo cancellation or resubscribe, Payment failure and grace period.
Cleanup after cancellation
Once a cancelled subscription ends, a background job removes the team's numbers and resources on a defined schedule.
Availability: Requires the Subscription management feature.
For: Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Platform settings | Admin Settings › Cron Schedules(cleanup-cancelled-teams) | Canceled-team cleanup |
Read more:
- Reference: Canceled-team cleanup
Related features: Cancel, undo cancellation or resubscribe, Decommission a team.
In-app notifications
The bell in the header collects alerts about usage, billing, account, legal and system events for the people allowed to see them, and lets them mark alerts as read.
For: Team administrators, Application builders
| Level | Where to change it | Owner section |
|---|---|---|
| Team settings | Settings › Notifications(notification) | Open notifications from the header |
Read more:
- How it works: Who sees which notifications
- Set it up: Open notifications from the header
- Set it up: Review and acknowledge an alert
- Troubleshoot: Diagnose a missing or repeated notification
Related features: Notification types, Email delivery.
Notification types
Super Admins maintain which kinds of notification exist, who receives them and over which channels they go out.
For: Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Platform settings | Admin Settings › Notifications › Notification Types(notificationType, NotificationResource) | 2. Separate a notification-rule problem from transport |
Read more:
- Set it up: 2. Separate a notification-rule problem from transport
- Reference: Review and acknowledge an alert
- Reference: Separate inbox records, email and SMS
Related features: In-app notifications, Email delivery.
Usage and overage alerts
When usage crosses a configured share of the plan or of the overage cap, the team is notified once per threshold and period.
Availability: Requires the Subscription management feature.
For: Team administrators
| Level | Where to change it | Owner section |
|---|---|---|
| Team settings | Settings › My Subscription › Notification Thresholds(notifyAtPercents) | Set overage and notifications |
Read more:
- Set it up: Set overage and notifications
- Reference: Review and acknowledge an alert
Related features: Overage spending cap and notification thresholds, In-app notifications.
Email delivery
Platform email goes out through SMTP or Amazon SES with a configured sender, and Super Admins can send a test message to confirm delivery.
For: Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Services and containers | Ops environment(EMAIL_TRANSPORT, EMAIL_SENDER_ADDRESS, EMAIL_SENDER_NAME, SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASS, SMTP_PROXY) | Configure and verify email delivery |
Read more:
- Set it up: Configure and verify email delivery
- Set it up: 1. Identify the actual sender
- Reference: Verify SES prerequisites
- Set it up: 3. Verify one permitted message
- Reference: Ops variables
Related features: Notification types, In-app notifications.
Send text messages from flows
Flows and tool code can send text messages to callers through the platform's SMS provider, with sender validation and per-message charges counted against the plan.
Availability: Requires the SMS feature.
For: Application builders, Deployment operators
| Level | Where to change it | Owner section |
|---|---|---|
| Portal and feature profiles | Deployment profile › SMS (seven.io)(sms, FEATURE_SMS) | Release profiles in the Portal |
| Services and containers | Ops environment(SMS_API_KEY) | Check the effective configuration |
| Flow and node settings | Tool code helper(sendSms) | Configure and diagnose SMS delivery |
Read more:
- Set it up: Configure and diagnose SMS delivery
- Reference: Understand message validation and charges
- Troubleshoot: Interpret the job before retrying
- Reference: See which features are enabled
Related features: Notification types.
Text message allowance and usage
Each plan includes a monthly number of text messages, further messages count as overage, and the team sees month-to-date message usage on its subscription page.
Availability: Requires the SMS and Subscription management features.
For: Team administrators
| Level | Where to change it | Owner section |
|---|---|---|
| Team settings | Settings › My Subscription › Current Usage(includedSms, overagePricePerSms) | Read usage and limits |
Read more:
- Reference: Read usage and limits
- Reference: Understand message validation and charges
Related features: Send text messages from flows, Current usage and usage history.