RoadAssist

Sign in with
your phone.

Real OTP against the live API. In development the server returns the code so you can sign in with no SMS gateway configured.

Namaste.

Signed in.

Hold to escalate — a deliberate gesture, so a pocket press never calls a responder. A model-detected crash always waits for your confirmation; it can never dispatch on its own.

  • LocationChecking…
  • NetworkChecking…
  • ContactsChecking…

Add your vehicle

Assistance is dispatched against a specific vehicle, so this comes first.

Trip Guardian.

Prediction happens while you still have signal; everything is cached here for when you don't. Dead-zone risk is learned from this platform's own device telemetry — a heuristic, not carrier coverage data.

Request assistance.

Describe the fault and the rules engine names a likely cause before you book — so you pick the right service, not the first one in the list.

  1. 1Vehicle
  2. 2Problem
  3. 3Location
  4. 4Service
  5. 5Mechanic

Step 1Which vehicle?

Vehicle

Step 2What happened?

OBD-II fault codes — optional, if you have a scanner

Step 3Where are you?

Not checked yet We use your device location so the mechanic is sent to the right place.

Step 4Which service?

Search radius

Step 5Find a mechanic

Sent only with your device's GPS position. With no fix nothing is sent unless you choose the NH-48 demo point (demo only) in step 3, for this one booking. Offline? A booking needs a connection — live dispatch does not work off-grid, so nothing is queued. SOS does.

Your rescue.

No active bookingRequest assistance and the live rescue appears here.

Off-grid mode.

RoadAssist doesn't stop when the network stops. Your emergency information is held on this device and sends itself the moment a connection returns.

What this device can do right now

Available

  • GPS position
  • Cached maps
  • Local diagnosis
  • Emergency instructions
  • Offline incident storage

Unavailable

  • Live mechanic dispatch
  • Cloud synchronisation
  • Live ETA
  • Live provider tracking

Cached map

No snapshot

Nothing has been cached on this device yet. Open the live map once while online and the last view is kept for when you are not.

Sync journal

Empty

Every off-grid operation, with the operation id the server de-duplicates on. Nothing leaves this list until the server has acknowledged it.

Storage & retention

Checking…

Your activity.

Settings & devices.

Emergency contacts

—

Texted when you confirm an SOS, in priority order — if this server has a live SMS provider. The SOS screen says which happened; without one, the text is only logged.

Vehicle documents

—

Insurance, PUC, RC and permit renewal dates. An expired PUC is a fine at the next checkpoint, and nobody remembers the date.

Emergency medical

Not set

Only you can read this. A responder can open it during an active SOS of yours — they must give a reason, it is written to a tamper-evident log, and you are told it happened.

Offline queue

Empty

Actions taken with no signal wait here and replay idempotently — the server journals each one by id, so a replay never duplicates a booking.

Off-grid mode

—

An SOS raised with no connection becomes an incident stored on this device — with its own reference, your GPS fix and an encrypted sync journal — and sends itself when signal returns. Nothing is ever claimed to have been transmitted when it has not.

Bluetooth device

Experimental

Pair an OBD-II dongle or a RAKSHA edge unit over Web Bluetooth. Needs a Chromium browser and real hardware — this build only lists the chosen device; telemetry pairing ships with the native app.

Appearance

Follows your system by default. Roadside at 2am and a depot office in daylight are different rooms.

Your name

Shown to the mechanic coming to help you. Without it they are looking for a phone number on a hard shoulder.

Session

—

Emergency raised.

At zero, RoadAssist texts your saved emergency contacts and looks for the nearest responder unit.

5