More consistent search and profile imports · Choose lead columns and use accurate first names
More consistent search and profile imports
What changed
LinkedIn people-search imports, Sales Navigator searches, conversation loading and profile capture became less dependent on the layout of LinkedIn pages.
How to use it
No setup is needed. Use the regular lead scan and inbox workflows; account access to LinkedIn and Sales Navigator still applies.
Choose lead columns and use accurate first names
What changed
The lead table gained column visibility, reordering, saved layout, and reset controls. Structured first and last names improved lead display and connection-note/reply personalization.
How to use it
In Leads, open Columns to choose visible fields; enable reordering to drag headers. Use Reset columns to restore the default layout.
Restore lead fit controls and connection data
What changed
Lead qualification controls and connection-degree data were restored and normalized, making fit decisions and connection filtering available again in the lead table.
How to use it
In Leads, review a person’s connection information and use the fit controls to mark them Fit, Not fit, or Unreviewed.
Restore reliable LinkedIn message synchronization
What changed
Inbox synchronization was repaired across opened-thread identification, message parsing, event depth, and LinkedIn API retrieval, helping conversations and their messages arrive with the correct identity and context.
How to use it
Open Inbox and review the synchronized conversations. The synchronization fixes apply automatically.
Build AI context from a valid self-profile
What changed
Self-profile capture and AI-default generation were hardened to preserve useful profile context and reject invalid captures instead of building settings from the wrong or incomplete page.
How to use it
No setup is needed for capture validation. Review generated context before using it in outreach.
Stop bulk invitations at LinkedIn’s weekly limit
What changed
Bulk invitation runs stopped when LinkedIn reported its weekly invitation limit, avoiding repeated attempts against the same limit and showing the stopped state in the run summary.
How to use it
No setup is needed. Review the bulk invitation run summary when a weekly limit stops a run.
Understand what happened in a bulk invite run
What changed
Bulk invitation progress distinguished sent, skipped, and failed outcomes instead of relying on a single aggregate count. Completed summaries stayed visible, and clearer run-status handling explained partial results.
How to use it
Open the bulk invitation run summary to review its outcome breakdown after the run finishes.