Feature Snapshot
Summary:
Health Monitoring Alerts email the admins on your LeadConduit account when something in your lead flow looks unusual, so you hear about a problem within minutes or hours instead of days later. Each alert compares your flows, recipients and sources to their own recent history, so there are no thresholds for you to set. Eligible alerts begin October 28, 2026.
Key Benefits:
- Faster awareness - learn about failed deliveries, rejected leads and quiet flows without checking the product
- Smart thresholds - the system learns what is normal for your account, so alerts reflect what is unusual for you
- One-click investigation - every alert email links to your LeadConduit events, already filtered to the problem
- Low noise - emails are sent only for serious and critical alerts, plus a notice when a new source starts posting
Typical Use Cases:
- Catching a recipient or integration that has started failing or has lost its login
- Noticing that a flow that normally posts has gone quiet
- Spotting a source that is suddenly sending rejected leads, duplicates or leads without TrustedForm certificates
- Being told when a new or reactivated source starts posting to your account
How do Health Monitoring Alerts work?
LeadConduit builds a picture of what is normal for each of your flows, recipients and sources from their recent history (the last 7 days, or 12 weeks by day of the week for quiet-flow detection). When today is well outside that normal, and enough leads are involved for the change to matter, an alert is created. The alert is graded by severity, based on both how many leads are affected and what share of your leads that is. Serious and critical alerts are emailed to the admins on your account, once per problem. An alert resolves on its own when conditions return to normal.
There are nine alert types:
| Alert | What it tells you | When it fires |
|---|---|---|
| Recipient failures | A buyer or integration is failing on more of your leads than usual. | Failures are well above that recipient’s normal. A complete (100%) failure always fires once the recipient has at least 10 submissions that day, and its severity depends on how many leads it affects. |
| Recipient disconnected | An integration appears to be down or has lost its login. | A recipient’s failures are mostly connection or authentication errors. |
| Recipient skips | Leads are bypassing a recipient step more than usual. | Skips are well above normal. Often a sign that acceptance criteria changed. |
| No leads | A flow that normally posts has gone quiet. | Silence is unusual for that flow on that day of the week. Flows that don’t post on certain days are not flagged on those days. |
| Source rejects | A source’s leads are being rejected more than usual. | The rejection rate is well above that source’s normal. |
| Duplicate leads | A source is sending more duplicates than usual. | The duplicate rate is well above that source’s normal. |
| Missing TrustedForm certificate | Leads arrive without a TrustedForm certificate. | The share of leads with no certificate is well above normal. |
| TrustedForm failures | A certificate exists but fails TrustedForm checks. | The failure rate is well above normal. |
| New source started posting | A source you haven’t seen in 3 months is sending leads. | A source with no activity in 3 months posts 5 or more leads in a day. A notice, not an alert. |
Alerts need a minimum number of leads before they fire, and an alert is not repeated for the same problem.
Severity levels
| Severity | What it means | Emailed |
|---|---|---|
| Critical | Leads are being lost at scale, or have stopped entirely. | Yes |
| Serious | A significant share of your leads is affected. | Yes |
| Warning | Early or limited impact worth watching. | No |
| Info | A notice, not a problem (for example, a new source). | Yes |
Step-by-Step Instructions
No setup is required. Alerts start automatically for eligible accounts. When an alert email arrives:
- Open the alert email. The top line shows the severity and when we detected the problem.
- Read the headline, which compares today’s number with your typical number from the last 7 days.
- Check What’s affected for the account, flow, recipient or source, and the most common reason.
- Click Investigate to open your LeadConduit events, already filtered to the problem.
- Review the events and the flow’s History for recent changes, then fix the cause (for example, re-enter an expired credential or contact the source).
- Confirm that the alert resolves on its own once conditions return to normal.
Example alert email (made-up names):
SERIOUS ALERT
Detected Oct 29, 2026 at 10:14 AM CDT
38% of submissions to Acme CRM in Spring Promo Flow are failing
Most common failure reason: “Server error.” 190 of 500 submissions today · typical last 7 days: 4%
What’s affected
Account: Example Home Services · Flow: Spring Promo Flow · Recipient: Acme CRM · Reason: “Server error.”
This alert reflects the data as of Oct 29, 2026 at 10:12 AM CDT. Conditions may have changed since.
[ Investigate ]
This email was sent to admin@example.com. If you’d rather not receive these emails, you can unsubscribe.
Example new source notice:
A new source Spring Leads Co has started posting
Spring Leads Co posted its first leads (5 so far today) to your account Example Home Services. It had no activity in the previous three months, so it may be a new vendor or a reactivated one.
No action is needed unless you do not recognize the source. If you do not, review its leads and check with your team before it keeps posting.
[ View source leads ]
To unsubscribe:
Click the unsubscribe link at the bottom of any alert email. It applies to that admin only, so other admins keep receiving alerts.
Expected Result:
Admins on your account receive an email when a serious or critical problem is detected, with the information needed to investigate it in one click.
Validation & Monitoring (optional)
-
Confirm who receives alerts:
- Only admins on your LeadConduit account receive alert emails, and every admin gets the same alerts.
- Make sure the people who should hear about problems are admins on the account.
-
Where to monitor?:
- Use the Investigate link in each alert to open the matching events in LeadConduit.
- Check the flow’s History for edits near the time the problem started.
Best Practices
- Treat serious and critical alerts as same-day issues. They mean a significant share of your leads is affected.
- Use the Investigate link first, then check the flow’s History for recent changes to steps, mappings or acceptance criteria.
- Disable flows you have retired, so a “No leads” alert does not keep reminding you about a finished campaign.
- Check in with your sources when you get duplicate, rejection or TrustedForm alerts. The rejection reason is shown in each response the source receives, so it can be forwarded as is.
- Keep your admin list current so alerts reach the right people.
Troubleshooting
| Symptom / Error | Likely Cause | Resolution |
|---|---|---|
| I did not receive an alert email | The alert was a warning, which is not emailed | Review the alert type and severity table above. |
| I did not receive an alert email | You are not an admin on the account, or you unsubscribed | Ask an account admin to confirm your role. Unsubscribing applies per admin. |
| An alert fired for a small percentage | The percentage is far above your own normal | Alerts compare change against your history, not a universal number. |
| A recipient alert mentions login or authentication errors | The recipient is rejecting your credential | Re-enter the credential in the step settings. |
| A “No leads” alert fires for a flow I no longer use | The campaign ended, or the flow was a test | Disable the flow so the alert closes. |
| A duplicate or TrustedForm alert fires repeatedly | The source normally sends a high share of these | Talk to your customer success manager or AP support about the source. |
| The problem is fixed but the alert is still open | Alerts resolve when conditions return to normal, which may take a short time | Check again after new leads have posted. |
Frequently Asked Questions (FAQ)
Do I need to set anything up?
No. Thresholds are set by the system from your own history, and alerts start automatically for eligible accounts.
Who receives alert emails?
Only admins on your LeadConduit account. Every admin gets the same alerts, and the recipient list cannot be changed.
How many emails will I get for one problem?
One email per problem. If a warning escalates to serious or critical, you get an email at that point. A serious alert that becomes critical is not emailed again.
Why did I get an alert for a small percentage?
Because it is far above your own normal. Alerts measure change against your history, not a universal number.
Why didn’t I get an email for something I noticed?
Emails go out for serious and critical alerts. Smaller changes are warnings, which are not emailed.
Can I set my own thresholds or turn off one type of alert?
Not yet. Thresholds are set by the system, and today the control is the unsubscribe link. Talk to your customer success manager or AP support if an alert is not useful for your account.
How do I unsubscribe?
Click the unsubscribe link in any alert email. It applies to that admin only.
What should I do when I get an alert?
Click Investigate. It opens your LeadConduit events already filtered to the problem.
Glossary
| Term | Definition |
|---|---|
| Health Monitoring Alerts | Automatic emails to account admins when a flow, recipient or source behaves unusually compared with its own history. |
| Normal (baseline) | What is typical for a flow, recipient or source, based on its recent history. Alerts fire when today is well outside it. |
| Severity | How serious an alert is: critical, serious, warning or info. It reflects both how many leads are affected and what share of your leads that is. |
| Recipient | The buyer or integration a lead is delivered to. |
| Source | Where leads enter your flow, such as a vendor or form. |
| TrustedForm Certificate | Proof of consent captured on the page where a lead was submitted. |
| Investigate | The button in each alert that opens your LeadConduit events, filtered to the problem. |
| New source notice | A short notice, with no severity, that a source with no activity in 3 months started posting. |
Comments
0 comments
Please sign in to leave a comment.