Lead alerts
A lead is worth the most in the first few minutes. Lead alerts tell you, by push notification, email or Slack, the moment a contact fills in a form, subscribes, or warms up enough to be worth a call. Each alert links straight to the contact's profile.
Set them up
Go to Settings → Lead alerts.
When to alert:
- Turn on lead alerts: the master switch. Nothing is sent while it's off.
- A contact submits a form in an email: a form block in an email you sent, answered by a contact on your list.
- Someone subscribes through a signup form: alerts on the submission itself, before any double opt-in confirmation.
- A contact turns hot: their engagement score reaches the Hot-lead score threshold (1 to 500, 20 by default). At 20, a few opens and clicks plus one form submit or purchase within a month is enough.
Where to send alerts:
- Push notification goes to every device signed in to the MailInApp mobile app on this account. Tapping it opens the contact.
- Email goes to the addresses under Recipients, one per line. It's sent through your own sending setup (SMTP or domain sending) and counts toward your monthly sends.
- Slack posts to a channel through an incoming webhook. In Slack, add the Incoming Webhooks app to a channel and paste the URL it gives you (it starts with
https://hooks.slack.com/services/). It's stored encrypted and never shown again. Paste a new one to replace it, or Remove it.
Click Save, then Send test alert. It sends a sample hot-lead alert to every channel that's on, even while lead alerts are switched off, and shows whether each channel worked.
How often you're alerted
- Hot lead: at most once a week per contact. It fires when the score crosses the threshold on the way up, not every time it's above it.
- New lead: at most once a day per contact, so a person who resubmits a signup form isn't two alerts.
- Email and Slack together are capped at 60 alerts an hour per account. Push has no cap.
- Anonymous form submits (from a forwarded email or a published page) don't alert, because there's no contact to open.
An alert that can't be delivered, such as a dead Slack webhook, never affects the vote, submission or signup that triggered it.
The Notify me journey step
For alerts at a specific point in a flow, add a Notify me step to a journey. Write the message, using {{tags}} from the contact and the event that enrolled them, for example "New demo request from {{first_name}} at {{company}}." Under Send through, choose push, email, Slack, or any mix of them.
The step uses the channels set up in Settings → Lead alerts, but it works even while the automatic triggers there are switched off, and it isn't limited to one alert per contact a day. The journey's own entry rules decide how often a contact reaches it. The run always continues to the next step, whether or not the alert was delivered.
Because the two are separate, a contact can produce two alerts for one event: one from the Someone subscribes through a signup form trigger and one from a journey's Notify me step. Turn one of them off if you only want one.
The Speed-to-lead starter
The Speed-to-lead starter journey wires this up in one click. It creates a signup form on the list you pick. Each new signup alerts you right away and gets an instant reply with a one-tap poll. Two days later, contacts who engaged alert you again, and quiet ones get a nudge email.
Send alerts elsewhere
The same moments are available as account webhooks, lead.hot and lead.new, for Zapier, n8n or your own endpoint. Webhooks ignore the switches and limits above: subscribing is the opt-in. See webhooks & events.