Proprietary technology · Patented by Otoblue

SmartRouting¼ — The algorithm that replaces your dispatcher

In under 100 milliseconds, SmartRouting¼ identifies the geographic zone, selects the priority technician, checks availability over 14 days and confirms the appointment — while your customer is still on the phone.

O(1) index on postal codes
Priority cascade P1→P2→P3
Zero double bookings

The problem

Without an algorithm, dispatch is your bottleneck

Every call requires a manual decision: which zone? which technician is available? which time slot? It's slow, error-prone, and impossible to sustain at 10pm.

5 to 15 minutes

The average time for a human dispatcher to find the right technician, check their schedule and confirm a slot — when they're reachable.

Meanwhile, the customer waits or hangs up.

Conflicts & duplicates

Without a centralized system, two simultaneous calls can result in the same time slot being booked for two different customers.

Result: no-show, unhappy customer, double-booked technician.

No 24/7 coverage

Manual dispatch stops when your team stops. Evening calls, weekends, and holidays go unanswered.

40% of requests come in outside business hours.

SmartRoutingÂź in action

Le bon technicien, dans la bonne zone, en moins de 100ms.

Fini le "je vais vérifier et je vous rappelle". L'algorithme trouve le créneau disponible pendant que le client parle encore.

Code postal

13009

Marseille 9e

Zone identifiée

Zone Sud

Index O(1) · ~2ms

Technicien assigné

Jean · P1

Priorité 1 · Lundi

Créneau libre

Jeudi 9h

Sur 14 jours · ~100ms

RDV + SMS

✓ ConfirmĂ©

Envoi immédiat

â†ș Cliquez pour rejouer

Temps pour trouver un créneau

Dispatcher humain~5 min
Otoblue Smart Routing< 100ms

Ce qui rend l'algo rapide

  • Pas de VRP complet — insertion locale O(n)
  • Index sur code_postal → O(1) lookup
  • Cascade par prioritĂ© — P1 → P2 → P3
  • FenĂȘtre de 14 jours
  • SĂ©paration claire : l'IA comprend, le code calcule

Architecture

How SmartRoutingÂź computes in real time

No on-the-fly machine learning, no full VRP solving. A layered architecture built for speed and reliability.

01

Zone resolution — O(1)

The postal code is the key of a pre-computed hashmap. The geographic zone is returned in ~2ms, with no loops, no SQL joins. If the postal code is missing from the index, the adjacent zone fallback activates immediately.

02

Technician selection — Priority cascade

Technicians are ordered by priority (P1, P2, P3) for each zone. The algorithm tries P1 first: if unavailable within the window, it falls back to P2, then P3. This cascade guarantees the best available technician without iterating all combinations.

03

Slot search — Local insertion O(n)

The search window is capped at 14 days. The algorithm does not solve the full travelling salesman problem (NP-hard) — it performs local insertion: it finds the first free slot that meets all constraints (duration, hours, technician working days).

04

Atomic write + notification

The appointment is written to the database with a transactional lock to prevent concurrency conflicts (two simultaneous calls cannot book the same slot). The confirmation SMS is sent immediately via Telnyx.

Benchmark — Computation time

Experienced human dispatcher5–15 min
Traditional scheduling software~30 sec
SmartRoutingÂź Otoblue< 100ms

Design principles

  • Clear separation: AI / deterministic algorithm

    AI understands language, code computes — not the other way around

  • No machine learning for dispatch

    Deterministic = predictable = zero surprises in production

  • Pre-computed index, never rebuilt on-the-fly

    Zone resolution stays O(1) regardless of load

  • Transactional lock on appointment writes

    Two customers cannot be booked on the same slot

  • 14-day bounded window

    Controlled complexity, no temporal drift

Configuration

Tailor SmartRoutingÂź to your organization

1 technician or 20, 1 zone or 50 — the engine adapts without redeployment.

Geographic zones

  • Map postal codes → named zone
  • Adjacent zones for P2 fallback
  • Overlap allowed between zones
  • Add / remove zones in real time
  • Example: Zone North (SW1–SW3), Zone South (SE1–SE5)

Technicians & priorities

  • Profile per technician: covered zones, working days, hours
  • Priority level P1 (senior) → P3 (junior)
  • Multi-zone: one technician can cover N zones
  • Configurable leave and unavailability
  • Example: John P1 Zone South Mon–Fri 8am–6pm

Business rules

  • Duration per service type (e.g. full setup = 2h)
  • Minimum gap between appointments (travel time)
  • Proposal window: 7, 14 or 21 days
  • Max appointments per day per technician
  • Custom message if no slot is found

Example: company with 3 technicians, 2 zones

Configuration

Zone A — codes SW1–SW3 → John (P1), Mark (P2)

Zone B — codes SE1–SE5 → Luke (P1), John (P2)

Rule — full setup = 3h, maintenance = 1h30

Window — 14 days, max 4 appts/day/technician

Scenario — incoming call

2ms Postal code SW2 → Zone A identified

5ms John (P1) → schedule checked → busy Thursday

8ms First free slot: Friday 2pm

95ms Appointment written + SMS sent to customer

Total: 95ms — the customer is still on the phone

Frequently asked technical questions

Ready to automate your dispatch?

SmartRouting¼ is included in all Otoblue plans — no technical setup required.

    SmartRouting¼ Algorithm – Dispatch in <100ms | Otoblue