Delivery failures30d
—
Bounces, spam complaints & send errors caught
Dashboard
Every bounced, failed or spam-flagged email — rescued on the lead's backup address.
Leads rescued—
—
Re-sent successfully to a backup address
Waiting to send
—
Queued behind your retry delay
No backup email—
—
Leads you can still save by adding an address
Rescue activity
Failures detected vs. leads re-approached
Failures
Rescued
Why sends fail
Breakdown by trigger
Where backups come from
Latest failovers
Most recent leads picked up by the app
| Lead | Primary address | Backup address | Trigger | Status | When |
|---|
Leads with a backup—
—
Ready to be rescued on the next failure
Still uncovered
—
One bounce away from being lost
Already lost
—
Bounced with nowhere to retry
Leads known
—
Contacts this app has handled
Add a backup address
GoHighLevel keeps one email per contact — store the second one here or in a custom field.
Saved addresses are used automatically the next time a send to this lead fails. Any lead sitting in No backup is queued again straight away.
Leads missing a backup
These are the ones still slipping away
Import backup addresses
One CSV beats a thousand manual entries
CSV
A header row is required. Name the backup column backup_email or email, and identify the lead with contact_id or primary_email. Addresses that look mistyped are reported rather than imported.
Suppressed addresses
Dead or complained-about addresses the app will never send to again
Delivery events
Raw signals received from GoHighLevel
App log
What the engine did, newest first
Audit trail
Every change to sending behaviour, and who made it
Sending route
Where lead email actually goes out from
Send lead email through
—
Connected email accounts
Your own sending identities — SMTP or a delivery provider
Connect an email account
Credentials are encrypted before they are stored
Provider
Send a test email
Proves the whole path end to end, and shows up on Sent mail
Sent30d
—
Every message this app put on the wire
Delivered—
—
Confirmed by the provider
Opened
—
Where the provider reports opens
Problems—
—
Bounced, complained, dropped or failed
| Recipient | Subject | Sent via | Status | Opens | When |
|---|
New leads30d
—
Leads created in this window
Booked calls—
—
Bookings made in this window
Still to come
—
Calls scheduled from now on
All time
—
Every contact in this sub-account
Leads over time
Leads created per day
Where they came from
The source column on each contact
New leads
—
Sender authentication
SPF, DKIM and DMARC decide whether your mail reaches the inbox or the spam folder
Check an address
Grade a lead's address before anything is sent to it
Suppression list
Addresses this app will never send to again
Hard bounces, spam complaints and unsubscribes land here on their own.
Demo mode
Sample sub-account with made-up leads, for walkthroughs and screenshots
Applies to the whole app, not just this sub-account. Turning it off deletes the sample data and hides the sandbox from everyone; turning it on creates it again. Real sub-accounts are never touched.
Failover engine
How and when a lead gets re-approached
Trigger on
Delivery mode GHL keeps one email field — pick how the app works around it
Where the backup address lives
Tick every custom field your sub-accounts use for a second email. The app also reads GoHighLevel's built-in additionalEmails list and anything saved on the Backup addresses page.
Before sending a bounce you never send is a bounce that never counts against you
Retry ladder a temporary failure deserves another try at the same address
Minutes to wait before each retry of a soft failure, in order. Leave empty to go straight to the backup address every time.
Pacing and resilience
A domain limit of 0 turns pacing off. Gmail and Outlook both throttle senders who arrive in bursts.
Unsubscribe Gmail and Yahoo require one-click unsubscribe from bulk senders
Turning the header off is only sensible for genuine one-to-one mail. These apply to messages this app sends through your own sender; GoHighLevel adds its own footer on its route.
Weekly digest
Reputation alerts providers suspend senders who cross these
Fallback message used only when the original body cannot be recovered
Merge tags: {{contact.first_name}} {{contact.last_name}} {{contact.name}} {{contact.email}}
Connect a sub-account
Standard GoHighLevel marketplace OAuth install
- Create the app in the GHL Marketplace (type: Private or Public, distribution: Sub-Account).
- Redirect URL — paste this into the app's OAuth settings:
… - Webhook URL — paste into the app's webhook settings and subscribe to the email/delivery events:
… - Per-location workflow hook (optional) — use this in a workflow's Custom Webhook action:
… - Put the Client ID / Secret / SSO key in
.env, restart, then hit install:
Required scopes
Tick exactly these in the marketplace app
contacts.readonlyread the lead and its custom fieldscontacts.writeswap mode, tags & notesconversations.readonlyfind the failed threadconversations.writecreate the retry conversationconversations/message.readonlyrecover the original bodyconversations/message.writesend the retry emaillocations.readonlysub-account namelocations/customFields.readonlylist secondary-email fields
How a rescue works
- 1GHL reports a bounce, failure or spam complaint for a lead.
- 2The app looks up that lead's backup address — custom field,
additionalEmails, or your saved list. - 3After your delay, the same message is re-sent through the sub-account's own email service.
- 4The lead is tagged
secondary-email-usedand a note is added, so your workflows can react.