Does Amazon Connect have a mobile app?
It's one of the most-searched questions about the platform — asked just as often as "is there an AWS Connect mobile app?" — and the answer has two halves: one about what AWS ships, and one about what you can actually put on an agent's phone. Here's both, plus what to look for so you don't end up with a workaround wearing an app icon.
The short answer
AWS does not publish an Amazon Connect agent app for iPhone or Android. The agent experience is the Contact Control Panel — the CCP — and it is a browser application. Sign in, keep the tab open, take contacts. Agents on the move are, as far as the platform is concerned, agents at a desk who happen to have moved.
That is a deliberate design choice, not an oversight, and it is fine right up until the moment a meaningful share of your people aren't at a desk: the team lead walking the floor, the duty manager on an after-hours roster, the field technician between sites, the two-person business where everyone does everything.
The longer answer is that a real Amazon Connect softphone does exist on the App Store — it just isn't published by AWS. Connect Phone by LiveUCX is a full agent softphone for iPhone that connects to your own Amazon Connect instance, and it's free to download.
"AWS Connect mobile app" and "Amazon Connect mobile app" are the same search
Worth clearing up early, because it changes what you'll find. The product's actual name is Amazon Connect; AWS Connect is the shorthand a lot of people use, and AWS's own documentation only ever uses the long form. Both point at the same cloud contact centre, so an AWS Connect mobile app and an Amazon Connect mobile app are the same thing.
The practical consequence is that searching one phrase and not the other will hide half the market from you. It also means you should be a little sceptical of vendors who lean on the "AWS" phrasing in ads — it's a cheap way to look like a first-party AWS product when nobody is. There is no AWS-published agent app under either name.
Why forwarding calls to a mobile isn't the same thing
Before buying anything, most contact centres try the free option: route the queue, or overflow from it, to an agent's mobile number over the PSTN. The phone rings, the agent answers, the customer is helped. It looks like it works.
What it actually does is hand the call out of Amazon Connect, and with it most of what you run Amazon Connect for. Routing intelligence stops applying, the agent leg isn't recorded in your instance, handle time and adherence go unmeasured, and the contact record fragments — no attributes, no wrap-up written back, often no meaningful Contact Trace Record. The interaction happened; your system of record barely knows it did.
We've pulled that apart properly in Amazon Connect mobile agents: what breaks, which is the piece to read if you need to justify the spend internally. This article is about what to buy instead.
What a real mobile softphone has to do
"Mobile app" covers a wide range of things, some of which are dashboards with a dial pad bolted on. Six criteria separate a genuine AWS Connect mobile app from a companion app that only looks the part.
- Carry the audio itself. The call has to run over a secure connection to your Amazon Connect instance — not as a call-back to the agent's mobile number. If the audio path is the PSTN, everything in the previous section applies no matter how good the app looks.
- Give full call control. Answer, hold, mute, keypad for IVRs, quick connects, reject, and — the one people forget until the first week — transfer. An agent who can't move a call on is an agent who takes messages.
- Handle more than voice. Contact centres route chats and tasks too. An app that only does voice creates a second rota.
- Write back. A disposition and notes captured on the phone must land on the Amazon Connect contact, or your quality and reporting data has a mobile-shaped hole in it.
- Authenticate like the rest of your estate. SAML single sign-on or native Connect login, with no Connect credentials stored on the device. Personal phones make this non-negotiable.
- Be honest about ringing. See below — this is the criterion vendors are least straight about.
The ringing question, answered plainly
Ask any mobile softphone vendor exactly when the app rings, and don't accept "it rings" as the answer.
Connect Phone rings while the app is open, using Amazon Connect's own softphone ringtone, and answers in a tap. It does not ring on the lock screen with the app closed. Ringing a force-closed app requires Apple's CallKit driven by a VoIP push, and on a browser-based softphone that mechanism can disrupt the call audio itself. It's on the roadmap and it isn't shipping until it's solid. We'd rather write that here than let you discover it in week two.
In practice this means agents keep the app open while rostered on a queue — the same discipline as keeping the CCP tab open at a desk. For rostered work that is a non-issue. If your requirement is genuinely "somebody's phone must ring at 3am from a cold start", say so during evaluation, because that is a different product and several vendors will imply they have it when they don't.
Which metrics you keep
This is the practical test of whether a mobile app has actually kept the call inside Amazon Connect: does the mobile agent look identical to a desk agent in your reporting?
With a genuine softphone, they do. The contact is routed by the same queues and skills, recorded in your instance under your retention rules, and measured the same way — handled count, average handle time, talk, after-call work, hold, occupancy, adherence. Contact Lens analyses the conversation like any other. Supervisors see mobile agents in the real-time metrics page alongside everyone else, and your wallboards don't need a footnote.
Connect Phone also surfaces those numbers to the agent: live handled count, AHT, talk, ACW, hold and occupancy on the phone, plus queue stats and a transfer directory showing which queues and agents are actually available. Roaming agents lose the ambient awareness of a contact-centre floor, and giving them the numbers directly is what closes that gap.
If you want the same picture on a screen the whole floor can see, that's what LiveUCX wallboards are for.
How to roll it out to a team
- Pick the cohort that actually needs it. Not everyone. Start with on-call, field and floor-walking staff — the people for whom the alternative today is a forwarded call or nothing.
- Decide the roster rule first. Agree what "rostered on the queue" means for a mobile agent, including when the app is expected to be open, before anyone installs anything. This is a people decision that gets blamed on software.
- Wire up sign-in. Configure the workspace and share the one-time workspace code. Agents install from the App Store, enter the code once, then sign in with their Connect login or SAML SSO.
- Test on the real network. Mobile data in a car park is not office Wi-Fi. Run a week of real calls across the conditions your agents actually work in.
- Check the reporting before you scale. Pull a real-time and a historical report and confirm mobile-handled contacts appear exactly like desk-handled ones. If they don't, you have a forwarding arrangement, not a softphone.
What it costs
Connect Phone is free to download on the App Store; licensing is per agent per month through the ProUCX portal, not through Apple. Basic is US$10 per agent per month for the full softphone with voice, chat and tasks, transfer, conference, caller history, contact attributes and SSO. Medium is US$15 and adds live queue stats and agent performance, disposition write-back, recording pause and resume, and Amazon Q assist beside the call. Advanced is priced on application for CCP customisation, your own branding and deploy-in-your-account. It's built for teams of five or more, and it's also available on AWS Marketplace if you'd rather it hit your existing AWS bill.
Against that, weigh what a forwarded call costs you in unrecorded conversations and unmeasured handle time. For most contact centres with a compliance obligation, the recording gap alone settles it.
The short version
Amazon Connect has no first-party mobile app under either name, and the browser CCP doesn't travel. A real third-party softphone does exist, and the test of a good AWS Connect mobile app is boringly simple: the call stays a routed Amazon Connect contact, and the agent on a phone appears in your reporting exactly like the agent at a desk. Anything that fails that test is call forwarding with an icon.
If you need the numbers to take to a budget conversation — which routing, recording and reporting you actually lose on a forwarded call — that's the companion piece: Amazon Connect on a phone: mobile agents without losing the contact.
Put your Amazon Connect agents on the phone in their pocket
A full agent softphone for iPhone, connected to your own Amazon Connect instance.
Forwarding a queued call to a mobile number quietly drops routing, recording, metrics and the contact record. Why a real softphone on the agent's iPhone keeps every call inside Amazon Connect.
The native metrics page is a supervisor tool, not a floor tool. What it can't do — thresholds, alerting, floor maps, more than one platform — and how to get a wallboard live.
Link, embed, CTI or full workspace — four products at four prices. What screen-pop really requires, how logging differs per CRM, and the eight questions to ask before signing.