Mobile App

Feature Request: Import Phone Contacts Directly into the Mobile App
It would be incredibly helpful to have the ability to import contacts directly from a mobile device's contact list into the mobile app. Currently, if I meet someone at a networking event, conference, or in the field and save their information in my phone, there isn't an easy way to bring that contact into GoHighLevel without manually creating a new contact and retyping all of their information. Suggested Functionality Add an "Import from Phone Contacts" option when creating a new contact within the mobile app. This feature could: Request permission to access the device's contacts. Allow users to select one or multiple contacts to import. Automatically map fields such as: First Name Last Name Mobile Phone Email Address Company Job Title Address Notes (if applicable) Detect duplicate contacts and provide options to: Skip Update existing contact Create a new record Why This Matters Many users rely on the mobile app while traveling, networking, attending trade shows, or meeting clients in person. Being able to import contacts directly from the phone would: Save significant time by eliminating manual data entry. Reduce typing errors. Make it easier to capture leads immediately after meeting someone. Improve CRM adoption for mobile-first users. Encourage users to keep GoHighLevel as their primary CRM instead of storing contacts only on their phone. Bonus Features It would be even more powerful if users could: Import multiple contacts at once. Assign tags during import. Add imported contacts directly to a Smart List, Pipeline, or Workflow. Automatically create an opportunity during import. Choose which phone number to import if a contact has multiple numbers. This enhancement would make the mobile app much more efficient for sales professionals, insurance agents, real estate agents, contractors, and anyone who builds relationships while on the go.
0
·
New Feature
Tap to Pay is needed for Authorize.net & NMI
Enable Tap to Pay on iPhone and Android in the HighLevel mobile app for merchants using Authorize.net and NMI. No extra hardware. Card-present, contactless, fast. Who needs this: Field sales and service teams Retail, pop-up, events, and on-site visits Agencies that standardize on Authorize.net or NMI Current workaround: External reader hardware, higher friction and cost. Manual card entry in the app, slower and higher risk of declines. Proposal: Ship Tap to Pay support tied to existing Authorize.net and NMI connections. Let users accept contactless payments in the HighLevel mobile app with NFC on iPhone and Android. MVP requirements: Works with existing Authorize.net and NMI accounts iPhone and Android support Contactless credit and debit, Apple Pay, Google Pay Sale, tip, refund, void Digital receipts via SMS or email Save card to vault for future invoices and subscriptions Taxes, service charges, and location-based settings Basic reporting in Transactions and Opportunities Roles and permissions for staff devices Surcharging or cash discount rules by location Nice to have, Phase 2: Partial authorizations and split payments Offline queue with auto-capture when online QR pay fallback Admin and UX notes: Gateway mapping by location and user Simple flow: New charge, amount and tip, Tap to Pay, receipt, add to contact Clear error states and retry, with audit log Exportable payout and fee summaries Compliance and security: EMV contactless support PCI scope aligned with Tap to Pay requirements Tokenization and gateway vault Strong device attestation and per-device enablement Business impact: Faster checkout, higher close rate in the field Fewer hardware costs. Typical readers cost 60 to 200 per unit, plus replacements Cleaner reporting, since payments stay in the same gateway and CRM Urgency: Contactless is now the default for many buyers. This removes a key blocker for in-person sales without forcing a gateway change. Success metrics: Tap to Pay adoption rate by location Time to charge, tap-to-receipt under 30 seconds Increase in card-present volume and tips Reduction in reader hardware tickets and costs
3
·
New Feature
Load More