BackOffice ChatClosed beta

Three apps' worth of talking,
one icon.

Your colleagues. Your customers. Your phone line. Most teams carry a messenger, a shared-inbox app and a personal SIM to cover those three — and lose the thread between them daily. This is all of it, on the workspace that already holds the order.

Join the closed beta onGoogle PlayComing soon onApp Store

Free download · signs in to your existing workspace · beta places are limited

9:41▮▮▮ ▮

Inbox

🟢 live · 4 open · 2 assigned to you

MK
Mariam K.2m
Is order #4471 shipping today?
WhatsApp
Is order #4471 shipping today?
It's with the courier now — arriving tomorrow before 14:00. 🚚
Perfect, thank you!
ON THIS CUSTOMERCRM
Order #4471₾ 348.00 · paid
👥Team📥Inbox📞Calls
3 → 1
Messenger, inbox app and softphone become one
6+
Channels land in the same queue
Live
Messages stream in, no pull-to-refresh
0
Personal numbers handed to customers
See it work

One thread, start to finish

A WhatsApp question, a quick word with the warehouse, and a call back — without leaving the app or losing who you were talking to.

The three tabs

Because those are the three kinds of conversation

Deliberately separated. Nothing is worse than replying to a customer in the channel you meant for your colleague.

👥

Team

Direct messages and one room per team you belong to. Membership follows the team, so there's no channel list for anyone to administer or get left out of. Mentions raise a real notification.

📥

Inbox

WhatsApp, Instagram, Messenger, Telegram, email, web chat and SMS in one shared queue. Assign a conversation, change its status, drop a saved reply, or have AI draft one you edit before it goes.

📞

Calls

A real softphone on your Twilio number. It registers for the whole session, not just while the tab is open, so an inbound call reaches you wherever you are in the app.

Why it's different

The message already knows which order it's about.

A standalone inbox app gives you a message and a phone number. Your agent then goes looking: which customer is this, what did they buy, did we already refund them? That lookup is most of the handling time, and it's why replies take hours.

Here the conversation lives on the same workspace as the record. Open a thread and the customer's orders, tickets and history are right there — because it's one database, not an integration that syncs every fifteen minutes.

The same is true in reverse: a colleague can ask about the shipment in the Team tab while you're still typing to the customer in the Inbox tab, and neither conversation contaminates the other.

9:41▮▮▮ ▮

Team

Warehouse · 6 members

Luka
#4471 is on the 11:20 van
@Luka can you confirm before 14:00 tomorrow?
Luka
Confirmed 👍
Thanks — telling her now
📞 Incoming+995 577 12 34 56
Mariam Kapanadzeknown contact
👥Team📥Inbox📞Calls
Built for a phone, not shrunk onto one

The parts you only notice when they're missing

A live connection that survives a tunnel

One stream feeds every tab. Lose signal in a lift and it reconnects; let the token expire overnight and it refreshes and reopens rather than sitting there looking connected while nothing arrives.

🔔

Push that opens the right thread

Mentions, assignments and system alerts arrive as real notifications, and tapping one lands you in the conversation it came from — not on a home screen.

🤖

Saved replies and AI drafts

Your canned answers are one tap away, and AI can draft a reply from the thread and the customer's record. You read it before it sends — every time.

📱

Optional call-log sync, matched only

If you turn it on, a call to or from a contact your workspace knows is logged against them. Calls to anyone else — your family, your dentist — are never uploaded. That's the contract, not a setting.

🔐

Biometric unlock

Sign in once with password and 2FA, Google or Microsoft, then Face ID or a fingerprint after that. Lock it again the moment the app goes to the background.

🛡️

Never a direct line to the API

The app reaches your workspace through the same front door the web app uses. Same session rules, same permissions, nothing exposed for the sake of mobile.

Availability

Where it stands today

The honest status. The app is built and running against production — what's gated is the per-workspace credential setup, and we'd rather do that with you than leave you staring at a blank Calls tab.

PlatformStatusHow to get it
Androidio.backoffice.chatClosed betaRequest a place →
iOSiPhone & iPadComing soonGet the TestFlight invite →
Browseravailable nowLiveTeam chat, inbox and the softphone all run at app.bo.ge
Questions

Before you sign up

Why closed beta rather than a public release?

Because three of the four surfaces need credentials that are yours, not ours — push, your Twilio number, your message channels. Onboarding a workspace at a time means you get a working Calls tab instead of an empty one, and we get the bug report from a real shift.

What do I need to have already?

A BackOffice workspace, and — for the tabs you want — the Omnichannel Inbox app with at least one channel connected, and a Twilio number for voice. Team chat works with nothing extra.

Does it replace the web app?

No, it's the same conversations from a phone. One workspace, one history; the mobile app is a second window, not a second service.

Will an inbound call ring if the app is closed?

Not today. The softphone stays registered while the app is running, including in the background on most devices, but waking a fully killed app for a call is native work still ahead of us. We'd rather say so than have you find out on a customer.

Can it see my personal messages or calls?

No. Team chat is colleagues only; the inbox carries the channels your workspace connected. Call-log sync is opt-in and matched-only — a call is logged if the other party is already a contact in your workspace, and ignored otherwise.

What will it cost?

The download is free and there's no separate mobile seat — it's your normal plan. See pricing.

Join the closed beta.

Tell us your workspace, your devices and which of the three tabs you'd use first. We add workspaces to the Play track in batches and set up your channels with you.

You getThe Play internal-track build, plus the TestFlight invite the moment iOS opens.
We askThat you tell us when something breaks on a real shift. That's the whole deal.
You keepEverything. It's your workspace's data — leaving the beta changes nothing about it.