
MCeTS had a problem with its telecom stack. The company, which builds software platforms for transportation operators across Peru and Latin America, had stitched together multiple providers for voice calls, SMS, and mobile data connectivity. Each provider covered a piece of the map. None of them covered all of Peru, let alone the broader LATAM region.
As a result, calls dropped on rural routes. Messages failed to deliver across carrier boundaries. SIM cards that were supposed to keep bus-mounted IoT sensors online went dark when buses crossed into coverage gaps. And when something broke, there were too many vendors to call, each pointing at the other.
MCeTS replaced that patchwork with a single provider: Telnyx.
The first product MCeTS deployed was the Telnyx Messaging API. Passenger notifications are the core use case. When a bus is delayed, when a gate changes, when a schedule updates, MCeTS software triggers an SMS to every affected passenger. Delivery reliability matters here. A notification that arrives late is worse than no notification at all, because it erodes trust. Telnyx operates its own carrier network, which means messages route directly rather than hopping through intermediaries. For MCeTS, that translated into consistent delivery rates across Peruvian carriers and, as they expanded, across Colombian, Ecuadorian, and Mexican carriers as well.
Voice was the next layer. MCeTS uses the Telnyx Voice API to power automated departure calls and schedule-change alerts for passengers who prefer voice over text. In regions with lower smartphone penetration, a voice call is often the only reliable way to reach someone. Telnyx provides local Peruvian phone numbers and carrier-grade call termination, so those calls connect and sound clear rather than getting flagged as spam or dropping mid-message.
For the buses themselves, MCeTS deployed Telnyx Wireless SIMs. Each long-haul bus carries GPS and telemetry sensors that report position, speed, and engine status back to the MCeTS platform. That data flows over cellular connections powered by Telnyx SIMs. When a bus is winding through the Andes between Arequipa and Cusco, the connection cannot drop. Telnyx SIMs aggregate coverage across multiple carrier networks in each country, automatically switching to the strongest available signal. That multi-carrier fallback is what keeps the fleet visible on the MCeTS dashboard even in mountainous terrain with patchy coverage.
As MCeTS scaled beyond Peru, voice infrastructure became a new requirement. The company added Telnyx SIP Trunking to connect its cloud-based PBX and contact center systems to the PSTN in multiple countries. SIP trunking gave MCeTS a single voice backbone for internal communications between regional offices and for handling inbound customer service calls from operators and passengers. Rather than provisioning separate trunking in each country, MCeTS routes everything through Telnyx, with local numbers and compliant termination in each market.
The consolidation mattered operationally. Before Telnyx, MCeTS managed separate contracts, separate dashboards, and separate support escalations for SMS providers, voice carriers, and IoT connectivity vendors. Each integration was its own maintenance burden. Each outage required figuring out which vendor caused it before anything could be fixed. With Telnyx, MCeTS has one platform for messaging, voice, wireless data, and SIP trunking.
That simplicity becomes more important as MCeTS grows. The company is now deploying its platform across Central America and has pilots running in Brazil. Each new country adds regulatory requirements, carrier relationships, and numbering compliance. Telnyx already holds telecom licenses and offers local numbers in over 140 countries, including dedicated PSTN replacement infrastructure across LATAM. MCeTS does not need to find a new carrier partner for every market. They plug into Telnyx and the coverage is already there.
Looking ahead, MCeTS is exploring Telnyx Voice AI Agents to handle inbound passenger inquiries automatically. Today, when a passenger calls a bus operator's customer service line, they wait in a queue. Voice AI agents could answer routine questions about schedules, routes, and baggage policies without any human in the loop, reducing wait times and freeing operator staff for complex cases. Because Telnyx runs inference at the edge on its own GPU infrastructure, those AI-powered conversations would run with sub-200ms round-trip latency, meaning the interaction feels natural rather than robotic. The same carrier network that delivers the call also runs the AI, so there are no handoffs between a telephony provider and an AI vendor.
For transportation companies across Latin America, the MCeTS story is instructive. Telnyx's carrier-owned network, local number availability across LATAM, and multi-product API platform make it the infrastructure layer for transportation technology companies scaling across the region. MCeTS proved it in Peru. The same architecture works everywhere buses run.