Mobile App

Some Features: : 1- Enable sending SMS via the SIM card for two-way communication. 2- Allow making calls, recording calls , and utilizing every function available in the system on SIM card calls 3- When a lead calls me, the app should display details such as the last action, comments, or a custom fields. Many CRM companies have this feature, and implementing it will significantly enhance our mobile app, specially Twilio doesn't cover all countries.

Allow Lead Connector to toggle between 2 different HighLevel accounts (not subaccounts, but completely different accounts with different username and password). Allow user to receive SMS notifications on their mobile device through lead connector from all accounts that they are logged into on Lead Connector. MS Teams has this functionality and Lead Connector should too.

For anyone who goes out to physical appointments, it would be great if you could click on the address in the appointment and it bring it up in Google Maps

We need to have the ability to upload images / documents from the mobile app LeadConnector for our clients to upload customer photos when on job sites.

PRD: External Support Application for HighLevel Direct Chat Support ## 1. Purpose Enable GHL support agents and end-users to engage in real-time, on‑the‑go chat support via a dedicated external application (mobile and desktop), reducing reliance on SMS and improving response continuity. ## 2. Background * Keith Besherse’s advice: Leveraging lesser‑known hacks to streamline support workflows. * Mario Aldayuz's advice: Utilize a native iOS/Android/Windows/OSX application for GHL support that doesn't require browser based communications and can seamlessly handoff between devices. * Christopher Gaudreau’s suggestion: SMS-based support is costly for GHL and end-users in foreign markets; a standalone app would be more efficient and affordable. * Pain point: Users often abandon chats when forced to multitask or wait, leading to dropped conversations and unresolved issues. ## 3. Objectives * Provide a seamless, dedicated GHL support app for iOS, Android, and web. * Eliminate or dramatically reduce SMS costs by routing support through in‑app messaging. * Maintain chat state and notifications to prevent abandoned conversations. * Improve support agent productivity and end-user satisfaction. ## 4. Scope ### In Scope Mobile applications (iOS, Android). Progressive Web App (PWA) or desktop client. Integration with existing GHL Direct Chat API. Push and in-app notifications for new messages and reminders. Chat history synchronization across devices. ### Out of Scope * Billing and account management features. * Voice or video calling capabilities. * Support for third‑party chat platforms. ## 5. User Stories End-User: As a customer, I want to receive push notifications for new support messages so I never miss a reply. End-User: As a customer, I want to see my entire chat history when I switch devices so I can pick up where I left off. Support Agent: As an agent, I want to manage multiple chats in a unified interface so I can respond quickly and efficiently. Support Agent: As an agent, I want to view user metadata (location, plan level) within the chat to provide personalized support. ## 6. Functional Requirements Authentication & Authorization * Users and agents authenticate via GHL SSO. * Role-based access: agents vs. end-users. Real-Time Messaging * WebSocket or push-based delivery of messages. * Typing indicators and read receipts. Notifications * Push notifications on mobile. * In-app alerts and badge counters on web. Chat History & Persistence * Server-side storage of complete conversation history. * Local caching for offline access. Reminders & Follow-Ups * Automatic reminder if user or agent is inactive > X minutes. * Option for users to set a manual reminder to revisit chat. Settings & Preferences * Notification preferences (mute, do-not-disturb). * Language and time zone settings. ## 7. Non-Functional Requirements * Performance: Chat screen load < 2 seconds on 4G. * Reliability: 99.9% uptime for messaging services. * Security: End-to-end encryption of chat data in transit and at rest. * Scalability: Support up to 10,000 concurrent active chats. * Localization: Support for multiple languages and time zones. ## 8. Success Metrics * Adoption Rate: * 50% of active support users adopt the app within 3 months. * Chat Abandonment Rate: * Decrease from current baseline by 30% in 6 months. * Average Response Time: * Achieve < 2 minutes agent response time for 90th percentile. * Cost Savings: * Reduce SMS expenses by 80% within first year. * User Satisfaction: * 90%+ positive feedback in post‑chat surveys.

be great to be able to type one text from the mobile app and send it to all contacts

Currently, when signing into Kollab, you have to select a single community server to join, allowing you to only view the groups from that community. It would be amazing if the app was similar to Slack, where users could choose which communities they have access to and be authenticated for all of those communities at once, without having to log out and back in to switch between different communities, while also making sure notifications aren’t missed between them.

The one thing I Adore about both Skool and Circle, is that they have separate apps that folks can download to access their community. Gohighlevel does not, and so its accessed by the clunky mobile web browser. Were competeing with facebook groups as far as ease of use is concerned. Facebook has its own app, but its so robust that individual groups can fall off in the feed. But alot of folks dont use facebook, and a dedicated app would make things alot easier to build a community up and interact with. Ease of access is paramount.

Would be awesome to be able to add documents, pdfs , videos and photos to a client contact in the mobile app. So service clients that use us can have their techs in the field would be able to grab all pertinent information about a job they are on rather than searching through emails and other channels to get everything they need.