ML fraud scoring
Sub-second fraud probability for every inbound A2P message. Catches SMS phishing, AIT, grey-route artefacts, and trust-score anomalies before they hit the subscriber.
Machine-learning fraud detection, routing optimisation, intent classification, and sentiment analysis for messaging at scale. The same models that run inside the BroadNet network — now available as composable services for the operators and enterprises that already trust the carrier.

Line-rate fraud detection, routing optimisation, and sender-ID anomaly scoring deployed inside operator networks — trained on telemetry from 300M+ messages a day.
Intent detection, a live tool call, a RAG lookup, and a resolved answer — in Arabic and English, from one conversational model. Below is a redacted, illustrative transcript.
Illustrative example — a redacted sample transcript, not a live customer session.
Carrier AI is trained on the same network signals BroadNet has been collecting since 2003 — DLRs, route latencies, sender-ID histories, and two-way conversational flows. It's not a wrapper on a public LLM. It's models with ground truth.
Every model below is running live inside the BroadNet network right now — catching fraud, picking routes, and tagging intents on the 300M+ messages we process every day. The same models are available as services to operators and enterprises through the Carrier AI API.
Sub-second fraud probability for every inbound A2P message. Catches SMS phishing, AIT, grey-route artefacts, and trust-score anomalies before they hit the subscriber.
Reinforcement-learning router that picks the best operator path per destination, time of day, and content type. Optimises for delivery, cost, and DLR truthfulness simultaneously.
Behavioural fingerprinting on alphanumeric senders. Flags hijacked IDs, spoofed brands, and look-alike registrations before they damage your customer trust score.
Multilingual intent tagging for inbound replies — STOP, HELP, purchase, support, escalation. English + Arabic native, plus 14 additional languages tuned for MENA business contexts.
Aspect-level sentiment scoring across two-way conversations. Surfaces the segments of a campaign that drove negative reactions so you can fix the message, not the audience.
Carrier-grade detection of grey-route revenue leakage — SIM-box origination, flash-call abuse, and bypass-OTT patterns scored at line rate. Feeds the same A2P monetization loop the firewall enforces.
Model decisions are written back into the routing plane in real time — no batch jobs, no nightly retrains. The firewall, SMSC, WhatsApp, RCS, and voice connectors all consume inference from the same regional clusters with end-to-end p99 latency under 50ms.
Every message, call event, and webhook is enriched in-flight with model features — sender reputation, content embedding, route history.
Six production models — fraud, routing, anomaly, intent, sentiment, conversational — served from regional inference clusters with <50ms p99 latency.
Model decisions are written back into the routing layer in real time — no out-of-band batch jobs, no human-in-the-loop bottleneck.
{
"msg_id": "01HGN…7QF",
"sender": "MyBank",
"destination":"+971 50 ••• 4567",
"features": {
"sender_age_d": 412,
"route_dlr_truth": 0.998,
"content_emb": "<f32x768>"
},
"decision": { "label":"clean", "score":0.0021, "model":"fraud-v4.2" }
}Carrier AI is built inside a regulated carrier — not a model shop. The same compliance posture that lets us operate as a licensed messaging provider in 200+ countries governs every byte the models touch.
No PII ever leaves your tenant. Models train on hashed, aggregated network features — never message bodies, never subscriber identifiers.
Every inference is signed and persisted with the feature vector, model version, and decision. Exportable for regulators, internal audit, and dispute resolution.
Carrier AI inherits the parent network's certifications: ISO 27001:2022, ISO 9001:2015, ISO 22301 BCMS, SOC 2, plus NIST AI RMF validation and OWASP LLM Top 10 testing.
Tell us where you want a model — in your firewall, on your two-way traffic, or fronting your support queue. An AI engineer will scope the integration, share a benchmark on a slice of your real traffic, and stand up a pilot within two weeks.