Notifications
Configure email and in-app alerts for new requests and conversation activity.
Notifications keep your team aware of new customer activity without leaving the inbox open all day. SupportPage can alert you when requests arrive and when conversations update.
What triggers notifications
Depending on your settings and plan, alerts may fire for:
| Event | Typical default |
|---|---|
| New request | Email to account owner or configured address |
| Customer reply | Email when the customer responds by email or form |
| Status changes | Usually off by default — enable if your workflow needs it |
Exact toggles live in Settings → Notifications (or Account → Notifications) in the dashboard. Labels may vary slightly by release.
Email notifications
New request emails
When a customer submits your form, SupportPage sends a summary to the notification address on file. The email usually includes:
- Subject and customer email
- Snippet of the message
- Link to open ticket detail in the dashboard
Verify the notification address is a shared team inbox or alias if multiple people triage support.
Reply and update emails
When a customer replies to a thread, your team can receive an alert with a dashboard link. This complements — does not replace — reading replies inside ticket detail.
High-volume pages can generate many emails. Tune notification settings before pointing a busy production form at a personal inbox.
In-app indicators
The dashboard may show:
- Unread badges on the inbox or individual requests
- Banners for billing or publishing issues that affect notifications indirectly
Mark a request as read by opening ticket detail. Unread state is per-account, not per teammate, when sharing one login.
Customer-facing emails (for context)
Notifications for your team are separate from emails customers receive:
- Submission confirmation with status link
- Replies when you respond from the dashboard
- Optional status-change messages
You do not configure customer copy in the notifications panel — that is handled by the product's transactional email templates.
Reducing noise
| Goal | Suggestion |
|---|---|
| One digest instead of per-ticket | Route alerts to a tool that batches email, or filter with inbox rules |
| Only urgent pages | Disable notifications on low-traffic test pages |
| On-call rotation | Use a rotating alias as the notification address |
Troubleshooting
| Problem | What to check |
|---|---|
| No new-request emails | Notification address in settings; spam folder; page is published |
| Alerts stopped after billing issue | Subscription status |
| Duplicate emails | Multiple notification addresses configured; forwarding rules |
| Customer says they got nothing | Tracking status — different from operator notifications |