DISHI
Sign in
SYS/ROUTE — FABRIC ONLINE
Global Omni-Channel Communication Dispatch System

One API.
Every channel. Every country.

Dishi — the global omni-channel communications wholesaler. Before every message, the engine analyses its recipient and picks the best channel and route — SMS, WhatsApp, Voice, Telegram, Instagram, LINE, RCS or Email. You send once. The network decides the rest.

Start routing Read the API
LIVE ROUTING DECISIONS
SIMULATED FEED
08
CHANNELS
190+
DESTINATIONS
20+
CARRIER REGIMES
24/7
AUTONOMOUS
Global send windows window open quiet hours
NEW YORK
--:--:--
SÃO PAULO
--:--:--
LONDON
--:--:--
BERLIN
--:--:--
MOSCOW
--:--:--
MUMBAI
--:--:--
TOKYO
--:--:--
SYDNEY
--:--:--

01 / Omni-Channel Matrix

Every channel your customers already live on.

Eight channels behind one endpoint. The router treats channels as interchangeable instruments — scored per recipient, per message — and falls back across them automatically when one cannot land.

SMS

The universal floor

Sm · 01 / 08
REACH
5.0B handsets
COST INDEX
1.0× baseline
LATENCY
~1s
BEST FOR
OTP, alerts, unconditional global reach
Automatic fallback chain
whatsappsmsemail

Fallback executes automatically and is invisible to the recipient.

+1NORTH AMERICA+44LONDON+49BERLIN+33PARIS+81TOKYO+91MUMBAI+55SÃO PAULO+52CDMX+61SYDNEY+7MOSCOW+65SINGAPORE+971DUBAI+82SEOUL+34MADRID+31AMSTERDAM+27JOHANNESBURG+1NORTH AMERICA+44LONDON+49BERLIN+33PARIS+81TOKYO+91MUMBAI+55SÃO PAULO+52CDMX+61SYDNEY+7MOSCOW+65SINGAPORE+971DUBAI+82SEOUL+34MADRID+31AMSTERDAM+27JOHANNESBURG

02 / The Shift

Messaging is no longer a pipe. It is a routing problem.

The industry still sells you a pipe: one number, one route, one price — take it or leave it. Dishi replaces the pipe with a fabric: a living mesh of channels and carrier routes that re-decides the optimal path for every single message, every single time.

Yesterday

Static binding

  • One sender, one route — bound forever
  • No cost awareness; you pay the list price
  • An upstream outage is a lost message
  • One country's rules, hard-coded
Dishi

Autonomous routing

  • Every message re-analysed and re-routed in real time
  • Least-cost path at committed quality, always
  • A failure is a reroute, never a loss
  • Carrier rules of 20+ regions, encoded as data

03 / The Routing Engine

Three layers of decision, in milliseconds.

Every message descends through three strata. Each layer answers one question, then hands the message down. The whole descent completes before your HTTP request returns.

03
LAYER 03 — CHANNEL

Which channel should carry this message?

explicit choicecompliance mandaterecipient preferencecost × deliverability

→ channel + fallback chain

02
LAYER 02 — ROUTE MESH

Which upstream path is optimal right now?

per-destination costlive delivery rateroute reputationcapacity headroom
score = 0.40·cost + 0.35·delivery + 0.15·reputation + 0.10·headroom

Recomputed on every delivery receipt, per route, per country.

→ ranked route list + auto-failover

01
LAYER 01 — CARRIER INTELLIGENCE

May we send — and when?

per-carrier sliding windowsbrand daily capsquiet hourscontent rulesregistration state

A message that would be filtered is deferred to its window — not sent to die.

→ dispatch, or defer to the lawful window

04 / Autonomous Analysis

Every delivery receipt re-trains the network.

Routing decisions are not configuration; they are measurements. The engine closes the loop on every message, so the mesh you use at noon is smarter than the one you used at midnight.

STEP 01

Execute

The message is dispatched on the top-scored route.

STEP 02

Observe

Delivery receipts stream back through webhooks, in real time.

STEP 03

Score

Sliding-window delivery rate, latency and cost update per route, per country.

STEP 04

Reroute

Degrading routes lose weight; recovering routes regain it. No humans involved.

Per-route delivery rate

Live, per country, per channel

Cost vs. optimal

What you paid vs. what the mesh would have

Fallback trigger rate

How often the chain saved a message

Time-to-deliver

p50 / p95 per destination

05 / Global Carrier Intelligence

Carrier rules are data, not folklore.

Every destination has its own physics: rate windows, quiet hours, registration regimes, content filters. The engine encodes them per carrier and per country — and plans around them before you press send.

RegionRegimeEngine behavior
United StatesCampaign-scope 60s sliding windows · brand daily capsThrottle and defer — never burst
United Kingdom & EUPer-sender rate windows · GDPR quiet hoursTimezone-aware best-send windows
IndiaDLT-registered sender IDs mandatoryAuto-switch channel when unregistered
JapanCarrier content filters · strict templatesContent adaptation + LINE fallback
BrazilHigh-filtering SMS routesWhatsApp-first routing
CISWeak SMS economicsTelegram-first preference

Quiet hours are always enforced in the recipient's local time zone.

06 / One Integration

Integrate once. Never think about routing again.

One endpoint. Declare the intent — channel: "auto" — and the engine returns more than a message id: the chosen channel, the route, the score, and the fallback chain it will walk if anything degrades.

REQUEST
POST https://api.frankdu.co/api/v2/messages/send
Authorization: Bearer ••••••••••••
Content-Type: application/json

{
  "to": "+44 7700 900000",
  "body": "Your verification code is 483920",
  "channel": "auto",
  "fallback": true
}
RESPONSE — DECISION INCLUDED
{
  "id": "msg_9f27c1",
  "status": "queued",
  "decision": {
    "channel": "whatsapp",
    "route": "eu-west/mesh-2",
    "score": 0.93,
    "reason": "recipient_preference",
    "fallback_chain": ["sms", "email"]
  }
}
Full API reference

07 / Compliance & Trust

Compliant by construction, not by policy PDF.

Consent & STOP automation

Opt-out intents are detected and enforced per sender number, per channel — globally.

Quiet-hours engine

Local-time enforcement per destination, with automatic deferral to the next lawful window.

Registration workflows

Guided brand and campaign registration for regulated routes, handled in-product.

Data discipline

EU-hosted infrastructure, GDPR-aligned processing, a full audit trail per message.

Route your first message.

One API key. Every channel. Every country. The mesh is already warm.

Start routing Read the docs

DISHI — THE GLOBAL OMNI-CHANNEL COMMUNICATIONS WHOLESALER