SMS Providers & Aggregators
A dead number costs you twice: the submission you already paid for, and the route quality you carry into the next campaign. Screen the file and only live numbers reach the SMSC.
You buy termination and sell delivery, and every submission that fails is bought and not sold.
Your customers upload their own lists, and their list quality becomes your delivery rate.
You are asked why a route underperformed, and the answer is often in the file rather than the route.
One batch sent without a check pays three times: at submission, at routing, and on every batch that follows it on the same route.
A message to a disconnected number is billed on submission and never delivered. The cost lands in the receipts, after the spend.
A number keeps its range when it ports, but changes network. Route on the range and the message goes to the operator the subscriber left.
Carriers filter on sender reputation. A batch with a high share of invalid numbers damages the route, and every customer sending on it pays for that.
score.phone.validation.mnp returns the serving network. score.phone.ehlr returns the activity verdict. score.phone.scoring runs the whole cascade in one request.
carrier is the operator holding the number today, after porting, not the range’s original issuer.
line_type returns mobile, landline or voip. A landline in a mobile file is a submission that was never going to terminate.
accessibility returns valid, invalid or unknown. Where signals disagree the answer is unknown, those numbers stay separable in the export, and an unknown result is not billed.
whatsapp, telegram, facebook, instagram. OTT channels only. A number with no channel available may still be a working SMS destination, and a number carrying WhatsApp may be cheaper to reach there. Neither boolean predicts SMS termination.
phone_accessibility returns 0–10. -100 means undetermined, not zero. It ranks how reachable the number is. It is not a fraud score.
Field names are exactly as returned by the API. Full reference at doc.scoremachine.ai.
ROI calculator
The waste shows up on submission: messages billed against numbers that were never going to receive them. Put your own volumes in.
Typical for a list older than six months: 18–30%.
Validation cost per contact: $0.002600
Scale pricing · 200,000 validations a month · 100,000 contacts × 2 checks
At 1,000,000 validations a month the rate drops to $0.00140 per contact.
Net monthly saving
$444
$5,328 per year · 2.7× return on validation spend
Net monthly saving
—
Nothing is validated, so nothing is saved: every unreachable number still gets messaged. Select a validation method to see the difference.
Estimates only. SMS rates are indicative wholesale A2P prices and vary by route and volume. Validation rates are list pricing for the volume entered.
Screen a batch before it goes out, or walk through your routing with our team.
Check numbers one at a time with sequential methods before each send, or run a whole file through the batch methods before the campaign goes out.
Up to 20 requests a second, up to 10,000 numbers in one request, up to 10 concurrent jobs. Validation, MNP and eHLR answer in around two seconds.
API reference →CSV or XLSX, up to 5 MB and 200,000 rows per file. For customer lists that arrive as files rather than as traffic. Poll no more than every two seconds.
Start free →For platforms that already speak it, validation runs on the protocol the rest of the stack uses.
SMPP integration →"When Ufone switched off traditional HLR, we needed another way to screen numbers. Tested against our last HLR data, eHLR’s results were very strong."
Saša Vodopivec
Business Development Director, Bind Technologies
Walk through your routing with our team and run a sample file through it.