Skip to main content
Number service uses paid 24-hour windows, not a per-message charge. A charge starts a paid window; stopping or disconnecting a number preserves the remaining paid time. Usage assigns the window and its credits to the UTC date of the charge.

​
Explore consumption

Open Usage for the selected project or choose All projects for team totals. The default period is the current UTC calendar month. Choose the last 7 or 30 days, or set a custom date range of up to 366 days. The summary shows credits charged and the measured number-service, call and storage charges for the selected period. Credit charges retain up to six decimal places, so a small nonzero charge stays visible. A dash means the charge is unavailable. Current-month limits and reservations remain in Funding controls and the selected resource’s limit panel.
  • Select a colored legend beneath the chart to view a service’s usage. Select Credits charged to return to total charges. Numbers shows only tiers charged in the selected period.
  • Match a graph series to the same color in the breakdown. Credits charged stacks measured charges by billable product, including number-service tiers. Each service’s quantity chart uses its own units; days, calls, GB-months and invocations are not added together.
  • Switch between daily, weekly and monthly points on the area graph. Project comparisons use bars. Cumulative adds usage over the selected period.
  • Open a product row for its detail chart. In All projects, Projects compares available project totals, with a ranked table and donut showing their shares.
In All projects, owners and admins on Pay-As-You-Go see each project’s current monthly credit-limit progress beside its usage. Select a project row to open all of that project’s consumption. The top bar shows Usage / All numbers. Open All numbers and search by number name, phone or ID. Scroll to browse more results. Press Esc to close the picker. In All projects, choosing a number opens its owning project. Choose All numbers to return to the selected project’s totals. Product charts keep the selected number. You also reach one number’s Usage from Numbers → View usage in its row actions. The link opens Usage in that number’s project. Number service shows charged credits. The breakdown includes billable products; unpriced operational measurements do not appear. All consumption uses the selected UTC range. Missing measurements show Data unavailable; this does not mean a priced service is unmetered. Missing daily data shows Daily data unavailable; loading or failed reads do not appear as zero usage. Monthly add-on subscriptions and their currency payments remain in Billing. Consumption is read-only. Funding controls appears below it for team owners and admins. Edit project limits and funding order there; number and customer limits and priority open in their native panels. The time picker lists Last 24 hours first. Select it for the preceding 24 hours, or choose a longer preset or custom range.

​
Calculate session-day usage

Use:
For a Pay-As-You-Go team, two Standard numbers connected for 30 days use:
That is USD 15 or BRL 75 at the credit purchase rate. For +55 numbers, apply the 85% country multiplier:

​
Tier rates

Each tier has one session-day rate. The number of numbers your team connects does not change it. The +55 multiplier applies to the tier rate. To earn extra credits as your usage grows, see Monthly purchase bonus. Only Pay-As-You-Go teams buy and use credits. A Free team’s one free real number uses 0 credits. See Free and Pay-As-You-Go.

​
Metered usage and spending

Outgoing calls have their own count, included allowance and overage rate. Monthly spending limits count charged number service and active pairing reservations. They do not price operational measurements or cap charges paid directly to Meta. The pricing page lists these overages per number: The breakdown shows measured usage and actual charged credits. A dash in the charge column means a charge amount is unavailable. It does not mean zero. Missing measurements show Data unavailable. For a selected number, outgoing-call progress compares this UTC month’s completed outgoing calls with its included monthly allowance. Pro shows Unlimited. Team owners and admins on Pay-As-You-Go also see the selected project’s or number’s monthly credit-limit progress, including active reservations. These progress bars use the current UTC month even when the chart shows another range. An unset credit cap shows No limit. WhatsApp storage uses GB-month for billed usage; its included storage allowance is in GB. Allowances belong to each number. Project totals do not pool unused allowances from different numbers. A number view does not assign project-wide serverless invocations to that number. Testing numbers use 0 session-day credits. An Enterprise agreement can set a negotiated Standard or Pro rate without creating another number tier.

​
Monthly spending limits

Open Usage with All projects selected to configure project limits and funding order in the Funding controls table. Select a project to see its own limit and priority above one Funding controls table for customers and numbers. For the selected project, Edit limit changes its monthly cap in place. Edit priority opens All projects → Usage to rank it against the team’s other projects. Team owners and admins can read financial controls; Pay-As-You-Go teams can edit them. Project overview cards remain read-only and link to Funding controls in Usage. For a number, open its details in Numbers and select Edit limits and priority. The Budget row action opens the same panel. For a customer, open the customer’s native detail page and select Edit limits and priority. Enter the monthly limit in credits and numeric priority, then select Save changes. An empty limit removes the cap; zero blocks new charges. Real number creation also accepts starting values. Limits reset at midnight UTC on the first day of each month. Charged service and active pairing reservations count toward the cap. Each customer’s assigned numbers share its cap. A number must fit its project, customer and individual limits. Already-paid service continues through its paid window. Transferring a number leaves past charges with the customer that owned it when charged.

​
Funding priority

In Usage, drag rows into highest-first order and select Save order. The all-projects Funding controls table ranks projects. A selected project has one Funding controls table for customers and numbers. Drag a number above a customer to give it higher priority. Enter a rank and press Enter to move any row directly. Search by resource name or ID. Filter customers and numbers by resource type, or filter projects by their limit status. Sort by name, funding order or lowest priority; project views also sort by limit amount and committed usage. Choose Funding order to drag rows. Reset view clears search, filters and sorting without discarding rank changes. Search, sorting and pagination preserve the complete order, including resources outside the visible page. Select Save order to apply rank changes. Set customer and number priority in their native detail panels. Higher numeric values receive priority. Project priority comes first. Within a project, numbers inherit their customer’s priority. A higher number priority overrides that inherited position. Number priority then breaks ties before renewal due time and number identity. Priority protects the next renewal and orders recovery; it never shortens a paid service window. Saves check the observed revisions. If another person or API request changes a setting, reload before saving. The native number and customer form saves its limit and priority atomically; a conflict leaves both settings unchanged. Organization keys use billing:read for reads and billing:manage for changes. Project and browser client credentials cannot access financial controls. Existing keys need these scopes. Read one resource without loading the team directory, or save its controls with expectedBudgetRevision and expectedPriorityRevision from that read. Directory reads accept scope=project for project-only results. Complete customer or number reorder requests require projectId; individual changes do not require a list. Priority reads also accept projectId to return one project’s funding controls. To reorder customers and numbers together, send scope: "resource", projectId, expectedRevision and a complete highest-first resources array. Each entry is { "scope": "customer" | "number", "resourceId": "UUID" }. An incomplete, duplicate, foreign or stale list is rejected without partial changes.

​
Monitor your balance

The Billing screen shows:
  • Active numbers: the number of WhatsApp numbers that are active for your team.
  • Credits used: the total number-usage credits charged to your team.
  • Credit balance: the credits that remain available to your team.
Team-wide warnings appear one day and two hours before forecast credit insufficiency. Enable Balance warnings in My Notifications for email alerts. Auto-top-up uses a separate credit threshold and charges the card saved on your team’s Pay-As-You-Go membership. The secure checkout window shows the payment methods, currencies, and final amount before you confirm a purchase.

Billing

Billing modes, number tiers, credits, and add-ons.

Sessions

See which numbers are connected.

​
Select the reporting period

Use the calendar button for a custom date range or its adjacent dropdown for a recent period. Click the month or year to jump through the calendar, select a start and end date, and apply. The timezone choices are Local and UTC. The selected range controls the usage shown in the report. See the product overview for a visual introduction.