Hunt → Call → Email or WhatsApp: A Practical Follow-up Workflow

Why it matters: A phone number or email address is not qualification. Start with companies that match the offer, then review which legitimate contact paths exist and which person is likely to own the problem.

• Define service, geography, and decision role
• Review source evidence instead of trusting a stale list label
• Save the shortlist in a shared working view

Why it matters: Use the browser dialer for accounts where a short conversation can confirm ownership, urgency, or timing. Keep the company context visible and avoid calling outside permitted hours.

• Check workspace DNC and prior history
• Use a focused or sequential one-contact-at-a-time call
• Do not treat no answer as permission to increase frequency indefinitely

Why it matters: A real conversation should produce a specific next action: requested information, a callback, referral to another person, or a clear stop. Save that outcome before opening the composer.

• Record a requested callback time
• Capture the prospect's language and question in notes
• Honor not-interested and do-not-contact outcomes across channels

Why it matters: Email is useful for formal detail and documents. WhatsApp can work for permission-based mobile follow-up in markets where the channel is expected. Neither should become an automatic duplicate of the same pitch.

• Reference the actual conversation instead of a generic template opening
• Use suppression, opt-out, queue, and sender-capacity controls
• Review history before starting the next sequence step