No, not every authentication request will result in a phone call. Authentication Requests are pre-call API or SIP requests submitted to authenticate a call before it is delivered. Because they occur before the call is completed, they should not be interpreted as a direct measure of call volume, instead, they can be considered as the number of times a notification is sent to indicate an outbound call is taking place.
Why the Numbers May Differ
There are several reasons Authentication Requests may not align with Treated Calls, Continued Calls, or total call activity:
- Not every authentication request results in a phone call. Some organizations send authentication requests for the purpose of system health checks or testing activity. This means they are generating an API or SIP request but are not actually generating a call. These requests are recorded, but no corresponding call is placed.
- Some calls are delivered to destinations that do not support branding or reporting. Examples include landlines or networks outside supported carrier coverage. While the authentication request may have intended to generate a branded call, the destination was not capable of receiving branding.
- Reporting metrics measure different parts of the call lifecycle. Authentication Requests represent pre-call activity, while Treated Calls and Continued Calls represent call outcomes. Because these metrics capture different events, a one-to-one relationship is not expected.