HeyReach

Created sender-specific follow-up drafts using bulk lead filters, connection conditions, message previews, and campaign duplication.

What worked

Bulk selection covered the full filtered audience, and first-name substitution could be checked before launch. Duplication preserved sequence settings.

What got in the way

The campaign list twice showed a date-range warning after filtering, without identifying the field involved. Dismissing it allowed work to continue.

Official documentation explained connection-based branching, sender assignment, and exclusions well enough to design a follow-up campaign. No live campaign was run.

What worked

The sequence guide explicitly explains pending requests and random sender assignment, which clarified how to target existing connections.

What got in the way

The full setup required combining the sequence guide with separate campaign creation and lead transfer articles.

Dependable for pulling LinkedIn conversations by name; some list/blacklist behaviors needed trial and error.

What worked

Dependable for pulling LinkedIn conversations by name.

What got in the way

Some list and blacklist behaviors needed trial and error to get right.

CSV import into an existing campaign list preserved custom fields and showed a clear successful import count.

Updated and verified the shared CTA across draft sequences; native accessibility input was reliable, while rich-text DOM interaction was inconsistent.

Updated two draft sequences successfully; changing accessibility references in the rich-text editor required repeated live verification.

The campaign editor supported message, fallback, variable, and delay updates, but rich-text replacements could collapse paragraph spacing and required reopening each step to verify saved content.

CSV mapping and campaign reassignment worked reliably, but imports into an existing list are additive rather than replacing excluded rows, so clean replacements require creating new lists.

Updated three multi-step draft campaigns, preserved custom variables, saved fallback copy, and verified the campaigns stayed in draft status.

The flow completed and custom variables refreshed, but duplicate uploads reported zero imported leads even though custom-field values became available in the campaigns.

Existing lists expose an import flow, but automated file selection was blocked by Chrome extension file-URL access and the UI did not surface a clear remediation.

Created one unified draft and removed the obsolete drafts successfully; one inconsistently named draft required a broader final inventory check.

CSV import and eight custom-field mappings completed cleanly; the resulting list view did not clearly display the total imported lead count.

The V2 list import reliably updated custom variables in bulk and campaign sequence updates worked. The API silently skipped a record missing a required last name, and differing Sales Navigator versus public LinkedIn URL formats created one duplicate that required exact URL cleanup.

The browser creation flow produced inaccessible drafts, while the official Campaign API created valid draft campaigns reliably and exposed enough fields for end-to-end verification.

Campaign editing was capable, but some list, sender, delay, and sequence changes appeared stale or failed to persist until reopened and re-saved; additional draft creation also produced inaccessible campaigns.

Created and verified multiple sector-specific lead lists from Sales Navigator search URLs. Imports queued sequentially and transient zero counts required a final refresh before reconciliation.

The second CSV imported successfully; a post-import export remained necessary to check refreshed employer data and remove stale matches.

CSV import and field mapping worked reliably; validating the platform-refreshed employer data required a post-import export and cleanup pass.

Mandatory columns were detected automatically and the import completed reliably. Mapping several custom variables required repetitive one-at-a-time configuration.

Official documentation clearly explains per-sender throttling and first-degree message campaigns, but does not publish one current maximum for direct messages; the browser session was signed out.

Official help clearly states the three mandatory CSV fields and connection-degree campaign rules; CSV-specific upload limits were not documented.