Reply Follow-Through Playbook

Email and LinkedIn replies land in one place.

• Replies from EmailBison and HeyReach land in MasterInbox.

• EmailBison
• HeyReach
• MasterInbox

Every reply gets one label, and the label decides what happens next.

• MasterInbox tags it and Jev confirms the label:
  • Interested: handed to Reply to Warm Call
  • Not now: a date to come back
  • Referral or out of office: a new person to reach
  • Left the company: their replacement, and where they went
  • Not interested or unsubscribe: stopped for good

• MasterInbox
• Jev

The date they gave becomes the day you come back.

• The timeframe in their reply, read from the day they wrote it, sets a recall in HubSpot.
• The follow-up quotes their own sentence back to them, so it reads like a person remembered.
• Anyone who gave no date is checked again in 90 days.

• HubSpot

Referrals, out-of-office cover and replacements all become new leads.

• Referral: the person they named, opened with who sent you.
• Out of office: the named cover now, and the original person after they return.
• Left the company: their replacement, found with Sumble and LinkedIn, and the person at their new company.
• The enrichment waterfall uses IcyPeas, Prospeo, LeadMagic and GetLeads. Each vendor only sees the contacts the ones before it missed.
• MillionVerifier checks every address first, then BounceBan checks every address that passes.

• Sumble
• LinkedIn
• IcyPeas
• Prospeo
• LeadMagic
• GetLeads
• MillionVerifier
• BounceBan

Nothing in this play sends on its own.

• Each draft posts to Slack with the reply it answers.
• The owner approves it, edits it or kills it.

• Slack

The follow-up comes from the same sender, and the outcome lands in the CRM.

• EmailBison sends from the inbox that got the reply.
• OutboundSync writes the outcome to HubSpot.

• EmailBison
• OutboundSync
• HubSpot