Get an alert when a number moves
Alerts on history is an agent that checks, every morning, the figures MarqIQ keeps for each connected tool against six rules, and sends one message on a day a rule fires — with what moved, the figures it rests on, the tool, the cause where the history can name it, and a link to the evidence. On a quiet day it sends nothing. This article sets it up and states every rule with its threshold, so you know what will and will not wake you. For the whole week in one message, read Get the Monday Brief by email.
Before you start
The rules read two things MarqIQ keeps for twelve months: the change log of your synced records (stage, lifecycle stage, owner, amount, close date) and each tool’s headline figures once a day. Both start the day MarqIQ began keeping them for a tool, and a rule that needs more history than that says so, with the first day it can be judged.
Note
One alerts agent covers every connected tool: each rule is judged per tool, and a rule a tool cannot feed — the MQL rule on a tool with no lifecycle ladder, the deal rules on a tool that syncs no deals — is left out for that tool and the report says which.
Set it up
Open Agents in the left-hand menu.
Click New agent.
Type a name, and pick Alerts on history under Kind.
Pick the time of day.
The cadence is fixed: the alerts run every day, at the time you choose on the workspace clock. The default is 06:30.
Tick the people who receive it, by email, in-app, or both.
Click Set it up.
Tip
Click Preview on the new agent to see what today’s check would say. It runs the rules and shows the report here without sending it; a quiet day shows that nothing fired, and why each rule held.
The six rules
| Rule | Fires when | Stays quiet when |
|---|---|---|
| New MQLs down a third week | The week’s new MQLs are at most 75% of the week before, three weeks in a row | The oldest of the three weeks had fewer than 20 new MQLs, or the change log is younger than 21 days |
| People with no owner up by half | The count is at least 1.5 times what it was a week ago, and at least 50 more | Fewer than 100 people were held on either day |
| Open pipeline down by 30% or more | Open pipeline in one currency is at most 70% of a week ago | Fewer than 10 priced open deals on either day |
| No deal won for two weeks | Two whole weeks with no deal won | The median of the eight weeks before is under 3 wins |
| Duplicate groups up by half | The count is at least 1.5 times what it was a week ago, and at least 20 more | Fewer than 100 records were held, or the counts are less than 8 days apart |
| Sync failing | Three failed syncs in a row, or no completed sync in 48 hours | The sync completed |
A "week ago" compares two kept days at least five days apart. The floors are printed when they hold a rule back.
- A fall that is really a stopped sync is named as one: while a tool’s sync is stopped, every down rule is held and Sync failing fires instead.
- An alert fires once per window. A condition that holds fires again when its window moves — a week rule when the week does — so a daily check never repeats yesterday’s message.
- Where the history can name the cause, the alert does: the first-touch sources the missing MQLs came from, who stopped assigning owners, the deals that left the open pipeline, the sync’s own error.
Where it arrives
- By email, from a no-reply address, with the subject Alerts — your workspace, date, on a day something fired. Every one carries a one-click unsubscribe link.
- In Agents › Inbox, counted in the notification bell.
- In the Monday Brief, under Risks: the brief repeats the week’s alerts from the reports this agent kept.
If it did not work
Nothing has arrived in a week
Why: Most days nothing fires, by design; the agent keeps no report and sends nothing on a quiet day. A run can also be held because scheduled runs are not switched on for this server yet.
Fix: Open the agent and read Last runs. A row per day with nothing fired is the agent working. No rows at all means it has not run: click Preview to check today, and tell support that the schedule did not fire.
Every rule says the history is too young
Why: The MQL rule needs three weeks of change log and the won rule ten weeks; the figures start the day MarqIQ began keeping them for the tool.
Fix: Nothing to do. Each line names the first day the rule can be judged.
A fall you can see in your CRM did not fire
Why: It did not cross the threshold, or it sits under a floor: a drop from 12 to 8 MQLs is under the floor of 20 and is said so, not alerted.
Fix: Read the line under What this rests on in the next report that fires, or click Preview: every rule that held says which floor or ratio held it.
The email was skipped and names a setting
Why: Agent emails need the sending address and the unsubscribe secret set on the server; until then no agent email is sent, and the in-app report still arrives.
Fix: Read it in Agents › Inbox and tell support the run id.
Next steps
Related articles
Was this article helpful?