Network operations staffed around the clock
Skyroute
EN · EnglishEN
Talk to salesRequest access
← All field notes
OPERATIONSBy Skyroute editorial

Verified identity before traffic

Sender and caller identity checks are part of a safe send or call, not an afterthought.

Route signal diagram for Verified identity before traffic
Route signals, illustrated.

The SMS send path checks that the sender ID is approved for the account. A destination may also require registration or a matching template before A2P traffic can proceed. The send form gives a reason when a request is blocked.

Voice calls use a verified caller ID. This prevents an account from presenting an arbitrary number as the origin of a call. Account standing and prepaid funds are checked before traffic is authorized.

These checks belong on the server as well as in the console. A client-side form can help explain a problem early, but an API request must receive the same decision.

For business SMS, collect the sender name, ownership evidence and any destination registration or template details before approving traffic. In India, domestic A2P traffic may require DLT entity, sender and template registration. The exact rules depend on traffic type and operator; validate the current requirements for the campaign before sending.

A caller ID follows a similar ownership principle. The account should prove control of the number before the platform permits it as an outbound identity. An inbound number purchased on the account can be bound to an IVR flow or SIP line, but that does not authorize presenting an unrelated number.

The server should check identity again when the request is executed, including a scheduled SMS or queued call. If approval was withdrawn after scheduling, the job must stop with a clear reason. A rejected request should not debit the wallet or create an ambiguous queued state. Keep the verification status visible in the console so the operator knows which identity can be used.

END OF NOTEBack to field notes