Email Notification

Enable and set up the email recipients to receive notification events from Suger service

Overview

Email notifications let you configure per-scope routing rules so that each notification event type has its own enable/disable toggle, recipient lists (TO, CC, BCC), and optional custom template. When an event from Suger matches a scope that is switched on in your saved configuration, and Enable Email Notification is on, an email is automatically sent to the designated recipients.

Configuration

Enable Email Notification

Go to the settings page and open the Notification tab. Toggle the Enable Email Notification switch to activate email routing.

While the switch is off, Suger sends none of the emails in the catalog. That includes the manual Notify Contacts action on private offers and the ready-to-accept email to an offer’s contacts. The page then shows the warning “Email Notification is off: every scope below is suppressed, including the manual Notify Contacts action on private offers.”

Email Routing Catalog

The Email Configuration catalog lists every notification scope, organized by category (Offers, Entitlements, Co-Sell, Partners, and so on). It is shown whether or not Enable Email Notification is on. Each category can be expanded or collapsed.

Every scope row provides the following columns:

Click Save after making changes to persist your configuration.

Email an offer’s contacts

Suger reaches the contacts on an offer only through the Offer Notification Contacts rule on a row. Add the rule to each offer email your buyer’s contacts should receive: Pending Acceptance, Accept Offer, Resale authorization active, Notify offer contacts, or Accepted but unpurchased offers digest.

1. Go to the settings page and open the Notification tab.
2. Find the row in the catalog.
3. In the row’s TO Recipients column, click Add roles, then under Suger select Offer Notification Contacts.
4. Switch the row on.
5. Click Save.

Everyone on a row receives the same email. The offer’s contacts and any other TO or CC recipients you add to that row appear together on one message.

Additional Settings

Below the catalog, one additional setting is available:

• Enable Expire Soon Offer Workflow Notification — Enables workflow notifications for offers that are about to expire. When enabled, you can configure the number of days before expiration to trigger the notification (default: 7 days).

The former Disable Email Notification on Offer Ready setting has been removed. To stop the ready-to-accept or resale-authorization emails, switch off the Pending Acceptance (PENDING_ACCEPTANCE.OFFER) or Resale authorization active (ACTIVE.OFFER) row in the catalog.

Update History

The Update History table at the bottom of the Notification tab shows an audit log of configuration changes. You can search across all fields and click a row’s detail icon to inspect the full JSON payload of the change.

Custom Templates

Custom email templates allow you to personalize your notification emails with dynamic content and professional layouts. You can create templates that automatically incorporate data from your notification events, making your emails more informative and engaging.

Any scope can have a custom email template assigned to it, replacing the default content. Templates support dynamic variables (for example, buyer name, deal name, and product).

Create New Template

In the routing catalog, find the Template column for any scope row and select + New Template from the dropdown. The template creation dialog opens, and once saved the new template is automatically assigned to that scope.

In the template creation dialog:

• Enter a descriptive name for your template
• Select the evaluator type (currently, only Golang Template is supported)
• Use the email builder to design your template
• Click Create to save your template

Use Email Builder

The email builder provides a comprehensive set of tools to create professional-looking emails:

• Columns: It allows your users to add columns to your design in order to have a better design arrangement.
• Button: Add any type of button in your email. You can change colors and styles.
• Divider: It gives your users appropriate spacing at any point they want in their design.
• Heading: Add headings (from level 1-6) to the design.
• Text: Text is a built-in tool so users can add text to their designs.
• Image: To make your emails attractive, you can add images using this tool.
• Social: It is a built-in tool that lets users add their social media icons to your design.
• Menu: Menu is a built-in tool used to create navigation menus.
• HTML: This tool will give your users room to add custom HTML to the design.

Working with Dynamic Data

Using Single Variables

1. Select a notification event type to make its variables available in the builder. By default, use the BaseNotificationEvent.

2. In the text or heading tool, click the Merge Tags button and select the variable you want to insert

   

Looping Over Lists

To display multiple items from a list:

1. Add a Columns tool to your template
2. Click the tag symbol on the Columns tool

   

3. Select the list you want to iterate over

   

4. For complex objects in the list:
   • All variables from the list items become available within the Columns block
   • Use them in text tools just like single variables

   

5. For simple values (strings or numbers):
   • Use the this merge tag to access the current item within the Columns block

   

Assign Templates to Notification Scopes

Templates are assigned directly in the Email Routing Catalog:

1. Go to the settings page and open the Notification tab
2. Find the scope you want to customize in the routing catalog
3. In the Template column, select an existing template from the dropdown or choose + New Template to create one
4. When a template is assigned, use the inline icons to:
   • Edit the template in the email builder
   • View details as a JSON payload
   • Delete the template (removes it from all scopes that reference it)
5. Click Save to persist your changes

Duplicate a template

To start a new template from an existing one, open it for editing, for example with the Edit template icon next to a row’s template, and click Duplicate in the editor’s header.

• Suger saves what is on screen, including edits you haven’t saved, as a new active template named <name>_copy. Further copies are named <name>_copy_2, <name>_copy_3, and so on, shortened if needed to fit the 50-character name limit.
• The editor then switches to the copy, so your next Save updates the copy. The original template is left unchanged.
• The copy isn’t assigned to any row. Pick it from a row’s Template dropdown to use it.

Test Custom Templates

Before using a template in production, you can test it to ensure it works as expected:

1. In the routing catalog, find the scope row with the template you want to test
2. Click the Test button in the Diagnostics column
3. In the test dialog, provide the following information:
   • To Email: The recipient email address for the test
   • CC Emails: Optional comma-separated list of email addresses to CC
   • One event json data: Choose (and modify as you want) between:

• Mock JSON data files
• Last recorded events for your organization

You can also edit the template directly from the test dialog by clicking the Edit Template button, which will open the email builder.

Test a scope’s default template

You no longer need a custom template to use Test. If a scope has no template assigned, the test sends that scope’s default template — the same content Suger would send in production — so you can check the wording and the event data a scope produces before deciding whether it needs customizing at all.

The partner-facing scopes (Partnership, Co-Sell, Commission, Certificate and Journey) render the production partners template, so what you receive is what your partners receive.

One exception: Product scope notifications are plain-text emails with no default template behind them. Test is disabled on that row, with the tooltip “This scope’s notifications are plain-text emails — assign a custom template to test.” Assign a custom template to that scope and the button becomes available.

Notification Scope Reference

Each notification scope has its own trigger, its own TO/CC/BCC recipient lists, and an optional custom template that replaces the default content. Use the tables below to understand when each scope fires and what its default email contains.

Keep in mind:

• No row is always on — Co-sell shared, Co-sell closed won, Co-sell closed lost, Commission terms updated, and the commission rows can all be switched off like any other row.

• Notices without a row — these have no row, so they can’t be switched off one by one:

  • The email to a partner that a co-sell was registered on its behalf
  • The email to a partner removed from a deal registration
  • Certificate expiry and renewal reminders sent to learners

  Enable Email Notification still applies to them.

• A row takes effect only once it is saved — see When an email is sent.

Offers

Entitlements

All four renewal scopes are disabled unless you enable the scope and configure recipients. For the three that AWS Marketplace reports (RENEW.ENTITLEMENT, AUTO_RENEW_OFF.ENTITLEMENT, and RENEW_SOON.ENTITLEMENT), repeated delivery of the same lifecycle event is deduplicated for one day. The Auto Renew value shown in the Console, Salesforce, and HubSpot is the buyer’s live accepted-agreement setting; it is not the separate “Renewal Offer” marker used when an offer replaces an existing agreement.

Co-Sell

These scopes cover activity on co-sell referrals shared via cloud marketplace co-sell programs (AWS ACE, GCP, etc.).

Every row except Inbound Referral covers referrals you share with a cloud partner. For a referral a cloud partner shares with you, Inbound Referral is the only email: accepting it (yourself or with Auto-Accept), declining it, and later updates to it send none.

Product

Partners

These scopes cover activity in Suger’s Partner Relationship Management (PRM) module, including partnership invitations, Suger co-sells, and commission lifecycle events.

Co-sell and commission emails thread into a single conversation per deal. Suger sends each one from the first of these that applies:

1. The Gmail of the signed-in user whose action triggered it, if they have connected Gmail as a user integration
2. The organization sender chosen in the row’s Sender column: your organization’s Gmail or verified custom domain
3. Suger’s default sender

Send co-sell emails from your Gmail has the full rules, the exceptions, and a diagram.

The sender decides the subject:

• Thread subject. Co-sell: [Deal Name] on the share email and Re: Co-sell: [Deal Name] on every email after it, with the event named in the email body.
  • Used when the email comes from Suger’s default sender or from the Gmail of the person who triggered it.
  • A copy that carries a recipient’s personal one-click link always comes from Suger’s default sender, so it uses this subject.
• Event-specific subject. Used when the email comes from your organization sender, which can’t carry the threading headers.

Both subjects are listed below. When you write inbox rules, use the one that matches how the email is sent.

Auto-Share Report

Headless Entitlements

Revenue

Suger Co-Sell

There is no separate row for the people on a Suger co-sell. The share email they receive is governed by the Co-sell shared row (CREATE.SUGERCOSELL) in Partners.

Unpurchased Offers

Usage Metering Alerts