Xsquare Technology builds custom voice and messaging software on Telnyx: SMS and MMS, programmable voice and IVR, number porting, US 10DLC registration, SIP trunking set-up, CRM integrations and dashboards. We build on your own Telnyx account, so the numbers, the code and the billing relationship with Telnyx stay yours.
Telnyx describes itself as a licensed carrier that runs its own private IP network, and it gives developers two ways to control calls: TeXML, which is designed to be compatible with Twilio’s TwiML, and an event-driven Voice API. Below is what we build on it, how the main pieces work, and what to plan for if you are moving from Twilio. If you are still choosing a provider, read our Twilio vs Plivo vs Telnyx guide first.
What we build on Telnyx
- Business texting. Two-way SMS and MMS, reminders, alerts, inbound replies routed to the right person, and opt-out handling.
- Voice and IVR. Call menus, routing by caller or time of day, call forwarding, voicemail, recording and conference calls.
- Call-control apps. Click-to-call, call transfers and bridging, and dialer-style workflows built on the Telnyx Voice API.
- SIP trunking. Connecting an existing PBX to the phone network over Telnyx SIP trunks.
- Number porting. Moving your existing numbers to Telnyx and configuring them before the switch.
- CRM integrations. Calls and texts logged against contacts in HubSpot, Salesforce, Zoho or a custom CRM or web app.
- Dashboards and apps. Web screens for conversations, call history and follow-ups, plus mobile apps when your team or customers need one.
TeXML or the Voice API: two ways to build voice
TeXML is an XML language for call flows. When a call reaches a number assigned to a TeXML application, Telnyx sends a webhook to your server, and your server returns TeXML instructions that Telnyx runs in order. Telnyx built TeXML to make moving from Twilio easier: it supports the common TwiML verbs, including Dial, Gather, Play, Say, Record, Redirect, Hangup, Stream and Enqueue, and it offers REST endpoints for calls, conferences and recordings that mirror Twilio’s. Telnyx’s compatibility table also lists TwiML features that TeXML does not support, so every flow still needs checking.
The Voice API (previously called Call Control) works differently. Telnyx sends your application an event for each stage of a call, and your code replies with commands such as answer, speak, gather digits, transfer, bridge, record or hang up, each sent to an endpoint for that specific call. This gives fine-grained control, which suits dialers, call-center tools and calls that change direction based on live data.
Telnyx’s documentation advises against mixing TeXML and Voice API commands on the same call. We pick one per application: TeXML when you are migrating existing TwiML or the flow is a simple sequence, and the Voice API when the app needs to react to every call event.
Messaging on Telnyx
Telnyx organises texting around messaging profiles. You assign numbers to a profile, and the profile holds settings such as the webhook address for incoming messages. A profile can also use a number pool: your app sends a message without naming a sender, and Telnyx picks an eligible number from the pool. We set up profiles, handle incoming messages and delivery receipts, and store conversations so your team can see the full history.
10DLC registration on Telnyx
Business texting to US mobile numbers from standard 10-digit numbers needs 10DLC registration. On Telnyx you register a brand with your business details, have the brand vetted (Telnyx notes that the vetting score affects your throughput), register a campaign describing your messages, including sample messages, the opt-in flow and your help and opt-out keywords, and assign your numbers to the campaign. These steps can be done in the Telnyx portal or through the API. Campaigns go through The Campaign Registry and carrier review, so we prepare the opt-in wording, privacy policy and sample messages carefully. Our guide to rejected 10DLC campaigns explains the common reasons for rejection; it is written for Twilio, but the review rules are the same on Telnyx.
Porting numbers to Telnyx
Telnyx ports numbers through porting orders. Its FastPort feature checks the details on your Letter of Authorization as you enter them and flags mismatches, which avoids a common cause of delays with the losing carrier. For eligible US and Canadian numbers, Telnyx also offers on-demand activation: once the firm order commitment (FOC) date is confirmed, you choose when to activate within that day’s activation window, and the numbers port automatically at the end of the window if you do nothing. We use that window to switch your numbers at a quiet moment and test calls and texts right away.
Moving from Twilio to Telnyx
- List every TwiML flow, webhook and Twilio feature you use, and check each against Telnyx’s TeXML compatibility table.
- Rebuild or adjust the flows, and move any REST calls to Telnyx’s endpoints and API-key authentication.
- Set up messaging profiles and register your 10DLC brand and campaign on Telnyx.
- Test everything on a new Telnyx number before porting the live ones.
- Port the numbers, switch over in the activation window, and keep the old account until everything checks out.
Examples of our communications work
Our published communications case studies are built on Twilio rather than Telnyx: DialEdge AI, a calling dashboard for sales and support teams, and Textjin, an SMS campaign tool. Dashboards and integrations like these use the same building blocks on Telnyx. See our Twilio development services and Plivo development services for the other platforms we build on.
How a Telnyx project with Xsquare runs
We start by reviewing your numbers, current provider, call flows and the systems you need connected. Then we agree a written scope in stages, build and test on your Telnyx account using spare numbers, and switch live traffic only when you have signed off. You get the code, documentation and admin access at handover, and we sign an NDA with clients as standard. Our team is based in India and works with clients in the USA, Canada and other countries. Contact us to talk through your Telnyx project.
Frequently asked questions
Can our existing TwiML run on Telnyx?
Often with small changes, because TeXML supports most common TwiML verbs. Some TwiML features are not supported, so we check each flow against Telnyx’s compatibility list and test it before you port any numbers.
Should we use TeXML or the Telnyx Voice API?
TeXML suits sequential call flows and migrations from Twilio. The Voice API suits apps that react to each call event, such as dialers and call-center tools. Telnyx advises against mixing the two on one call.
Do we need 10DLC registration to text US numbers from Telnyx?
Yes, for business texting from standard US 10-digit numbers. You register a brand and a campaign, and assign your numbers to it.
Can you show Telnyx examples?
Our published case studies, such as DialEdge AI and Textjin, run on Twilio. Telnyx builds use the same patterns, and we can explain how your project would work on Telnyx before you start.

