ConnectWiz Mobile

Not a notification companion. The actual desk, in a pocket.

The agent app carries the full inbox — and then keeps going: calls that ring natively like real phone calls, the social comment queue, and email. Live on the App Store and Google Play, updated over the air.

Live on both stores Calls ring like calls OTA updates, both platforms
Agent app — a call rings in
Sofia L. · WhatsApp call
Answered on lock screen
History opens with the call
Orders · chats · notes, one screen
Transfer → Billing
Live captions on
4 queues: chats · calls · comments · mail
2
Stores it’s live on — the App Store and Google Play, one codebase, tablets included
4
Queues in one app — chats, calls, social comments and mail
1
Publish to update both platforms over the air — no store queue for interface fixes
60s
Native ring auto-cancel — a missed call can never leave a phone ringing forever

The inbox

Everything the web panel does with conversations — from a phone

Full conversation parity

Folders, filters, typed message threads, attachments, delivery ticks, templates, saved replies, internal notes, transfer and assignment — the desk, not a viewer of the desk.

Comments & mail queues

The social comment desk and the email client are tabs of their own — the two-star review and the invoice question both get answered from the train.

Push that arrives

Notifications ride a dedicated push provider, verified end-to-end on physical devices — because "we sent a notification" and "the agent’s phone buzzed" are different claims.

Native calls

A WhatsApp call that rings like a phone call — because it is one

Most "mobile support apps" show calls as a notification you race to tap. Ours registers with the operating system’s own call machinery, so customer calls ring the lock screen like any phone call.

Abstract 3D illustration: a glass smartphone with a glowing inbox list and a pulsing incoming-call ring, a headset orb and comment bubble orbiting

OS-native ringing

iOS CallKit and Android’s Telecom framework with full-screen ringing — locked phone, pocket, whatever: the call rings like a call, and answering opens the customer’s conversation.

Server-backed call control

Hold, resume and transfer live on the server, not in the handset — so a transfer survives the phone’s network hiccup, and the panel and mobile see the same call state.

Captions & the dialer

Live captions during calls, audio-route switching, a dialer for outbound — and a bridge-health banner that says so when media quality degrades, instead of letting agents blame themselves.

Ring hardening

A 60-second native auto-cancel (no eternal ringing), cancellation observers, and answered-elsewhere detection — the edge cases of real phones, engineered rather than hoped away.

How it ships

Engineering you can feel in week three

Over-the-air updates

Interface and logic fixes reach both platforms in one publish, without a store review in the path. Native changes go through the stores as they must — the split is principled, not lazy.

A version gate

The server knows the minimum and latest versions; stale installs get nudged to the store before drift becomes support tickets.

Keychain-grade auth

Device tokens live in the OS keychain/keystore, tenant context is derived server-side — a lost phone is a revoked token, not a leaked workspace.

The honest fine print

Two things to know before you rely on it

Online-first, honestly

There’s no offline send queue yet — a reply typed in a dead spot asks you to retry rather than pretending it sent. We’d rather a visible retry than an invisible loss; the offline outbox is on the roadmap, unpromised until it ships.

Agent app, not customer app

This is the tool your team carries — your customers never need it. They stay on WhatsApp, Instagram, your website and the rest; the app is where your people answer.

Better together

The same platform, pocket-sized

The call center rings natively

Inbound calls from the voice platform ring the phone like a phone call — lock screen, car Bluetooth, watch — because the apps sit on each OS’s native calling stack.

Full inbox, not a viewer

Assign, tag, note, translate, answer with AI drafts — the mobile inbox is the same machinery as the desktop one, not a read-only companion.

Same roles, same walls

Permissions follow the person, not the device — an agent’s scope on mobile is exactly their scope on desktop, enforced by the same server-side policy.

Notifications that route

Push follows the same assignment and department logic as the inbox — the person who gets pinged is the person whose queue it is.

The field playbook

Built for the parts of work that happen standing up

The between-meetings reply

Most "slow" support is a fast answer waiting for someone to reach a desk. A routed push plus a full composer turns dead minutes into closed conversations.

Calls without a desk phone

Field teams take queue calls on the same number customers always dial — the office phone system stops being a place.

Small teams, honest coverage

For a two-person team, mobile is the difference between "business hours" meaning something and the AI carrying everything alone at 16:00 on a Tuesday.

Mobile FAQ

Before you install

More in the full FAQ, or ask us directly.

No — it’s the actual desk. The full conversation list with folders and filters, typed message threads, attachments, templates, internal notes, transfers, assignment and read receipts — plus three more queues: calls, social comments and email. What the web panel does for conversations, the app does from a phone.

Like real phone calls. A WhatsApp or phone-line call rings the device natively — lock-screen ringing via the platform’s own call system on iOS and Android — and answering opens the conversation with the customer’s history. Hold and transfer are server-backed, captions are live, and a mic-lock prevents cross-talk between calls.

It’s ConnectWiz on both the App Store and Google Play. Agents sign in with their existing account; device credentials live in the OS keychain, and a server-driven version gate nudges outdated installs to update before they drift.

Interface and logic fixes ship over-the-air to both platforms in one publish — no store review queue in the path. Native-layer changes still go through the stores, as they must, and crash reporting with full symbol maps means regressions are seen and fixed fast.

The queue doesn’t know you left the office.

Create your workspace, install the app from your store, and the desk follows your team.