Plans, Wallet, and Current Source Values

Guide intro

ConvortAI combines subscription plans with wallet-based charges for AI activity and certain outgoing automation sends. Businesses evaluating the product need both views: what the plan includes and how workflow activity may affect wallet spend over time.

This guide explains how to interpret the pricing structure responsibly so the business can test workflows without getting surprised by usage behavior later.

Plans and included capacity

Plans define the base client-facing capacity such as instances, products or services, and other included limits. They should be reviewed alongside the actual operational complexity of the business, not only by price.

A plan that looks larger than needed may still be useful if the business expects multiple active workflows or faster growth. A smaller plan may be appropriate for a narrow initial rollout.

Wallet usage and AI activity

Wallet usage is separate from the subscription plan because AI activity and outgoing automation send volume can vary significantly by business. Voice, text, media handling, sequence sends, and Media Group sends do not all behave the same way from a usage perspective.

Teams should review wallet behavior during testing rather than assuming usage will stay flat after launch.

How to read current source values

Public pricing materials and the client billing area should be treated as the current source of truth for visible values. If your live account shows updated plan totals or add-on effects, follow the account-level view.

Do not build external promises around outdated screenshots or internal assumptions.

Best practices

• Review pricing before expanding into voice-heavy workflows.
• Re-check visible plan and usage values before rolling changes into client-facing promises.

Related docs