Product

Mobile app

Two apps, because these are two jobs: the agent workspace works the queue, the customer portal follows requests. The same data as the web, the same API, and a session you revoke device by device.

The agent workspace, not a cut-down version

Saved views, the full thread, replies, internal notes, status changes and assignment. What is missing is missing on purpose: workspace configuration stays on the web, because nobody tunes an SLA on a six-inch screen.

The customer portal in their pocket

Your customers open a request, follow the answer and attach a photo. Magic-link sign-in: no password to remember for a service you open three times a year.

One session per device, revocable

Each phone gets its own token, listed and revocable from the workspace. A lost device is cut off on its own, without changing anyone's password — something a shared API key cannot do.

The agent workspace and the customer portal, side by side. Two apps, two jobs.

iOS 16 and Android 8 minimum. Both apps are free and included with your workspace.

Feature details

Told what concerns you

Assignment, new reply, SLA approaching or breached. The tap opens the ticket itself, not the home screen: a notification that makes you search has not told you anything.

Search, for real

Full-text search across tickets and contacts, with cursor pagination. It is an endpoint of the public API, so whatever the app can search, your integration can too.

Attachments in the thread

A photo taken on site goes into the conversation, at its date, in the same place as everything else. No orphan file in a separate store.

Agent sign-in through SSO

Your organisation's SSO, OIDC with PKCE, plus Face ID or fingerprint to reopen. No API key embedded in a binary shipped through two stores.

Counters without loading everything

Badges per saved view arrive with the list of views, in one call. An app that paginated to count would drain the battery to display a number.

The same API as yours

The apps get no privileged access: they consume the public REST API, documented, with its errors and its 429. If plugging in is painful for them, it is painful for you — and that is the only way to know.

The call that opens a session on a device, and registers it for notifications

POST /api/v1/auth/login
{ "email": "lea@acme.fr", "password": "…", "device": {
    "name": "iPhone de Lea", "platform": "ios" } }

-> 201 { "token": "ohd_dev_…", "device_id": "dv_9f2c",
         "agent": { "id": "usr_18", "name": "Lea Marchand" } }

POST /api/v1/devices
{ "device_id": "dv_9f2c", "push_token": "APNs:…", "platform": "ios" }

-> 204   # assignation, reponse, SLA proche ou depasse
         # DELETE /api/v1/devices/dv_9f2c coupe ce telephone seul