Route actionable alerts
Alerts notify a team when grouped issue evidence crosses an actionable boundary. Dozenfold alerts on issue state and priority changes instead of sending a message for every captured event.
Connect Slack channels
Open Settings → Alerts and add a Slack channel with its incoming webhook and a channel name. Add more channels when different teams own different problems. Save, then use the channel’s test action to confirm delivery before relying on it for triage. Slack alerts are available on every plan.
Connect Telegram chats
Open Settings → Alerts and choose Connect Telegram. Dozenfold shows two links:
- Open in Telegram connects your private chat with the Dozenfold bot.
- Add to a group lets you pick a group; the bot joins it and that group gets the alerts.
Tap Start in Telegram. The bot confirms in the chat, and the chat appears under Telegram chats after you choose I tapped Start. Each link works once, for 15 minutes. Use Send test alert to confirm delivery. Telegram messages carry the same content as Slack alerts.
To stop alerts to a chat, choose Disconnect, or remove the bot from the group: Dozenfold disconnects that chat on its own. A store can connect up to 10 Telegram chats.
Pick the rules for each channel
Each Slack channel and Telegram chat receives only the alerts you pick for it:
| Rule | Sends an alert when |
|---|---|
| Checkout-stage errors | A checkout-stage issue is new, regresses, or recovers. |
| Cart API failures | A cart API failure is new, regresses, or recovers. |
| New issues | Any other issue is new. |
| Issue regressions | Any other resolved issue comes back. |
| Issue spikes | An open issue’s rate rises sharply. |
| Core Web Vital degradation | A Core Web Vital gets worse. |
Recovery of a new or regressed issue goes to channels with either of those two rules. A new Slack channel starts with checkout and cart alerts; a new Telegram chat starts with every rule. One alert can go to several channels and chats; each gets it once.
Read an alert
An alert names the issue and links back to it, so commercial context, affected sessions, and developer evidence stay in one investigation. When they are already computed, the message also shows the issue’s estimated revenue impact (on plans with revenue impact) and its likely owner: theme, Shopify, a third-party script, an extension, or unknown. Alerts are not held back waiting for either value. Treat the message as an entry point, not as the complete diagnosis.
Keep notifications useful
Use Quiet hours to pause delivery during a recurring local time window; held alerts stay visible in Recent alert activity, which also shows the latest delivery attempts. Review noisy issue fingerprints in Dozenfold instead of muting an entire evidence family. Resolution and ignore state remain issue decisions, not Slack or Telegram reactions.
Alerts are delivered to Slack and Telegram; email delivery is not offered for alerts.
Weekly report by email
Every Monday from 07:00 UTC, the store’s owners get one email summarising the last seven days:
- sessions and sessions with errors
- the three open problems with the highest estimated revenue impact, each linked to its issue
- LCP, INP and CLS at p75
- short cards for anything not set up yet: release markers, error-session replay, Slack or Telegram alerts, or source maps
On Shopify it goes to the shop’s email address; on a custom site, to the workspace owners. It is on by default. Turn it off under Settings → Alerts, or with the one-click unsubscribe link in any report. Each store gets it once a week.