How Do VAS Numbers Work for Voice Monetisation?
A premium-rate number can turn an inbound call into measurable voice revenue, but only when billing, routing and reporting align. So, how do VAS numbers work in practice? They provide a telephone access point for a value-added service, apply the relevant destination tariff to eligible calls, route the traffic to the service, and create the records used to calculate a revenue share.
For call centres, IVR operators, audiotext providers and traffic resellers, the number itself is not the commercial model. The model is the full chain behind it: a compliant service, a reachable number, a carrier billing agreement, clean traffic delivery and verified call data. If one part of that chain fails, high call volume alone does not produce a dependable payout.
What a VAS number actually is
VAS means value-added service. In voice monetisation, a VAS number is commonly a premium-rate or shared-revenue telephone number associated with a service beyond standard voice connectivity. The caller may reach recorded information, entertainment content, a consultation line, a live agent, an interactive menu or another approved voice experience.
The caller is charged according to the tariff set for that number and destination. Depending on local regulation and carrier arrangements, this may be charged per minute, per call, or through another defined billing model. The originating operator collects the charge from the caller, while carriers and other parties in the delivery chain retain their agreed portions. The remaining eligible revenue is shared with the service provider or traffic partner.
This is why the same service concept can perform very differently across countries. A destination may have a higher advertised rate but lower mobile reachability, stricter eligibility rules or a smaller payable share. Another may offer a lower rate but stronger answer rates and more predictable settlement. Commercial value comes from realised, payable minutes, not from the headline tariff alone.
How do VAS numbers work from dialling to payout?
The process begins when a caller dials the allocated number from a supported network. Their originating operator recognises the destination and applies the relevant charging logic. The call is then handed through one or more carrier routes towards the platform or termination partner serving the number.
At the delivery point, the number maps to a destination selected by the partner. That may be a SIP endpoint, an IVR, a call centre queue or another configured voice route. The caller hears the service only once the call has been answered and connected. The exact billing and qualification point depends on the destination agreement, which is why technical testing matters before traffic is scaled.
During and after the call, network elements create call detail records, usually called CDRs. These records commonly include the called number, call start time, answer time, duration, originating network information where available, disposition and route. The platform uses this data to present live or near-real-time statistics, while the carrier uses validated records for formal settlement.
A simplified revenue calculation is:
Payable revenue = eligible billed usage × agreed revenue-share rate
In reality, each part needs definition. Eligible usage may exclude unanswered calls, very short calls, unsupported originating networks, invalid CLI presentation, duplicate attempts, fraudulent patterns or traffic that breaches the destination's service rules. The agreed share may vary by country, number range, network type or billing interval.
There can also be a time difference between reporting and final payment. Live statistics are operational data, useful for monitoring campaigns and diagnosing routing issues. Carrier reconciliation determines the settled amount after validation windows, adjustments and any applicable compliance review. A reliable partner should make that distinction clear rather than presenting estimated earnings as finalised revenue.
The service and the number are separate layers
A common mistake is to treat a VAS number as a product that creates value by itself. It is better understood as the access and billing layer. The content, call handling and user journey are separate, but they directly affect commercial results.
An IVR that takes too long to answer can reduce answered calls. A call centre with insufficient agent capacity can create abandoned traffic. Poor audio quality, unclear pricing disclosure or irrelevant content can lead to complaints, short durations and service restrictions. Conversely, a clear, properly provisioned service helps maintain legitimate engagement and stable call patterns.
For an operator, this separation creates useful control. You can allocate numbers by campaign, language, media source or destination, while sending each number to the appropriate IVR or queue. That makes it easier to compare traffic quality without changing the entire service architecture.
The metrics that determine whether traffic is valuable
Raw minutes are only one part of the picture. Telecom partners need to read performance across the call path and the commercial path.
ASR, or answer-seizure ratio, shows the proportion of attempted calls that receive an answer signal. A weak ASR can indicate a routing problem, capacity constraint, invalid dialling pattern or poor quality traffic. ACD, or average call duration, helps show whether callers are reaching and remaining on the intended service. Neither metric should be judged in isolation: unusually high durations can be as worthy of investigation as unusually low ones.
The most useful operational view also separates attempts, answered calls, billable calls, total duration, eligible duration and estimated revenue. When a discrepancy appears, this breakdown narrows the question. Is traffic failing before answer? Are calls connecting but not qualifying for billing? Is the issue confined to one carrier, number range, campaign or hour of day?
For that reason, real-time statistics are more than a dashboard feature. They allow a traffic manager to pause a poor route, investigate a sudden change in ASR, check a new number before launch and avoid sending additional traffic into an unresolved issue. TrustCaller provides live call statistics and CDR reporting to support this level of operational visibility.
Why destination rules and compliance matter
Premium and revenue-share services are regulated differently across international markets. Pricing notices, service descriptions, age restrictions, opt-in requirements, maximum charges and permitted content can vary by country and sometimes by originating network. A number that is valid for one use case may not be suitable for another.
Compliance is not simply an administrative task completed at onboarding. It affects traffic acceptance and long-term payment reliability. Carriers may review unusual spikes, repetitive calling behaviour, very short call patterns, misleading promotion or traffic inconsistent with the declared service. Where evidence is missing, revenue may be withheld, reversed or the number may be suspended.
Partners should retain clear campaign records, keep the caller journey aligned with the approved service description, and make pricing communication appropriate for the market. They should also ensure that traffic sources are legitimate and that calls are genuinely initiated by users. These controls protect the service, the carrier relationship and the ability to operate at scale.
What to check before allocating traffic
Before launching a number, confirm the commercial and technical conditions in writing. The payable rate should state the relevant country, number type, originating networks, billing unit and any exclusions. Ask whether the displayed rate is estimated or settled, how often CDRs update, and how payment adjustments are handled.
Technical checks should cover number activation, CLI requirements, supported codecs, SIP configuration, expected answer behaviour and failover handling. Place controlled test calls from the intended network types where possible. Check that the correct IVR or endpoint answers, timestamps are accurate, audio is clear and the calls appear in reporting as expected.
It is equally useful to agree escalation routes before a campaign starts. If ASR drops sharply or a number becomes unreachable, a support contact who can interpret carrier-side information is more valuable than a generic ticket response. For multi-country operators, this is often the difference between a short interruption and a day of unusable traffic.
Choosing numbers for durable performance
The best destination is not always the one with the highest payout shown on a rate sheet. Assess payout alongside reachability, historical route stability, settlement terms, local service requirements and the fit between the tariff and your audience. A campaign with modest rates and consistent eligible usage may outperform a higher-rate destination with frequent validation losses.
Use separate numbers where meaningful attribution is required. This gives media buyers and resellers a clearer view of which source creates answered, eligible calls, rather than just which source generates dial attempts. Review results over enough time to account for daily patterns, network changes and carrier settlement cycles.
A VAS number works best when it is treated as part of a controlled operating system: approved service design, correct routing, transparent CDRs, active monitoring and realistic settlement expectations. Build that discipline before increasing volume, and each new destination becomes easier to assess on evidence rather than assumption.
Get your IPRN test numbers — instant activation
Create your account