Skip to content

Qualified leads, in the Slack channel you choose.

Embers posts one card per event into a single channel: the score, why the person matched, the evidence, and a suggested opener. Connect a workspace, pick the channel, send a test.

Start free trial See pricing

Your first 2,000 engagers free. No card to start.

# leads One channel per account

EmbersAPP

New qualified lead

Nicolas ColeCo-founder · Ship 30 for 3091

Why nowPosted about declining LinkedIn reach

Open in EmbersLinkedIn profile

What posts here

  • New leads
  • Engagement refreshes
  • Status changes
  • Report ready

Illustrative examples from verified public profiles. No affiliation implied.

The card

Is this person worth a message? One card answers it.

Every lead card carries the same parts in the same order, so the channel reads at a glance: who, the verdict, why now, the proof, and a first line to edit.

  • The score, the ICP verdict, and the strongest signal
  • A quote from the post or comment, with a link to it
  • Email and phone only when Embers already has them
What the Slack card shows
Anatomy of a cardPick a part

Why now. One sentence on what they just did. The reason this card exists today.

Illustrative examples from verified public profiles. No affiliation implied.

Who gets delivered

A channel people read, not one they mute.

Set a minimum score and keep it to ICP matches. A lead a rule holds back is logged as skipped, with the rule and the value that failed it, and you can send it anyway.

  • Minimum score, ICP only, sources, excluded titles and industries
  • Checked in order; the first rule that fails is the reason
  • Rules decide what leaves Embers, never what it collects
Delivery rules
Who gets deliveredSlack
ICP only
  • Nicolas Cole91 · ICP match
  • Ben Shafii84 · ICP match
  • Oskar Kwasniewski62 · ICP match
  • Maceo Cardinale48 · Not an ICP match

Illustrative examples from verified public profiles. No affiliation implied.

Retries and pauses

Slack hiccups get retried. Real breaks pause and say why.

Rate limits and Slack server errors are retried on the same schedule as webhooks. A revoked token, an archived channel, or a removed bot pauses the install instead, and the reason shows on the Integrations screen.

  • Eight attempts over about 6.3 days
  • 30 days of delivery history, attempt by attempt
  • A master switch stops posting and keeps your choices
Slack delivery is paused
Delivery to #leads8 attempts, about 6.3 days
  1. Now Attempt 1: not sent yet
  2. 30 s Attempt 2: not sent yet
  3. 2 min Attempt 3: not sent yet
  4. 10 min Attempt 4: not sent yet
  5. 1 h Attempt 5: not sent yet
  6. 6 h Attempt 6: not sent yet
  7. 24 h Attempt 7: not sent yet
  8. 5 d Attempt 8: not sent yet

Pick what the receiver does.

Your next pass

Put the next good lead
where your team already talks.

Start with your first 2,000 engagers free and review the fit before choosing a plan. No card to start.

Your first 2,000 engagers free · No card to start · No LinkedIn login · Cancel anytime

Start free trial