Changelog

A lead who just started a new role, or whose company just raised money or started hiring, is worth a message this week. Embers now keeps checking the people and companies behind the leads it already found, and tells you when something changes. A change never creates a lead; it gives you a reason to write to one you have.

What you get

• Eight kinds of change. New role, Title change, New leader, Hiring, Team hiring, Headcount growth, Funding, and Acquisition. Each is one sentence, such as “Started as VP Sales at Acme in Oct 2026.”, with its source and the day Embers checked it.
• It leads the Why. A change from the last 30 days opens the lead’s Why on the leads list, the lead sheet, and the full lead page. In the Priority Queue it shows under Why now, and on your dashboard Start here shows it above the lead’s words.
• Filter by it. Changed in the last 30 days, in Filters, narrows the list to the leads with news, by kind. On the Watchlist, a Last change column shows the newest change for a watched person or their company.
• Colleagues who engage. The company line names up to three colleagues who also engage with you, so you can see when a whole team is paying attention.
• Get told. The Lead changes email switch, under notifications, is on by default. Destinations can receive the lead.changed event once you turn it on.

Kept to real news

A role counts only when it started in the last 90 days and two checks a few days apart agree. Side roles such as advisor, board, investor, and freelance are left out. Funding comes from US SEC Form D filings, matched to the company’s exact name.

On Solo and above, and the free trial includes it. Each plan tracks your watched profiles first, then your best ICP leads: 250 people and 150 companies on Solo, 750 and 400 on Growth, 2,000 and 1,000 on Enterprise and Agency. First checks are spread out, so changes arrive over the coming days. See company changes.

Every profile on your Watchlist, your own and each competitor, influencer, investor, or company page you watch, now has stats. They answer two questions: is this profile worth watching, and what can you show a client about it. The answer always sits next to the ICP engagers the profile brought you, so a big audience never passes for a good source on its own.

What you get

• Two new Watchlist columns. Followers and Posts/wk on every profile and company page row, over 7, 30, or 90 days. Engagement rate and ICP engagers are in each profile’s stats.
• A profile’s stats. Select a profile’s row on the Watchlist, choose Profile stats from its menu, or open Profile stats in its agent’s details on Agents. The stats open on one sentence that sums up the window, then Followers, Posts a week, Eng. rate, Avg per post, Engagers read, and ICP engagers, with Overview, Top posts, and ICP engagers tabs: follower growth, each week’s posts and engagement, the top posts, and the top ICP engagers. Top posts can be ordered by engagement or by the ICP engagers they brought.
• Your numbers beside theirs. A watched profile’s stats show your own profile’s numbers next to its own, and Previous profile and Next profile step through the list. To change or remove a profile, choose Manage from the row’s menu.
• Watched profiles in client reports. Every report, the weekly Agency report included, has a section with each watched profile’s stats for the report’s dates, so an agency can show a client’s profile against its competitors. Reports are Solo and above.
• For AI assistants. On Solo and above, a read-only profile_stats tool returns the same numbers for every watched profile over the last 1 to 365 days.
• Every plan. Stats are not plan-gated. On Free they cover your own profile, the one profile Free watches.

What the numbers count

• Engagement uses LinkedIn’s public counts. Engagement per post is the reactions, comments, and reposts LinkedIn shows. Engagement rate is each post’s engagement divided by the profile’s follower count, averaged over the window’s posts: the same formula as the free engagement rate calculator.
• Engagers read is a floor on big posts. Embers reads up to 100 reactions and 100 comments per post on a person’s profile, and 25 reactions and 15 comments on a company page.
• Follower history starts when profile stats shipped. Embers refreshes the follower count of every watched profile you have not paused once a week, while your agents are running, so growth fills in over the coming weeks.
• Posting is counted from when Embers started watching. When a window starts before that, the stats say “since” and the date.
• Audience numbers count everyone. Only ICP engagers leave out people at your own company and companies you have blocked.

Also changed

• A watched profile that grows past 250,000 followers is put on hold. The weekly follower count now feeds the very large audiences rule, so a profile that crosses the line while you watch it is held like one that was that large when you added it. If the count drops back under 250,000, its scans resume.

See profile stats and what a client report contains.

Salesforce, Pipedrive, and Attio join HubSpot, Notion, and Google Sheets under Send leads to your workspace on the Integrations page. Connect one and each qualified lead arrives with the signal that surfaced it, so whoever works it in your CRM knows why to reach out.

What each one writes

• Salesforce. A Salesforce Lead for each qualified lead, or an update to the Lead or Contact your org already has, with a completed Task that says why it qualified. Set the Lead Source, and connect a Production or Sandbox org. Your org needs API access. Set up Salesforce
• Pipedrive. A Person, created or updated in the fields you map, plus a Lead in your Leads Inbox with the label you choose, and one note. Connect with your personal API token, or Connect Pipedrive where it shows. Set up Pipedrive
• Attio. A person on Attio’s own attributes, optionally added to a list and linked to their company, with one note. Connect with a workspace API key, or Connect Attio where it shows. Set up Attio

Works like the rest

• Send the leads you already have. After you connect, Send existing leads sends the qualified leads Embers found before, once, best score first. HubSpot has the same button now.
• Send by hand. Each CRM is in Send to on the leads list.
• Rules, activity, and pauses. Delivery rules per destination, 30 days of activity with retry, and a pause with its fix when the connection or a field changes under it.

On Solo and above, and an account administrator connects them. See choose where Embers sends your leads.

Someone asking for a recommendation is a different conversation from someone praising a post. Embers now names what each person’s words show, with one set of eight intents used the same way across the app.

What changed

• Eight intents. Looking for a solution, Switching providers, Seeking recommendation, Hiring / outsourcing, Pain point, Growth / change, Question, and Advocacy. Hover a chip to read what it means.
• One chip everywhere. The intent shows on Leads, Posts, Comments, the lead sheet and page, the Priority Queue, and the dashboard.
• Filter by it. Intent in the leads filters, and an Intent menu on Posts and Comments with a count beside each intent.
• More leads from your comments. When you comment on someone’s post and their post shows a buying intent, its author now becomes a lead, with a signal such as “Asked for recommendations in a post you commented on.”

On Solo and above. See filter the leads list, find a post, and post authors who need what you sell.

If you tracked people and keywords in another tool, you no longer have to add them one at a time.

How it works

• Upload or paste. On the Watchlist, open Add monitor and choose Import. Choose a CSV file, or paste one LinkedIn profile, company page, or keyword per line.
• Review before anything is added. Review import says what it found, such as “Found 12 profiles and 3 keywords in 812 rows.”, with a checkbox and a role for each profile. Embers reads the column headers, so the people your old tool found stay unchecked and only the profiles you watched are picked. Choose what to keep and import them all at once; a Not added list gives the reason for anything refused.
• During setup too. The Monitors step has Import a CSV or a list for anyone moving from Trigify or another tool.

On Solo and above. Each imported profile and keyword counts toward your plan’s limits, and a profile Embers knows has 250,000 or more followers is not added. See import profiles and keywords.

Everything else new from 16 to 31 October, beyond the entries above.

Around the app

• A notifications inbox. The bell at the top opens Notifications: your lead updates from the last 30 days, with Unread and All, Mark all as read, and Mark as unread. During a free trial, a Free trial card in the sidebar shows the engagements used and the days left.
• What is new since your last visit. Posts and Comments show how many are new in the sidebar, and each row says what it brought, such as “2 new leads”.
• Every comment in one place. The Comments page now lists comments from your profile, your watched profiles, and your keywords, with All sources, Yours, Watchlist, and Keywords tabs.
• More ways to read a list. Compact list and Grouped views on Posts and Comments. On Leads, Posts, Comments, and the Watchlist, show 20, 50, or 100 Rows, type a page number to jump to it, and come back to the same sort.
• A fuller lead sheet. The lead’s company links to its LinkedIn page and website, and the full lead page reads like the sheet with more room. On Leads, a cut-off Title, Company, or Why cell shows in full on hover.

Destinations and your AI assistant

• Company data on every lead you send. Webhooks, every destination, and the CSV now carry the lead’s country and their current company’s size, industry, LinkedIn page, website, and domain. A value Embers does not know is left blank, never guessed.
• Several accounts of one outreach tool. With two or more HeyReach, Instantly, Smartlead, or Emelia accounts, the page opens on All accounts, one view and one activity log, then a tab per account.
• Keywords as chips. In a configuration, tick Keywords to pick from your tracked keywords as chips, each with its post count.
• More for your AI assistant. New tools sum up a workspace, rank posts by the leads they brought, list and change your watched profiles and keywords, reveal a lead’s contact details, and undo your last ICP change, with three ready-made prompts: Work today’s leads, Check my ICP, and Weekly pipeline review. An assistant you connected before needs to reconnect once to get the new permission to watch profiles and track keywords.

Suggestions, setup, and the trial

• Suggestions that keep coming. Answer one and the next takes its place. On Agents, one banner says how many are waiting, with the best one ready to answer.
• Setup that gets to leads sooner. Skip, just find me leads starts the first scan from your ICP, setup asks Where are your buyers?, your agents go live on their own once the first scan settles, and the first lead you see comes with Write reply to draft your message.
• The trial starts when you see your leads. The 7 days of the free trial now count from the first time you open your leads, so days spent waiting for the first scan no longer use it up.

See notifications, the lead object, what an assistant can do, and the free trial.

Google Sheets joins Slack, HubSpot, and Notion under Send leads to your workspace on the Integrations page (/integrations/google-sheets). Each qualified lead becomes a row. With Everything else switched on, the same row updates when the lead engages again or changes status.

What you get

• A spreadsheet in one click. Create a spreadsheet makes one in your Google Drive with its columns ready and mapped, so leads start arriving with no further setup.
• One row per lead. Embers finds the lead’s row by the LinkedIn profile URL or Embers ID before every write, so sorting and filtering your sheet is safe and a repeat never adds a second row.
• Real values. The score is a number, ICP match is TRUE or FALSE, and text that starts with = stays text instead of running as a formula.
• Your own columns stay yours. Add columns for your notes beside the ones Embers fills. Embers never writes into a column it does not fill.
• Access to only your Embers files. Embers can open the spreadsheets it creates, and nothing else in your Google Drive.
• Rules, activity, and pauses work as they do for Notion: delivery rules per destination, 30 days of activity with retry, and a pause with its fix when the spreadsheet, tab, or a column changes under it.

Available on Solo and above; an account administrator connects it. See send qualified leads to Google Sheets and Google Sheets delivery is paused.

Notion joined the Integrations page on 5 October (/integrations/notion). Connect it once and Embers keeps a Notion database in step with your LinkedIn pipeline.

What you get

• Your database, your properties. Pick a database you shared with Embers, then choose which property receives each field: name, company, job title, score, ICP match, status, why now, last engaged, and more. Embers pre-selects properties whose name and type match, and never adds, renames, or removes a property.
• One row per lead. A qualified lead adds a row. With Everything else switched on, a lead who engages again or changes status updates the same row.
• Send by hand too. Notion is in Send to on the leads list, and a lead you pushed shows a Sent to Notion pill that opens its page.
• Test before leads flow. Send test checks the connection, the database, and the mapped properties without creating a page.
• Rules, activity, and pauses: delivery rules per destination, 30 days of activity with retry, and a pause with its fix when the connection, the database, or a property changes under it.

Available on Solo and above; an account administrator connects it through Notion’s own sign-in. One Notion workspace and one database per Embers account. See send qualified leads to Notion and Notion delivery is paused.

The leads list now carries a lead from first look to a booked call without leaving the page.

What changed

• Focus. Work these 20, above the list, puts the page’s leads in front of you one at a time: who they are, what they said, why they fit, and a draft message. Copy and open LinkedIn, send it there, then Mark contacted, and Focus moves on. j, k, o, c, and d skip, go back, open, mark contacted, and dismiss.
• Contacted is a pipeline. Everyone you reached out to, grouped by what to do next: Follow up today, Replied: book the call, Gone quiet, Waiting for a reply, and Calls booked, with the reply and call rates on top. Solo and above.
• Lists that fill themselves. Choose New leads go to on a watched profile or keyword, or Fill automatically on a list, and each scan adds that source’s new ICP leads to it. Lists sit in the sidebar under Lists, and a lead’s sheet shows which lists they are on, with a way to take them off. Solo and above.
• New ways to read your leads. View switches Leads to Cards, Compact list, or Grouped by source, and Posts, Comments, and Watchlist to cards. Nothing changes until you choose Apply.

See work leads one at a time, work your conversations, fill a list automatically, and choose how the list looks.

On 1 October Hot Leads took over from ICP Watching as a tab. Since 5 October Hot is a mark on the lead instead, and it asks for recent engagement as well as fit, so a strong fit who went quiet weeks ago is no longer Hot.

What changed

• Tabs. Leads opens on ICP Leads, everyone who matches your ICP. All Engagers holds everyone who engaged, match or not, and Contacted is your pipeline.
• Hot. A confirmed ICP match with a fit above 70% who engaged in the last 7 days gets an orange flame. The Hot button beside Filters shows only them, and the sidebar’s Leads row counts them. An old Hot Leads link opens ICP Leads with Hot on.
• The table. ICP is the fit with four bars for its tier, Signal shows who they engaged with, and Why quotes their latest comment. Found, in Edit Columns, says when Embers first found them, and every tab sorts by Newest found or Oldest found.
• The lead page opens on a verdict: their fit as a ring, one line on whether to act, such as “Strong fit, gone quiet.”, their latest words, and Write message.
• The dashboard opens on who to message first: one person in the dark card, Hot leads first, with what they said and Write reply, then the next two and this week’s counts. New leads are counted as people, not engagements.

See Hot leads, the full lead page, and your dashboard.

Sending a lead to an Emelia LinkedIn-only campaign that already held that person failed with “This contact is already included in this campaign”. Every later push of the same lead failed the same way.

What changed

• Delivered, not failed. When Emelia answers that the person is already in the campaign or list, the push shows as Delivered. That covers people you added in Emelia yourself.
• No repeat pushes. Embers records the lead as sent to that campaign, so a later push to it is skipped as already pushed to the campaign.
• Earlier errors. A push that already failed this way turns Delivered when you choose Retry on it.

See Push qualified leads into Emelia.

Everything else that shipped from 1 to 15 October, beyond the entries above and the ones posted earlier this month.

Around the app

• One frame on every screen. A sidebar on a tablet or computer, a top bar across every page, and a tab bar along the bottom on a phone. Settings, ICP, and Agents share it, and settings save as you change them.
• Help where you are. The ? button in the corner of every page has Share feedback and Chat with us. Ask a human and Book a call sit at the foot of the sidebar.
• Posts, Comments, and Watchlist are tables with sortable, resizable columns, like Leads. Posts show the leads each one brought, and Comments open on the answers you got.

Integrations

• One Integrations page in the sidebar (/integrations), on three shelves by the job each tool does. Zapier, Make, and Clay set up in place, and Webhooks and MCP have pages of their own.
• Each destination’s page opens on its status, with Needs attention listing each problem beside its fix, and an Activity log.
• Emelia can target older LinkedIn-only campaigns, listed with “(LinkedIn)” after the name.
• Clean names for outreach tools. First and last names arrive without emoji, credentials after a comma, or nicknames in brackets, so a {{ firstName }} greeting reads right.

Agents and setup

• Your profile is one agent. One Your profile agent reads the reactions and comments on your posts and the replies to comments you leave elsewhere. Outreach configurations choose agents by profile, plus Keywords (all, or the ones you pick) and Qualified posts.
• First leads sooner. Setup searches your keywords alongside the first scan, and the email that says your first leads are ready names them.
• Setup on a phone, your ICP in plain words, and a done screen that shows what Embers found.

Account and support

• Delete a workspace or your account. The Danger zone now separates Delete workspace for the owner, Leave team for members, and Delete my Embers account for everyone.
• See when support looked. Support can open a workspace read-only to help you, never signed in as you. Each visit shows under Support visits on Profile for 90 days.
• Error references. The error page, and any message about a problem on our side, now ends with a short reference, such as “Reference K7Q29XMA.” Quote it when you write to us and we can find what went wrong straight away.

Fixed

• Keyword tracking no longer drops posts by people who fit your ICP just because they did not ask for help, and each keyword lead now says why it is a lead.
• A lead whose company name shares a common word with your category, such as Capital, is no longer ruled out as a competitor.
• Two leads who did exactly the same thing now get the same score.
• A 6-month plan shows its price as the total for the period, such as “$420 every 6 months ($70/mo)”.
• Renaming a workspace on Free no longer shows its owner a member’s locked screens until a reload.
• Digest and roundup emails no longer show code such as ' where an apostrophe belongs.
• Qualify a post accepts LinkedIn links that end in -share- or -ugcPost- and a number.

See find your way around, integrations overview, and account settings.

Embers suggests pages to watch, keywords to track, and fixes to your ICP from what your agents found. Until now only paid plans got them, every 7 or 15 days, and only on the Dashboard.

What changed

• Every plan, every 7 days. Free and the free trial get suggestions too. A batch holds only what your plan can act on, so a Free batch has no pages or keywords to add.
• Pages to stop watching. A profile or page you watch that has not posted in 30 days, or whose posts drew 50 or more people in 30 days with none who fit your ICP.
• Keywords to stop tracking. A keyword with no posts from buyers in 30 days. Stopping a page or keyword keeps its leads, and Undo puts the same one back.
• Audiences checked. Embers samples the people who engaged with a suggested person’s or page’s recent post, judges them against your ICP, and drops pages that fall well below your best source. A checked page shows the counts.
• More places. Suggestions now show on Agents, and as Suggested for you in setup’s Monitors step, in New agent’s Watch a profile step, and in the Watchlist’s Add monitor panel. The old “Popular profiles to track” list is gone.

See act on suggestions.

When a trial or paid plan ends, Embers offers 20% off your first billing cycle for 14 days. Until now, every plan you picked in that window checked out with the offer, whether you had asked for it or not.

What changed

• Claim to apply. The offer applies only after you click Claim 20% off, on the Billing screen or beside the plans in the plan table, the plan picker, and Choose a plan.
• Unclaimed means full price. A plan picked without claiming the offer checks out at the normal price.
• The screen says which. Before you claim, the plans read “You have a 20% return offer”. After, they read “Your 20% return offer is applied at checkout”.

See return offers after a plan ends.

The Embers affiliate program now runs on Partnero. Partners sign up, log in, get their personal referral link, and follow clicks, paying customers, and commission status in the Partnero dashboard. A referred customer appears there with their first payment.

What changed

• Commission. Approved partners earn 20% of eligible net subscription revenue from a referred customer for the customer’s first 12 months.
• Dashboard and links. Referral links come from your Partnero dashboard. Use that link in new posts and reviews.

What stays the same

The 30-day referral window, the 30-day commission hold, and monthly PayPal payouts once a balance reaches 50 USD. The affiliate terms remain the controlling policy.

Slack, HubSpot, and signed webhooks used to pause the whole destination when a single lead was refused, so one bad lead stopped every lead after it. A destination now pauses only when the connection itself is broken.

What changed

• Slack. A card Slack refuses for its content, such as invalid_blocks or msg_too_long, fails on its own row in Delivery status. The next lead still posts.
• HubSpot. A contact HubSpot refuses for its values (VALIDATION_ERROR, such as an invalid email, or CONFLICT), or a lead with nothing to write, fails on its own. The next lead still syncs. A contact deleted or merged in HubSpot is created again (or matched by email) instead of pausing HubSpot.
• Signed webhooks. A 400, 409, or 422 from your receiver fails that event only. A 401, 403, 404, or 410 still pauses the endpoint at once.
• Five in a row still pause. A receiver that refuses five leads in a row, with nothing delivered in between, is paused with a reason that says so. One successful delivery resets the count, and so does resuming, reconnecting, or switching delivery back on.
• Connection errors are unchanged. A revoked token, a missing channel, a rejected HubSpot token, and retries that run out pause the destination as before.

See webhook retries and pauses, Slack delivery is paused, and HubSpot delivery is paused.

ICP Watching held right-fit leads that had not yet warmed up. Hot Leads now covers that job, so the separate list is removed.

What changed

• No Watching list. Leads that match your ICP with an ICP fit above 70% appear on the Hot Leads tab. Every other lead who matches your ICP is on All Leads, and everyone who engaged is on All Engagers.
• One fewer notification. The Watched lead becomes ICP update type is gone from Settings, then Notifications, leaving seven.
• Editing your ICP works as before. Embers still reclassifies your leads after you save a change.

See find and filter leads and choose your notifications.

Instantly took qualified leads into email campaigns. Smartlead now does too, and the two can run side by side on one workspace.

Smartlead delivery

Connect your Smartlead account from Settings → Integrations → Smartlead with your Smartlead API key (Smartlead, then Settings, then API key), then add configurations that route each agent’s leads into its own Smartlead campaign.

• Every pushed lead carries the signal that surfaced it as the embers_signal custom field, so a sequence can open with {{embers_signal}}. embers_icp_reason, embers_score, embers_source, embers_lead_url, and embers_title come with it.
• A lead without an email has it looked up first on paid plans, and is skipped only when none is found.
• Smartlead’s global block list, unsubscribe list, and community bounce list are always respected, and so are people already in another campaign. A lead Smartlead refuses shows as skipped with “Smartlead skipped it:” and Smartlead’s reason.
• Campaigns only: Smartlead has no lead lists, and there is no sender to pick, because the campaign rotates its own mailboxes. A paused or draft campaign holds the leads until you start it; a stopped or completed one pauses its configuration, because Smartlead never emails new leads there.
• Push by hand, or automatically with delivery rules. Send to works here too.
• Embers never emails anyone. Smartlead does the sending.
• Solo and above, account administrators only. See Push qualified leads into Smartlead.

Instantly and Smartlead together

A workspace can now connect both email tools at once, each with its own key, fields, and configurations. If both listen to the same agents, a lead goes into both; split them by agents or delivery rules to keep one tool per lead. In Send to you pick the configuration, and an AI assistant pushing to email_outreach over MCP gets the list of configurations back and asks you which one.

The leads list and the ICP review were built for a desk. On a phone they now fit the hand.

What changed

• Lead cards are three steady lines. Who the person is and their score, what they do, then one signal line (how often they engaged, where and when, and intent) with the status at its end. When the card is narrow, whole details drop off the end of the signal line instead of being cut mid-word; the lead sheet still lists them all.
• Status opens a sheet. Tap the status on a card and a sheet rises from the bottom with one large row per stage: Pending, Contacted, Replied, Call Booked, and Not Interested. Picking one closes it. A Pending lead also offers Dismiss lead there.
• ICP review fills the screen. On a phone, previewing an ICP change opens full screen: the counts as tiles, full-width tabs, Keep as a switch on each lead, and Apply pinned to the bottom where your thumb is.

See find and filter leads and change your ICP safely.

Saving your ICP judges your leads again with AI, and until now you found out who dropped only after the fact. Now you see it first, and you can take it back.

What changed

• Review before saving. When you save, Embers runs the edit against your real leads. Current matches that one of your exclusions would veto show up straight away, with the rule named. Then the AI re-judges a sample of up to 200 leads and lists the matches it would drop and the leads it would add. Nothing is saved while you look.
• Keep. Tick Keep on any lead the edit would drop and it stays an ICP match, pinned the same way as tagging it yourself.
• Your change or a correction. Leads a save would move whatever you edited (an old label your current ICP disagrees with) are listed as re-check corrections, apart from the ones your edit moves. Both are applied.
• Apply saves what you saw. Applying a preview saves those verdicts as shown. The rest of your leads are judged in the background.
• Adding targets drops no one by itself. An edit that only adds to job titles, departments, industries, or locations you already list, or only removes exclusions, cannot drop a lead itself. Every save still re-checks every lead, so any drop it shows is a re-check correction.
• Undo last change. Puts back the criteria and every lead verdict the last save changed, in seconds, with no AI involved. Leads you kept stay pinned, and deliveries or notifications already sent for leads the change added are not recalled.
• Change history. Every save records the ICP as it was before. Restore to before this on any save loads the ICP as it was before it into the editor, then you review and apply it.
• For AI assistants. A new preview_icp_update tool runs the same preview, and update_icp can apply a preview as shown and keep leads you name. That makes twelve tools.

See change your ICP safely and connect an AI assistant.

HeyReach took qualified leads into LinkedIn sequences and Instantly into email. Emelia now takes them into sequences that mix the two.

Emelia delivery

Connect one Emelia workspace from Settings → Integrations with your Emelia API key, then add configurations that route each agent’s leads into its own Emelia campaign or contact list.

• A lead needs a public LinkedIn URL or an email. A lead with neither is skipped, and Embers never spends a contact lookup for Emelia.
• A campaign target adds the lead to the campaign’s first attached contact list, which is how Emelia enrolls contacts. A campaign with no list pauses its configuration until you attach one.
• There is no sender to pick: the campaign’s own LinkedIn accounts and mailboxes send.
• Every pushed lead carries the embers_* custom variables, so a LinkedIn message or an email step can open with {{embers_signal}}.
• A campaign that is not running still takes the leads and holds them until you start it.
• HeyReach, Instantly and Emelia can all be connected at once, each with its own configurations. Send to works here too.
• Embers never sends on LinkedIn and never emails a lead. Emelia does the sending.
• Solo and above, account administrators only. See Push qualified leads into Emelia.

The Leads table has always shown where a lead’s signal came from. The CSV export now carries it too.

What changed

• Signal Source. Where the lead engaged, most recent first: Your post, Your comment, Keyword post, Qualified post, or a watched profile with its role, such as a competitor. Several sources are joined with a pipe.
• Signal Date. The latest engagement date for each source, in the same order, so splitting both columns on the pipe gives one date per source.
• A lead with no recorded source leaves both cells blank.

That makes it easy to sort a sheet into people who reacted to your own content and people who reacted to a competitor’s. See export leads to CSV.

One HeyReach or Instantly connection used to mean one campaign for every lead. Now it holds as many routes as you need.

Configurations

After you paste the API key, the tool’s page in Settings → Integrations shows a Configurations list. Each configuration picks:

• Which agents feed it. All of them, or only the ones you tick: posts, comments, keyword tracking, or a watchlist profile by name.
• Where their leads go. A campaign or a lead list, and for a HeyReach campaign, the sender.
• Who gets delivered. A minimum score, ICP only, and excluded titles and industries. A new configuration starts at score 70 with ICP only on.

Each row has its own switch, so turning one campaign off never touches the others. A campaign that stops running pauses only the configuration that sends to it.

• Send the leads you already have. When you add a configuration, tick Also send leads you already have to send the matching leads Embers already found, once. Anyone already in that campaign or list is skipped.
• Send to picks a configuration. With more than one, Send to on a lead lets you choose which campaign it goes into.
• Your existing setup carried over as your first configuration, with the same campaign, sender and rules. A setup in automatic mode is switched on; one in manual mode starts switched off, so nothing sends until you turn it on. A Sources rule became the agents of those types.
• Solo and above, account administrators only. See Push qualified leads into HeyReach and Push qualified leads into Instantly.

LinkedIn’s image links expire, so a lead’s photo could quietly turn into initials a few days after Embers found them. That is fixed.

What changed

• Pictures that last. Embers keeps one copy of each person’s latest public profile picture and shows that, so it no longer depends on a link that expires. When a person changes their photo, the newest one wins everywhere they appear.
• Comments shows the post author. Each row on the Comments page now shows the picture of the person who wrote the post, where it always showed initials before.

See the Comments page.

The Leads page opened on All Leads even when the first tab in the strip was ICP Matches, so the list you saw did not match the tab that looked selected.

What changed

• Opens on the first tab offered. For post engagement that is ICP Matches. From an agent that only offers All Leads and Contacted, it is All Leads.
• “All leads” links mean all leads. Links from the dashboard, the command palette, the sidebar, and the Posts, Comments, and Watchlist pages that promise every lead now open the All Leads tab explicitly.

See find and filter leads.

Connecting a tool used to mean scrolling one long settings page. Each tool now has a page of its own.

What changed

• One row per tool. Settings, then Integrations lists every tool with its logo, a Connected or Needs attention chip, and a status line. The Zapier, Make, and Clay recipes sit under them.
• Its own page. HubSpot, Slack, HeyReach, and Instantly each open at /settings/integrations/<tool>, with that tool’s settings card. The cards on the Integrations page and the Delivery rules action in the push toast open the same page.
• Real logos. Every card shows the tool’s own mark instead of a generic icon.
• The guide is one click away. Each card links the help article that sets it up, and the outreach tools repeat the link beside the API key field, where people stop to ask where the key lives.

See choose where Embers sends your leads.

Instantly finds a person by email, and public LinkedIn activity carries none. At launch, a lead without a revealed email was skipped. Now Embers goes and gets it.

What changed

• Looked up first. On a paid plan, a lead headed to Instantly with no email gets one contact lookup, the same as the Reveal button, and its delivery waits for the result.
• Sent when found. The lead goes to Instantly with its email, usually within a minute or two.
• Skipped with a reason when it cannot be. No email found, a lookup that fails or runs past 30 minutes, or an account still on the free trial, where contact details are locked. Each skip carries its reason, such as no email found for this lead.
• One paid lookup per lead. However many deliveries are waiting for the same person, Embers asks once.

See push qualified leads into Instantly.

HeyReach took qualified leads into LinkedIn sequences. Instantly now takes them into email.

Instantly delivery

Connect one Instantly workspace from Settings → Integrations with a scoped Instantly API key, pick a campaign or a lead list, and qualified leads can go straight into it.

• Only leads with a revealed email are sent. A lead without an email is skipped, not lost.
• Every pushed lead carries the signal that surfaced it in Instantly’s {{personalization}} field, plus the embers_* custom variables, so the first line of an email can reference what the person actually posted.
• A campaign that is not running still accepts the leads and holds them until you start it.
• Push by hand, or automatically with delivery rules: the same minimum score, ICP only, sources, and excluded titles and industries as every other native destination. Send to works here too.
• HeyReach and Instantly can both be connected, so one lead can go into a LinkedIn sequence and another into an email campaign.
• Embers never emails a lead. Instantly does the sending.
• Solo and above, account administrators only. See Push qualified leads into Instantly.

You no longer pick a plan and enter a card to try Embers. Signing up starts the trial, and you land in onboarding with the agents ready to go live.

What changed

• No card to start. The trial begins when you create your account. There is no checkout in front of it and nothing to cancel.
• The offer is the same. Your first 2,000 engagements, the public profiles Embers fetches for your workspace whether or not they match your ICP, or 7 days, whichever comes first.
• Nothing is charged automatically. No plan begins on its own when the trial ends, so there is no date to diary and no first charge to avoid.
• Skip the trial whenever you like. Choosing a plan during the trial charges you that day, ends the trial, lifts the 2,000 engagement cap, and unlocks contact details.

When the trial ends

Your agents stop and the account moves to Free, but you are not locked out. Every list keeps showing its first few real leads with the rest blurred behind a “Pick a plan” panel, and a banner explains why. Your leads, ICP, agents, reports, and settings are kept exactly as they were, and they come back the moment you subscribe.

Contact details, the email addresses and phone numbers on a lead, are still not part of the trial. They unlock with your first paid month.

The trial doubles. Solo, Growth, and Enterprise now start with your first 2,000 engagements free, up from 1,000.

What changed

• 2,000 engagements free. The trial covers the first 2,000 public profiles Embers fetches for your workspace, whether or not they match your ICP.
• 7 days is still the backstop. The trial ends at 2,000 engagements or 7 days after it starts, whichever comes first.
• Trials already running get the new cap. If your trial stopped at 1,000 and your 7 days are not up, your agents pick up again until 2,000.

Everything else is unchanged: a payment method is required at checkout, contact details unlock with your first paid month, and the first paid charge is refundable for 14 days.

See the free trial and plans and limits.

The trial used to be a week. It is now measured in what Embers actually does for you.

What changed

• 1,000 engagements free. The trial on Solo, Growth, and Enterprise covers the first 1,000 public profiles Embers fetches for your workspace: everyone who reacted to or commented on a post you watch, a keyword you track, or your own content, whether or not they match your ICP.
• 7 days is the backstop. The trial ends at 1,000 engagements or 7 days after it starts, whichever comes first. A busy watchlist gets there in a couple of days; a quiet one still has the week.
• Everything pauses at the end. When the trial ends without a plan, every agent is paused until you subscribe. Nothing is deleted, and subscribing picks the workspace up where it left off.
• Contact details are not part of the trial. Work emails and phone numbers unlock with your first paid month on Solo or higher. Until then the contact card on a lead is locked and CSV exports leave those columns blank.
• You can see the count. Settings, then Billing shows engagements used, days left, and the first billing date; the dashboard banner counts both while the trial runs.

A payment method is still required at checkout, and the first paid charge is still refundable for 14 days.

See the free trial and plans and limits.

The legacy dashboard view retires on 1 October 2026. Copy published briefly after the new dashboard shipped said 31 October. That date was wrong, and every page now says 1 October.

From 1 October 2026 at 00:00 UTC the new intent dashboard is the only view. Settings, then Profile, under App view will no longer switch you back. If you still use the previous overview (summary tiles, score distribution, top post, recommended actions, recent leads), move to the new view before then.

See Reading the dashboard.

Embers decides who is worth a conversation. This month it can hand that decision to the tool that starts one, filter what reaches every destination, and let you push a lead the moment you find it.

HeyReach delivery

Connect one HeyReach workspace from Settings → Integrations with your HeyReach API key, pick a sender and a running campaign or a lead list, and qualified leads can go straight into the sequence.

• Every pushed lead carries embers_signal, embers_icp_reason, embers_score, embers_source, and embers_lead_url as custom fields, so the first line of a sequence can reference what the person actually posted. Every lead is tagged embers in HeyReach.
• One push per lead per target. The same campaign skips a repeat as already pushed; a different campaign is a new push.
• Manual mode is the default. Automatic mode starts at ICP only and a minimum score of 70, because a LinkedIn sequence is a costlier mistake than a message in a channel.
• Embers never sends connection requests, messages, comments, or reactions on LinkedIn. HeyReach does. Embers pushes leads, and it never starts, resumes, or finishes a campaign on your behalf.
• Solo and above, account administrators only. One HeyReach workspace per Embers account. See Push qualified leads into HeyReach.

Delivery rules on every native destination

Slack, HubSpot, and HeyReach each have a Who gets delivered section: a minimum score, ICP only, the sources that count, and up to 50 excluded titles and 50 excluded industries. Rules are per destination, so Slack can stay wide while the CRM and the campaign stay narrow.

A lead a rule holds back is written to the delivery log as skipped with the reason, not retried and not lost, and can be sent anyway from that row. Signed webhooks are deliberately unfiltered and still carry every qualifying lead.

Send to

Send to appears on the leads list bulk bar, in the Priority Queue card menu, and on a lead’s detail page. Push up to 100 selected leads to a connected destination at a time, 60 actions an hour per person, with an ignore rules tick for the leads you have already judged yourself. Any member of a paid workspace can use it; connecting a destination and editing its rules stay with administrators.

An assistant connected over MCP gains the same ability as a confirm-gated tool, so “push these three to the campaign” asks before it acts.

Also this month

• Accept and reply status flowing back from HeyReach into Embers is not shipped yet. HeyReach exposes both per lead and as rates, and it is on the list.

A pass against the shipped product turned up a handful of help-center claims that were wrong. The articles are updated. The short version:

• Paid plans scan 500 posts per run and collect 1000 reactions and 1000 comments per post, not the Free figures of 30 / 100 / 100 that the docs had published as if they were universal.
• The return offer after a plan or trial ends runs for 14 days, not 7.
• A downgrade is blocked only by a member overage. Watched-profile and keyword overages warn and still let you confirm.
• Free accounts get no digest and no update notifications, but they do get the first-leads-ready email, the trial nudge, and transactional mail.
• Connected apps needs no administrator role. Any signed-in member can open it. The plan check happens on the first assistant tool call.
• Qualify Post is capped at 20 submissions per billing cycle on paid plans, and is off on Free.
• Agency includes dedicated onboarding, the same as Enterprise.
• Company pages cap comments at 15 and reactions at 25 per post. Posts per scan follow the plan cap.

See plans and limits, change your plan, post engagement, and Connected apps.

Two changes from watching new accounts land.

Notifications

• Only new ICP leads email you by default. Hot leads, buying intent, company clusters, leads heating up, score drops, post spikes, and watched lead becomes ICP all start off. Turn on the ones you want.
• Notifications have their own tab: Settings, then Notifications. Which agents can email you, which update types get through, and the digest schedule all live there. Profile keeps your timezone, lead names, and password.
• Accounts that had never changed a toggle were moved to the quiet defaults. Anyone who had already switched something off kept their own settings.
• The three toggles that did not save before (leads heating up, watched lead becomes ICP, post spikes) now do.

Leads

• The Signal column is now ICP match: the fit percentage as a tile, the fit tier beside it, and the engagements by kind (comments, reactions, reposts, matching posts) as counts underneath.
• The signal score, its grade and trend, and why the person scored the way they did are on hover, so one row shows one number.
• The column header sorts by ICP fit, and the sort menu gained Best ICP fit and Weakest ICP fit. Highest score still orders by the signal score.

The dashboard has been rebuilt around the question it should answer: who is showing intent right now, why they matter, and what to do about it.

What changed

• Four numbers at the top: qualified leads (with this week’s delta), warm signals across profiles, keywords and posts, the average ICP match of your top 20 leads, and verified contacts with the enrichment rate.
• Qualified leads found: a running total of new ICP leads over the last 7, 30 or 90 days.
• Opportunity found: the highest-ranked lead whose latest signal reads as buying intent, with the reason and one button to review them. When nobody is asking, the card shows your strongest signal of the week.
• Audience fit: the share of your qualified leads by role, location or industry.
• Newest qualified leads: the four most recent, linking into the leads list.

The legacy view

The previous overview (summary tiles, score distribution, top post, recommended actions, recent leads) is still there as the legacy view until 1 October 2026. Switch under Settings, then Profile, under App view; the legacy view carries a banner with a one-click way to try the new dashboard, and the new view keeps a link back at the bottom. The choice is saved in your browser.

Paste one address into an AI assistant, approve Embers once in your browser, and work your lead queue in the conversation you are already in.

What changed

• Connected apps is a new screen under Developer. It has the server address to copy, the list of assistants you have authorized, and a record of what each one has done.
• One approval, no API key. You approve in the browser and Embers issues the credentials itself. There is nothing to copy into a config file.
• Ten actions. List your workspaces, read today’s queue, search leads, open one, draft an opener, read and edit your ICP, record ICP feedback, update a lead’s status, and block a company.
• Changes ask first. Editing your ICP or blocking a company tells you what would happen and waits for your agreement, because both affect more than the lead in front of you.
• It cannot act on LinkedIn. No posts, messages, comments, connection requests, or follows, and no assistant can start a scan. Drafting an opener saves a draft for you to send.
• Revoke any time. One button, and access stops immediately. Every action stays on the record for 90 days.

Available on Solo and above, for account administrators. Works with any assistant that supports a remote MCP server with OAuth.

See connect an AI assistant and AI assistant access.

Embers plans are now priced by the signal sources you watch, not by connected LinkedIn accounts. Every self-serve plan is exactly one workspace: one ICP, one set of watched profiles and keywords, one lead book.

What changed

• Solo stays $49 per month, or $39 per month billed annually: one member, 5 watched profiles, 10 keywords, standard support.
• Growth is the new name for Team: $99 per month, or $79 per month billed annually, with unlimited members, 10 watched profiles, 25 keywords, and priority support.
• Enterprise is new: $199 per month, or $159 per month billed annually, with unlimited members, 20 watched profiles, 50 keywords, priority support, and dedicated onboarding.
• Agency is now a plan of its own, priced per client workspace with volume pricing by client count. Each client gets its own workspace with 20 watched profiles, 50 keywords, unlimited members, and client-level reporting. Email viraj@useembers.com for a quote; there is no self-serve checkout.
• Watched profiles replace LinkedIn accounts. Any public profile you watch, including your own, is a watched profile with a role. Your own profile is optional, added from the same list, and you can add several within the cap. There are no seats and no extra-account add-on.
• Members are never billed. Growth, Enterprise, and Agency include unlimited members.
• Onboarding now runs audience, business, ICP, add profiles, preview, reveal, then plan. Solo, Growth, and Enterprise start with the 7 day card trial.

See plans and limits, watched profiles, change your plan, and agency workspaces.

Lead webhook payloads no longer include account.type (founder or ghostwriter). That flag never drove behaviour, and workspace setup (solo, team, or agency) already covers the same split.

What changed

• The signed webhook envelope still carries account.id and account.name. Use those to route events for more than one client account.
• schema_version is now 2026-09-10. api_version stays 2026-07-20.
• Settings no longer has an Account Type picker. Copy that used to say “your client’s leads” follows the agency workspace preset instead.

See the webhook payload reference.

Embers is now priced per LinkedIn account, and Team is one shared book of business instead of three isolated slots.

What changed

• Solo is the label for the starter plan: one LinkedIn account, one member, $49 per month or $39 per month billed annually.
• Team includes two LinkedIn accounts at $99 per month or $79 per month billed annually. Extra LinkedIn accounts are $59 per month, or $49 per month billed annually, when checkout offers the add-on.
• Agency is not a separate price. It is the Team SKU framed per client workspace: one lead book, watchlist, and report per client.
• Members are not LinkedIn accounts. Invite people to work the same queue. Buying another LinkedIn account is a separate action.
• Lead owners live on Team. The leads list has an Owner column so two people do not message the same person.
• Watchlist and keyword caps apply per connected LinkedIn account (5/10 on Solo, 10/25 on Team).

This supersedes the older “this is not a new Agency plan” framing: there is still no Agency SKU. Agency is a mode of Team, priced per LinkedIn account.

See plans and limits, LinkedIn accounts, and lead owners.

Until today, the only way to find out exactly how a destination behaved was to ask us. That answer now has a permanent home at the help center.

What is there

• Getting started: what Embers is and is not, the quickstart, connecting a public LinkedIn profile, and defining your ICP.
• Signals and leads: how the four agents collect engagement, how scoring works, ICP matching, and the company blocklist.
• Every destination: Slack, HubSpot, signed webhooks with a payload reference and signature verification, the Zapier, Make, Clay and n8n recipes, and CSV export.
• Account and billing: plans and limits, the trial, changing plans, cancelling, and notification settings.
• Troubleshooting: an empty queue, a paused Slack, HubSpot, or webhook destination, and missing email.

How it works

Search with Cmd+K or the slash key. Articles have a light and a dark theme. Every article is also published as plain Markdown at the same address with a .md suffix, so you can hand one to an assistant instead of copying screenshots.

One correction

The lead webhooks feature page previously implied that webhooks were available on the Free plan. They are not, and never have been. Slack, HubSpot, webhooks, and CSV export are all Solo and above, and are configured by an account administrator. The page and the machine-readable product files now say so.

The blocklist in Settings → Account used to be a list you kept. Now it is a filter the whole product obeys.

Blocked means blocked

Block a company once and everyone who works there disappears from the lead list, the Today queue, stats, CSV exports, client reports, digest emails, notifications, and every delivery destination you have connected: Slack, HubSpot, and signed webhooks. Nothing you blocked reaches an outreach tool.

• Matching runs on the company name, so acme.com also catches “Acme”, “Acme Inc”, and “Acme, Inc.”
• Current role matters. Someone who used to work at a blocked company still shows up.
• Remove an entry and those leads come back within a minute.

Block a company without leaving the queue

• From a lead: “Block Acme” sits next to the company name on the lead page and in the detail panel.
• From the Today queue: it is in the “More” menu on each card.
• In bulk: select leads in the table and use “Block company”. The confirm dialog names every company in the selection before anything happens.

Each block tells you how many other leads went with it, and the blocklist shows how many leads each entry is currently hiding.

Your own company is blocked for you

When you connect your LinkedIn profile or define your ICP, we add your own company to the blocklist automatically and label it. Teammates stop arriving as leads on day one. You can remove the entry whenever you want, and we never remove it for you.

This September, qualified leads can land in the Slack channel your team already lives in. Connecting a profile also starts from public history, and Team workspaces can keep more than one client isolated.

Slack delivery

Connect Slack from Settings → Integrations. Install the workspace, pick a channel, and send a test. After that, new lead cards post when someone qualifies.

• Get hot LinkedIn leads in Slack the moment they engage. No more tab-hopping to check Embers
• Every alert includes why they’re a fit plus the evidence, so your team can reply in one click
• Contact fields stay on the payload (when enriched) so you can act without opening another tool

Also shipping this month

• Connecting a profile now looks back at public history (up to 12 months), so the first queue can include people who already engaged instead of starting empty.
• A unified watchlist lets you follow public LinkedIn profiles beyond your own: competitors, investors, teammates, advisors, and client founders. Starter can watch five public profiles and Team ten.
• Team workspaces can keep isolated clients under one operator, with a switcher and branded client reports. This is not a new Agency plan.
• ICP Watching now distinguishes a rescore in progress from an honestly empty list after you edit ICP.
• Checkout keeps trial access until payment completes or is abandoned.

The Embers affiliate program is now open to creators, consultants, operators, and communities that help founder-led B2B teams make better LinkedIn pipeline decisions.

Earn recurring commission

Approved partners earn 20% recurring commission on eligible net subscription revenue from referred customers for the lifetime of the customer relationship.

The program uses a 30-day referral window. Commissions remain pending for 30 days and approved balances are paid monthly through PayPal after the balance reaches 50 USD.

Track referrals in one place

The Affonso partner dashboard provides a personal referral link and reporting for visits, leads, conversions, and commission status.

Embers now carries eligible referral data from the first visit through signup and Dodo Payments checkout. This keeps the affiliate record attached to the customer journey without adding it manually at payment time.

Promote the product accurately

The new partner resource kit includes current positioning, approved product facts, disclosure examples, ready-to-adapt social and email copy, and downloadable brand assets.

The core rule is simple: teach a useful LinkedIn signal workflow first, then show where Embers makes that workflow repeatable. Partners may not publish fabricated results, fake dashboards, private customer data, or unverified performance claims.

Read the program details, use the partner resources, or review the affiliate terms before applying.

Embers is adding a focused Today queue for the leads that deserve attention now.

Start with a prioritized queue

The Today queue combines ICP fit, signal age, lead status, and follow-up timing. Each item explains why it is prioritized and keeps the original signal attached.

You can open the LinkedIn profile, mark the lead as contacted, snooze it, dismiss it, or move directly to the next useful action.

Record what happened

Lead outcomes now support replies, meetings, opportunities, customers, no response, and not relevant.

This creates a clearer connection between a public buyer signal and the pipeline result it produced.

Reports now summarize contacted leads, replies, meetings, opportunities, and customers. They also show conversion rates, recorded opportunity and customer values, and results by signal source.

Keep control of every action

Embers does not send messages, connection requests, comments, or reactions. Suggested actions remain under your control.

See clear plan limits

Starter includes one connected LinkedIn account, five watched public profiles, and ten keywords. Team includes three connected accounts, ten watched profiles, 25 keywords, contact information when available, team invitations, white-label reports, and priority support. (Updated September 2026: watched profiles cover competitors, influencers, investors, and teammates on one count; the separate competitor number this post originally listed is gone.)

Both plans include the signal workflow, lead scoring, drafts, notes, follow-ups, reports, sharing, and signed lead webhooks.

The Today queue and outcome tracking are available now.

LinkedIn posts often keep attracting reactions and comments long after they are published. Embers now keeps those growing conversations in sync for longer, while making sure downstream automations receive the right people and the right context.

Keep growing posts in sync

Embers now revisits up to 90 days of your posts during the scheduled engagement refresh. This captures people who react or comment after the first scan, including activity that arrives several weeks later.

Existing workspaces receive a catch-up refresh automatically. After that, Embers revisits the full 90-day window every week and uses a smaller rolling refresh between those runs. Post engagement totals are rebuilt from the detailed reaction and comment records, so the people shown in Embers stay aligned with the activity available from LinkedIn.

Newly discovered engagers continue through ICP classification and scoring. If they qualify, they can enter the connection, messaging, or CRM workflows you already configured.

Send qualified leads to your automations

The new lead webhook now follows the same definition as the default Leads view. It is sent only when a positive-scoring engager matches your ICP or is manually approved.

People who do not match your ICP remain available in the broader engager view, but they no longer trigger a new lead webhook. This keeps connection campaigns and CRM automations focused on the prospects they were designed to reach.

Webhook delivery now waits for profile enrichment to finish, which makes role and company details more complete. Current work history and profile headlines provide additional fallbacks when LinkedIn does not return a structured job title.

Review webhook activity more easily

The Webhooks page now uses the same wider layout and pagination patterns as the rest of Embers. Delivery rows identify the person or report involved, show useful context at a glance, and support server-side filtering by status and event type.

Delivery details lead with the event summary and attempt history. Raw JSON remains available when you need it, but it stays collapsed until you choose to inspect or copy it. Older events that were created for a non-ICP engager are labeled clearly as historical engager events.

Search leads, posts, and comments from one place

Global search now searches account content instead of only matching navigation commands. Results can take you directly to a lead or comment, while broader actions open filtered views for leads, posts, and comments.

Search results include useful lead context such as names, companies, and job titles, making it easier to find someone without first opening the Leads table.

Recover agent work more reliably

Pending engagement backfills can start as soon as they are due instead of waiting for the next normal agent interval. If a server interruption happens after data is fetched, Embers now requeues normalization so that completed work is not silently discarded.

Together, these updates keep engagement counts fresher, protect lead automations from non-ICP engagers, and make it easier to understand what Embers sent and why.

The best lead workflow keeps the useful context moving without adding another dashboard to maintain. This July, Embers made that path clearer from a new LinkedIn signal to the next action your team takes.

Send qualified lead activity into your workflow

Lead webhooks are now available from the Developer area. Configure a destination, choose the lead events that matter, and inspect delivery history without leaving Embers.

Each delivery includes clear status information and the context needed to troubleshoot a failed request. Profile avatars and webhook history also hold up better when your workspace has more activity to review.

Review and export leads with less friction

Lead drill-downs are easier to navigate, and CSV exports now respect the exact page of leads you are viewing. That makes it simpler to share a focused working set instead of cleaning up an oversized export later.

Filters and overlays behave more reliably on mobile, so reviewing a lead or changing a view does not interrupt the rest of your workflow.

Make setup and account changes more predictable

Onboarding recovery is clearer when a step needs another pass, and the dashboard is faster and easier to navigate with assistive technology.

We also improved billing self-service, including scheduled plan changes, so account updates are easier to understand before they take effect.

Sharper context for every decision

The ICP editor now gives you more room to describe the people and companies you want to reach. Small improvements across authentication, account selection, and reliability help keep that context available when you need it.

Smaller improvements

• Lead profile details and webhook delivery views are easier to scan.
• Mobile setup and filter interactions are more dependable.
• Dashboard loading and accessibility are improved across day-to-day navigation.
• Error reporting is more resilient, so problems are easier for our team to identify and fix.

These updates share one goal: help you move from a LinkedIn signal to a thoughtful next step with less busywork in between.