Video summary
XLEADS UPDATE - IMPORT LEADS DIRECTLY FROM LEADS TAB!
Main summary
Key takeaways
Product reviewed
XLeads (CRM on GoHighLevel) — the newly updated lead flow feature that imports/exports leads directly between the Leads tab and the Contacts tab.
Key features (what’s new / what it does)
- One-click “Export to Contacts” from the Leads tab to the Contacts tab.
- Removes the usual export/mapping/tagging pain from the old workflow:
- No manual property mapping
- No need to dig into how mapping works
- Supports workflows where users can:
- Build a filtered lead list (e.g., “Columbus, Ohio / vacant properties”)
- Import a data file to create a list
- Create lists and add results to an existing list
- Requires setup of an “X Leads connector app” (a GoHighLevel app) to connect the CRM and enable the export bridge.
- After export, imported contacts can be tagged automatically with chosen tags (e.g., SMS blaster / power dialer / custom tags like “April 2026 marketing”).
User experience / workflow described
- Go to XLeads → Leads tab and create/import/filter a list.
- Click Export to Contacts (referenced in the video as “export to Ninja CRM / export to the contact section”).
- Connect accounts (log in, get support code, install the X Leads connector app, connect to the sub-account).
- Assign tags (examples: “SMS blaster”, marketing tag, etc.).
- Export, then check Contacts—properties and fields appear there (including phone numbers and a “contact source: leads pipes export…” indicator).
Pros mentioned
- Much faster and simpler than the previous process.
- No manual mapping and fewer steps—the import/export feels “done for you.”
- Integrates cleanly with GoHighLevel automations:
- Power dialer tag for calling automations
- SMS blaster tag for texting/blasting automations
- Exported contacts display relevant data:
- Phone numbers (primary + additional)
- Property information
- Source indicator
Cons / caveats mentioned (important)
Imported leads into Contacts are set to “Do Not Disturb (DND)”.
- Because of DND, automatic calling/texting won’t work immediately until DND is removed.
- The reason given: the system can’t determine opt-in status, so the user must decide whether outreach is compliant.
- Workaround:
- Create or use a workflow/automation to remove/disable DND (example: an automation triggered on contact created that removes DND).
- Test the automation, then apply as needed.
Comparison to previous workflow
- Before: export → lead trace/download → import into Contacts → manual mapping + tagging work
- Now: direct connection + one-click export from Leads to Contacts with mapping handled by the system
Numerical details mentioned
- Example list created with:
- 47 properties, then filtered down to 14 properties before export
Unique points mentioned (consolidated)
- Direct Leads → Contacts export via a new one-click feature
- Eliminates manual property mapping
- Adds an export-to-contacts section
- Uses an installed X Leads connector app inside GoHighLevel to connect
- Tagging on export:
- Power dialer tag
- SMS blaster tag
- custom tags (e.g., marketing tag)
- Contacts created from imports include:
- phone numbers (including additional)
- property details
- contact source indicator
- Main caveat:
- imported contacts start with DND enabled
- Requires user-side compliance handling:
- automation to disable DND for all appropriate channels
- Example automation logic:
- trigger: contact created
- action: enable/disable DND (disable outbound/all channels)
- After removing DND, tags and automations can be used to call/text
Speakers / roles
- Zach Gin (single speaker): explains the feature, provides examples, and demonstrates the DND workaround automation.
Overall verdict / recommendation
Recommended if you use XLeads and regularly move leads into Contacts—this update significantly reduces manual export/mapping work.
Be aware of the DND default on imported contacts: you’ll likely need to set up (or reuse) an automation to remove DND before calling/texting.
Rate this summary
Your feedback will help improve summaries.
Improve this summary
Reprocess with a stronger model when the summary feels incomplete or inaccurate.
Translate summary in another language
Ask questions to this video
Chat for follow-up questions, clarifications, and source-backed answers.