Workflow
Turn a new inquiry into an alert someone can act on.
- Lead arrivesCapture contact, source, campaign, and urgency data.
- Choose recipientsRoute the alert to the right owner or response group.
- Send alertNotify email, chat, browser, or mobile channels.
- EscalateUse a backup channel when the lead remains unclaimed.
Why lead alerts fail
Lead notifications often fail because they are treated as simple messages instead of an operational workflow. A form email goes to one inbox, a CRM notification is ignored, or a chat message lands in a noisy channel without ownership. The lead technically arrived, but nobody knows who is responsible.
Instant lead notifications should do more than announce that a lead exists. They should tell the right person what happened, where the lead came from, why it matters, and what action to take next.
Notification channels
Alert channels
Choose channels your response team already watches.
- Email: useful for owner, manager, and monitored inbox alerts.
- Slack and Microsoft Teams: useful for sales pods, dispatch teams, and operations channels. Follow the Slack or Teams guide for setup.
- Discord and Telegram: useful for lean teams and community-driven operations. Use the Discord or Telegram guide.
- Browser push: useful when reps are working inside the dashboard throughout the day.
- SMS and WhatsApp: useful for urgent field, local service, or mobile-first response teams. Start with the SMS and WhatsApp guide.
- Voice fallback: useful when a missed high-value lead should trigger a call-style escalation. Configure it from the same fallback alert guide.
- CRM webhooks: useful when the alert should also create or update records in another system. Follow the CRM webhook overview.
What a useful alert should include
A lead alert should be short enough to act on quickly but complete enough that the recipient does not need to open three other tools before responding. InstaChime alert payloads can include contact name, phone, email, source, campaign, message, score, priority, SLA state, and the dashboard context needed to claim or review the lead.
Escalation patterns
Escalation sequence
Increase urgency only when the lead remains unclaimed.
- Primary alertNotify the assigned owner or response group immediately.
- Secondary alertAdd a manager or backup group as the SLA approaches.
- Fallback alertUse mobile or voice interruption for qualified urgent leads.
Primary alert
The assigned owner or response group receives the first alert as soon as the lead is captured.
Secondary alert
If the lead is not claimed within the expected window, a manager, backup owner, or wider response group can be notified.
Fallback alert
For urgent sources, SMS, WhatsApp, voice, or another watched channel can be used as a fallback when chat or email is not enough.
Delivery visibility
Alert attempts include channel, provider, recipient, status, stage, and response details so operations teams can see what happened after capture. That makes notification failures visible instead of leaving the team to guess whether a message was sent.
Common questions
Which alert channel should I start with?
Start with the channel your response team already watches during business hours. For many teams that is Slack, Teams, email, or browser push. Add SMS, WhatsApp, or voice fallback only for leads that justify interruption.
Should every lead alert every person?
No. Over-alerting makes people ignore the system. Route alerts by source, urgency, team role, client, or territory so only the right people are interrupted.
Can alerts and CRM updates happen together?
Yes. Use InstaChime to alert the team immediately and send the same lead to the CRM or automation destination for long-term recordkeeping.
Explore
See the messaging bridge guide, the Slack setup guide, or compare CRM lead alerts.
Start with a controlled test
Send a controlled lead alert.
Choose the channel your team already watches, then verify the message, recipient, and fallback path before launch.