Skip to Content
Notifications & Alerts

Notifications & Alerts

Audience: Marketers and admins

There are two audiences for notifications, and they live in different places:

  • Submitters receive automatic, co-branded status emails when their submission is received, approved, or rejected. These are configured under Settings > Email Notifications.
  • Your team receives alerts when something happens that needs attention: a new submission, an approval, a rejection, or a reward sent or failed. These are configured under Settings > Notifications, which is split into two tabs: Integrations and Team Emails.

The three submitter-facing emails, the merge variables you can use, and how rejection reasons are inserted.

Submission status emails

Wire up Slack, Microsoft Teams, Discord, Zapier, or a custom webhook. Test the connection, view delivery logs, and handle auto-disabled integrations.

Notification integrations

Submitter emails at a glance

Three types, all toggleable:

EmailTriggerTiming
Submission ReceivedSubmitter submits a claim5–10 minute delay
Submission ApprovedA reviewer approvesImmediate
Submission RejectedA reviewer rejectsImmediate

Emails are sent from {Company Name} via HighAdvocacy <[email protected]>, are co-branded with your logo in the header and “Powered by HighAdvocacy” in the footer, and accept merge variables like {{user_name}}, {{company_name}}, {{platform_name}}, {{reward_name}}, and {{reward_value}}. You can preview emails with sample data and send a test email to yourself before going live. Existing campaigns have these notifications auto-enabled.

Team alerts at a glance

Five events are available across integrations and team emails:

  • submission.received
  • submission.verified
  • submission.rejected
  • reward.sent
  • reward.failed

All five are pre-selected when you create a new integration or set up team emails. You opt out of events you do not want, rather than opting in.

Integrations route alerts to Slack, Microsoft Teams, Discord, Zapier or Make, or a custom HTTPS endpoint. Each integration is scoped to All campaigns (dynamic, includes future campaigns automatically) or to a specific set of campaigns (newly created campaigns are auto-added to the selection, with a “Recently added” indicator so you can remove them if unwanted). Up to 10 integrations per account.

Team Emails sends the same five events to a list of email addresses (up to 10). One event configuration applies to all recipients. A master toggle pauses all team email alerts without removing the recipient list.

What happens when an integration fails

After 5 consecutive delivery failures, the integration auto-disables. The account Owner receives an email explaining what happened and pointing back to Settings to re-enable. The detail page shows a warning banner and a Re-enable action. The failure counter resets to 0 when:

  • Any delivery succeeds.
  • You manually re-enable the integration.
  • You edit the webhook URL.

Test events run from the configuration form (or from the integration detail page) do not write to delivery logs and do not affect the failure counter.

Permissions

Editing notification settings (including end-user emails, integrations, and team emails) is allowed for Owner and Admin. Members cannot edit these settings. See Roles and permissions.

Last updated on
Reward versioningSubmission status emails