Skip to main content

​
Mobile app first-shift onboarding

This guide takes a brand-new user through a complete first shift on the Orbit mobile app, in order: install, sign-in, push, a first inbound and outbound call, a first Meet, a first Inbox conversation, and a clean sign-out. The Orbit mobile app page is the feature reference for what each tab shows; this page is the journey.

​
What a “mobile shift” means

A mobile shift is doing your normal Orbit work from a phone instead of a desk. The app carries the four working surfaces you already know from the web dashboard: the Softphone (the voice dialer and live call screen), Meet (the same video rooms you create on the dashboard), the Inbox (the same unified inbox of customer conversations, team channels, and direct messages), and Calls (your call history and voicemail). Nothing on the phone is a separate system: a call you answer on mobile lands in the same call log the wallboard shows, and a reply you send from the Inbox tab resolves the same conversation your desktop colleagues see. Each step below takes a minute or two, so a new hire can run their own first shift, and an admin rolling mobile out to a team can hand this page to each user.

​
Install and sign in

  1. Install the app from the App Store on iOS or Google Play on Android. If your workspace distributes the app through Apple Business Manager or a managed Play listing, use the link your admin shares.
  2. Open the app and sign in with the same work email you use for the web dashboard.
  3. If your organization enforces single sign-on, sign-in hands off to your identity provider; complete the IdP prompts and the app picks the session up. The admin side of that setup is Enroll SAML SSO: Okta and Microsoft Entra ID.
  4. If your account belongs to more than one workspace, pick the workspace this shift is for in the workspace picker.
  5. If your account has multi-factor verification enabled, finish sign-in in the browser window the app opens, then return to the app.
The app keeps you signed in between restarts, so this is a one-time setup per device.

​
Enable OS push

When the OS asks whether Orbit may send notifications, accept. That prompt is the whole push setup: the app registers the device’s push token with your workspace the moment sign-in completes, and re-registers whenever the OS rotates the token. With push allowed, missed calls, new voicemails, and Inbox messages reach the lock screen; with it denied, the app still works but only shows what happened after you open it. Accepting is safe because of the deep-link gate (the essentials here; the full rule in The Orbit mobile app): a link carried in a push only navigates if it matches one of Orbit’s own origins, the orbit:// scheme, https://orbit.devotel.io, or https://api.orbit.devotel.io, and the push declares the workspace you are currently signed into. A link from any other origin, or a push addressed to a different workspace, is rejected and the app stays on the current screen.

​
Take an inbound call

  1. Confirm you are signed in and reachable: on iOS the app registers for CallKit call push at sign-in, and on Android the same push token is registered for high-priority call notifications.
  2. From a cell phone or another line, call one of your workspace’s numbers that rings to you: your direct number, or a queue you are a member of.
  3. The app rings on the OS call screen, CallKit on iOS and a full-screen incoming call on Android. Answer it the way you answer a regular mobile call.
  4. Use the in-call controls to mute or hang up. When the call ends it appears in the Calls tab with direction, the caller’s number, and duration; a missed call is flagged if you did not pick up.
If the phone never rings: check that notifications are allowed for the app in OS settings, that you are signed in on this device, and that the number you dialed actually rings to you in the dashboard’s voice routing.

​
Make an outbound call

  1. Open the Softphone tab. The dial box takes E.164 numbers, so dial the full international form, for example +14155552671.
  2. Tap call. The call connects through your workspace’s voice setup exactly like a dashboard softphone call.
  3. The person you call sees the caller ID your workspace configured for agent calls: one of your organization’s numbers. To change which number presents on outbound calls, update the outbound caller ID in the dashboard (see Outbound caller IDs).
  4. When the call ends, the call shows in the Calls tab as outbound with its duration.

​
Join a video Meet

  1. Open the Meet tab. The tab lists the live and scheduled rooms for your workspace.
  2. Tap a room to join; the OS asks for camera and microphone access the first time. A Meet link that arrives in a push or an Inbox message opens the same way, after passing the deep-link gate.
  3. To invite someone without the app, share the room link; anyone you invite via link joins from a browser.
Creating rooms, scheduling, and room settings live in Persistent video rooms; the Meet tab joins and lists what already exists.

​
Work the Inbox

The Inbox tab shows the unified inbox from the dashboard: customer conversations, the team-chat channels you belong to, and direct messages, sorted by activity with unread-count badges. Tap a row to open the conversation; a reply you send is visible to everyone on that conversation, desktop and mobile alike. Use the Refresh button in the tab when you want a fresher view.

​
Sign out, retire the device token

When a shift ends for good, a device leaves the team, or a phone is lost, sign out of the app. Sign-out retires the device’s push registration, so calls, voicemails, and messages stop routing to that device immediately. If you build your own client against Orbit, or you need to retire a registration without the device in hand, delete the token with DELETE /api/v1/push/device-tokens/:id; the request and its idempotent behavior are documented in The Orbit mobile app. Reinstalling with the same install identity likewise retires the previous token instead of leaving a registration that pushes to nothing.