1. Regulatory focus
On July 30, 2026, CRC Resolution 8308 brought bulk A2P activity carried over E.164 personal numbers into the operator fraud-monitoring framework. Operators must be able to detect unusual outbound volume, highly dispersed recipients, mechanical periodicity, lack of correlated inbound traffic, and geographic or network concentration. Where a line repeatedly exhibits these patterns, the operator may restrict messaging, report the case to CRC, and evaluate contract termination under applicable user-protection procedures.
2. Business impact
For international messaging teams, relying on local long numbers or P2P-priced routes is becoming an unstable cost strategy. OTPs, order notifications, or support callbacks may be classified as disguised A2P when they show fixed-interval bursts, one-way volume, or shared-number behavior across multiple accounts. The future operating model requires A2P traffic to use the appropriate short code, Sender ID, and approved content template, which may affect routing design, pricing, delivery monitoring, and dispute handling.
3. Operating recommendations
Segment Colombia traffic by country, customer, number, and use case, then establish baselines for volume, recipient dispersion, timing intervals, inbound correlation, and shared-number behavior. Do not mix OTP, marketing, and support traffic on the same P2P resources. Confirm the implementation phase, A2P remuneration, and short-code onboarding path with the local operator or aggregator. Preserve routing evidence, template versions, Sender ID ownership records, and documentation used to challenge false positives.