Mobile App

Import contacts from the phone's address book in the mobile app
Let users select contacts from their phone's native address book and import them into the CRM from inside the mobile app. Today the only mobile option is the Business Card Scanner, which creates one contact at a time. Bulk import means a CSV upload from the web app. ❗ Problem Sales reps, agency owners and small business users often keep leads and customers in their phone contacts. That's especially common for people met in the field, at events, or through referrals. Moving them into the CRM now means exporting to CSV, reformatting, and uploading from a desktop. Many mobile-first users never do it. Scanning business cards one by one doesn't work for contacts they already have saved. As a result, contacts stay outside the CRM. They miss follow-up automations, pipelines and conversation history. ✅ Proposed solution Add an Import from Phone Contacts option in the mobile app's Contacts section, next to the Business Card Scanner. Ask for contacts permission using the standard iOS and Android prompt. Show a searchable list with multi-select and Select All. Map phone fields to CRM fields automatically: first name, last name, phone, email, company, and notes if available. Before importing, let the user: Add tags Assign a source Optionally add the contacts to a workflow or campaign Run duplicate detection on phone and email, with the same options as CSV import (skip or update). Show a summary when done: imported, skipped as duplicates, and failed. 🎯 Benefits Much faster onboarding for mobile-first users and field sales teams. Fewer leads lost between the phone and the CRM. Closes a gap in the mobile app's contact creation options. Helps agencies onboard small business clients who mostly work from their phones. 🔒 Considerations Request contacts permission only when the feature is used, and explain why. Only import the contacts the user selects. Never sync the whole address book in the background. Support the HighLevel, LeadConnector and white-labelled mobile apps. Make sure imported contacts respect existing consent and DND settings. ⭐ Priority and use case Priority: Medium–High
0
·
New Feature
Load More
→