The desktop GoHighLevel interface is where systems get built. The mobile app is where they get used — by the technician between jobs, the agent between viewings, the owner who is never at a desk. If your client only ever sees GoHighLevel on a laptop, they are probably not using half of what you built for them.
This guide covers what the LeadConnector mobile app does well, what it does not, how to white-label it, and how to set it up so your team actually responds to leads instead of watching notifications pile up.
What the App Is Called
The standard app is LeadConnector, available on iOS and Android. Agencies on higher plans can publish their own branded version, so your clients download your app rather than one carrying a platform name they have never heard of. More on that below.
What It Does Well
Conversations
The unified inbox is the app’s strongest feature and the reason most people keep it installed. SMS, email, Facebook and Instagram messages, WhatsApp and webchat all land in one thread per contact. Replying from the app sends from the business number, not the user’s personal phone — which means the conversation history stays in the CRM when that employee leaves.
This alone solves a genuine problem. Staff texting customers from personal mobiles is how businesses lose their customer history, and it is remarkably common.
Calling and Call Recording
Outbound calls place through the business number with caller ID intact. Calls log against the contact automatically, and recordings attach to the timeline where enabled. For any business that needs a record of what was agreed on the phone, this is the difference between a CRM and a filing cabinet.
Calendar and Appointments
View the day, book appointments, reschedule, and mark outcomes. For field teams, being able to book the next visit while still standing in the customer’s kitchen is worth more than any automation you can build.
Pipeline and Opportunities
Drag opportunities between stages, update values, add notes. Not as comfortable as the desktop board, but adequate for updating a deal after a site visit — which is exactly when it should be updated, rather than three days later from memory.
Payments
Collect payment on site through the app, including text-to-pay links. For trades and mobile services, getting paid before leaving the driveway materially improves cash flow. Our invoices and text-to-pay guide covers the setup.
Push Notifications
New message, missed call, new form submission, appointment booked. These are what turn a slow business into a responsive one — provided they are configured, which most accounts never do properly.
What It Does Not Do
Be honest with clients about the limits, or they will find them at the worst moment:
- No workflow building. Automations are desktop-only. You can see that a workflow ran; you cannot edit it.
- No funnel or website editing.
- Limited settings access. Custom values, field schemas and integrations are desktop territory.
- Reporting is basic. Enough for a glance, not enough for a client review. Use an emailed dashboard instead — see our client reporting guide.
- Bulk actions are constrained. Mass tagging and imports belong on desktop.
The app is for operating the system, not building it. Positioned that way, nobody is disappointed.
White-Labelling the App
On eligible plans you can publish a branded mobile app to the App Store and Google Play under your agency’s name, with your logo, colours and splash screen.
Why it matters commercially:
- Retention. A client with your app on their home screen, used daily by their staff, is significantly harder to churn than one who logs into a web page occasionally.
- Perceived value. “Our software” justifies a different price point than “a tool we set up for you”.
- Consistency. The branded app matches the white-label desktop experience rather than breaking it.
The process runs through GoHighLevel’s white-label app submission: you supply branding assets and developer account details, and they handle store submission. Expect the review process to take real calendar time — plan for weeks, not days, and do not promise a client a launch date until it is approved. If you are building an agency around this, our white-label GoHighLevel guide covers the wider positioning.
Setting It Up So People Actually Use It
Installing the app is not adoption. Four things decide whether it gets used:
1. Configure notifications deliberately
Default notification settings are either too noisy or too quiet. Too noisy and people disable them entirely; too quiet and leads sit unanswered. Walk each user through enabling notifications for new messages and missed calls, and disabling the ones that do not require action.
2. Assign contacts to owners
An unassigned contact notifies nobody in particular, which in practice means nobody. Set contact ownership in your workflows so every inbound lead has a named person whose phone lights up.
3. Set permissions correctly
A technician does not need access to every contact and every pipeline. Scope users to what they need — it reduces noise as much as it improves security. Our guide to user roles and permissions covers how to structure this.
4. Train on one workflow, not the whole app
The fastest adoption comes from teaching a single habit: “when the phone buzzes with a new message, reply from the app.” Everything else follows once the app is open daily. Trying to teach the full feature set in one session guarantees none of it sticks.
Speed to Lead: Where the App Pays for Itself
Response time is the single strongest predictor of whether an inbound lead converts. The gap between replying in five minutes and replying in an hour is enormous, and it is almost entirely a mobile problem — because leads rarely arrive while someone is sitting at a desk.
A working setup looks like this:
- Lead submits a form or calls.
- A workflow assigns the contact to the right user immediately.
- The assigned user gets a push notification on their phone.
- An automated first response goes out within seconds so the lead is not sitting in silence — the same principle as missed call text back.
- The human replies from the app, in the same thread, from the business number.
The automation buys you time; the app is what lets a person use it.
Troubleshooting
- Notifications not arriving: check OS-level notification permission, in-app notification settings, and that the user is actually assigned to the contact. All three must be right.
- Cannot send SMS: usually a phone number or A2P registration problem rather than an app problem. Check A2P 10DLC status first.
- Calls not connecting: confirm microphone permission and that the user has a number assigned.
- Wrong sub-account showing: users with access to multiple locations must switch explicitly — a common source of confusion for agency staff.
- Missing contacts: almost always a permission scope, not a sync failure.
A Rollout Plan That Gets Adoption
Handing over a login and hoping is how most mobile rollouts fail. This sequence works considerably better.
- Install it during the training call, on their actual phone, with you on the line. Do not send instructions.
- Turn on notifications while you are still talking. This is the step that silently does not happen otherwise, and without it nothing else matters.
- Send a real test message to their phone and have them reply from the app. One successful round trip builds more confidence than any explanation.
- Teach exactly one habit: when it buzzes with a new lead, open the app and reply. Nothing else in week one.
- Check in on day three. Look at whether they have actually replied to anything. If not, find out why now rather than at the monthly review.
- Add the second habit in week two — usually booking an appointment or sending a payment link.
Measuring Whether It Is Being Used
Adoption is measurable, and it is a leading indicator of whether the whole system will stick.
- Median response time to inbound messages, per user. The number that matters most.
- Percentage of conversations with a reply within the hour.
- Messages sent from mobile versus desktop. A field team sending everything from desktop is not using the app.
- Days since last app activity, per user. Anyone past a fortnight needs a conversation, not another reminder email.
Where adoption is poor, the cause is almost always notifications being off, contacts not being assigned, or nobody having shown the person how it works. All three are fixable in a ten-minute call, and all three are invisible unless you look.
Frequently Asked Questions
Is the mobile app included in every plan?
The standard LeadConnector app is available on all plans. The branded white-label app requires a higher tier — see our pricing breakdown.
Can staff use it without seeing everything?
Yes. Permissions are set per user on the desktop and apply in the app, so you can restrict a user to their own contacts, specific pipelines or particular calendars.
Does it work offline?
Not meaningfully. It needs a connection to send and receive. Field teams in poor-signal areas should expect messages to queue until they reconnect.
Can clients use the app instead of the desktop entirely?
Many owners do, for day-to-day operation. Someone still needs desktop access for building and reporting — usually you, as the agency.
How long does white-label app approval take?
Long enough that you should not commit to a client launch date in advance. App store review is outside anyone’s control and varies considerably.
The Practical Takeaway
The mobile app is the difference between a system your client owns and a system they were sold. Set up assignment and notifications properly, train one habit, and the automation you built starts producing the results you promised.
GHL Nexa configures mobile access, permissions and notification routing as part of every build, and handles white-label app setup for agencies. Get in touch if your team has the app installed but nobody is answering.
