Platform overview
Everything you need in an SMS testing tool
Delivery, Sender ID, content, latency, SMSC and more, all verified on real handsets in 180+ countries.
01 · Delivery testing
Confirm every SMS reaches the handset
Send a test through your production route. A real SIM card on a real network in the destination market records what actually arrived.
Real SMS delivery status
Send test SMS to TelQ's local mobile test numbers and get real-time feedback on delivery status directly from our handsets, not just from your suppliers' reporting system.
Compare the actual receipt status against the delivery report your supplier provides. Discrepancies are flagged immediately.
Why it matters
The only way to know if a message delivered is to check from the receiving end. Trust your supplier, but verify their routes.
Fake DLR detection
Testing from TelQ's UI, you get a direct comparison of vendor's DLR and the actual receipt status. When these two do not match, it is a confirmed fake DLR.
Fake DLRs are one of the most common and costly problems in A2P SMS. TelQ uncovers them for you.
Why it matters
Fake DLRs mask a very important issue of messages not being delivered. While the issue is invisible without proper testing, the impact your end users feel is real.
Latency measurement
TelQ measures the exact time between when your SMS is sent and when it's received on our test handset. We then break it down by timestamps so you know what caused the receipt status delay.
Why it matters
Latency directly affects user experience, especially for OTP and time-sensitive messages.
02 · Content & Sender ID
Verify what your customers actually receive
Sender ID often arrives modified due to routing issues or local restrictions. TelQ shows you exactly what landed on the handset and highlights the discrepancies.
Sender ID verification
TelQ captures the exact Sender ID received on our test handset and compares it to what you sent. If there are any modifications, they get flagged.
Why it matters
Your Sender ID is your brand. A substituted or numeric Sender ID destroys trust, reduces open rates, and can expose your customers to fraud.
Content validation
TelQ compares the text you send with what's actually delivered to the handset. Any modification (added URLs, changed words, appended text) is detected and flagged.
Why it matters
Content modification can confuse and mislead your end users, damage brand trust and cause churn. TelQ helps prevent this.
Dynamic Test ID text
Craft test messages that mirror your live traffic, including WhatsApp and Instagram code formats. Customize the Test ID Text type, case, and length, then drag-and-drop to position it anywhere in your message.
Why it matters
Carriers can detect and treat testing traffic differently. A realistic Test ID Text makes your tests indistinguishable from real messages.
Detection of test ID text changes
Some routes alter codes as an anti-filtering tactic. This impacts SMS testing tools that rely on test codes for delivery matching. TelQ is able to detect these modifications and successfully match results with requests in cases where codes change to unicode and emojis or when line breaks, dashes and spaces get added.
Why it matters
In the past, these testing outcomes would be marked as negative. Having this option in your test tool means reliable test results which show text modifications instead of failed delivery.
03 · Technical attributes
See the technical details behind every delivery
For routing engineers who troubleshoot at the protocol level. TelQ returns SMSC data, raw PDU, encoding details, and UDH parameters from every delivered test.
SMSC verification
Once your test message reaches our handset, TelQ retrieves the SMSC number and performs a lookup. This helps you compare the delivering SMSC against your supplier's claims.
Why it matters
The SMSC information comparison can indicate whether the route used to deliver the message was direct or not.
Access the complete raw PDU of every delivered test message, including UDH settings, encoding details, and all technical parameters.
Manually specify the data coding scheme for your test messages. Test compatibility across encoding formats.
Verify that your supplier correctly handles long messages split across multiple SMS segments.
Send test SMS with customizable UDH parameters to test your supplier's SMSC handling of advanced SMS features.
04 · Routing & Portability
Catch delivery failures on ported numbers
Ported numbers are a common silent failure point in SMS routing. TelQ covers a wide range of ported network combinations.
Ported number testing
TelQ includes ported numbers in our test network: real SIMs that have been ported between operators.
Many routes silently fail on ported numbers. They deliver to the old network, or not deliver at all.
Why it matters
In markets with high portability rates, a significant percentage of your traffic may be to ported numbers. Failing to support MNP means messages simply don't arrive.
05 · Scheduling & Automation
Test continuously and proactively
Set up automated test schedules and let TelQ issue tests for you around the clock. Set up notifications and catch degradation the moment it happens.
SMS test scheduler
Configure recurring tests to run automatically at any interval (hourly, daily, custom, or randomised) to avoid detection by your supplier.
Set alert conditions and get notified when any test meets them, or review the full report at the end of each cycle. Every scheduled test runs exactly like a manually issued test: real SIM cards, real delivery data, complete result sets.
Why it matters
Route quality doesn't degrade on a schedule. Continuous testing is the only way to catch problems in real time.
Full REST API
TelQ's REST API lets you trigger tests, retrieve results, and receive callback notifications programmatically.
SDKs available for Java, Python, PHP, and Shell. Most teams are up and running in under an hour.
Why it matters
Automated testing built into your pipeline catches problems before they affect live traffic.
Get real-time test result updates over callback URL/webhook. Detect fake DLRs, content modifications and latency issues as they happen.
Enjoy all the benefits of TelQ's advanced testing settings in your own SMS platform. Optimize your routing automatically based on test results.
Integrating via REST API is done in a few simple steps. Testing uses only a couple of endpoints, so it stays simple.
06 · Beyond SMS testing
Non-SMS channel detection
Some vendors switch your traffic to a different channel to cut costs. TelQ detects it and shows you exactly what happened on the handset.
RCS testing and detection
TelQ is able to detect RCS delivery, so you can either submit SMS to see if your vendor translates it to RCS to cut cost, or test your own RCS messages. Get RCS-ready test numbers in the UI or through the REST API, send your test as usual - you'll be able to check delivery, sender ID and content exactly as they arrived.
Why it matters
Vendors may terminate SMS as RCS to lower their costs. Seeing the channel used lets you hold suppliers accountable for the route you're actually paying for.
Flash call detection
Coming soonSome vendors deliver SMS as a voice call instead of a text message to cut costs. Turn flash call detection on when you run a test, and TelQ flags it the moment it happens.
Why it matters
Receiving messages as calls instead of texts can turn into a compliance issue. Test markets where flash calls are common and catch them before your end users do.
07 · Analytics
Track quality over time, not per test
Individual tests tell you what's happening now. Analytics tell you whether things are gradually getting better or worse, and when performance started degrading.
Track delivery rates, latency, fake DLR frequency, and content accuracy per route over time.
See test performance broken down by country, network, and time period.
Export test results in structured formats for internal reporting and route quality tracking.
Run parallel tests across multiple suppliers and compare results side by side.
See it in action
Every feature on this page is available from day one. Request access and we'll get you started.