1. Details pane
2. Details pane tabs
3. Details pane menu
4. Survey emails thumbnails
5. Search bar
6. Filter

• Details tab — Summarizes the most important information of your setting, such as:

  • Emails — Number of emails the distribution setting has. The minimum number is 1, as an Invitation email is required.

  • Priority — Priority number given to the setting. For more information, see Priority and Distribution rules.

  • Created — Date the distribution setting was created.

  • Last modified — Date the distribution setting was last modified.

  • Email distribution rule — Rule applicable to the setting. For more information, see Priority and Distribution rules.

• In Use tab — Programs where the Distribution setting is being used.

Edit

Edits the email on the Template editor.

Preview

Sends a preview email.

1. From Rules screen, click New Rule.

2. Enter a name for the rule.

3. Set the Priority and Distribution rules.

4. Configure the Invitation email.

5. Optionally, configure a Reminder email, Thank-you email, and the Expiration.

6. Click Save.

• Active — The distribution setting is always used.

• Inactive — The distribution setting is never used.

• Custom rule — The distribution setting is used based on the rule conditions. Click Add rule to build the setting rule. For details on how to build the rules, see Logic, rules, and conditions.

1. Create a distribution setting.

2. Choose the rule type: Active, Inactive, Custom rule.

3. Set the rule priority. The priority establishes the position that rule takes relative to the others if a survey matches multiple rules.

4. Click Save.

Edit rule

Modifies the rule.

Delete rule

Deletes the rule.

1. Select the Invitation email to use. The dropdown only lists the Distributions of type Invitation email.

   Note: To instead pick an email based on the rules on emails, set the Invitation email field to Based on email rule. This overrides what is set in the Rule field of the Email.

2. Define the "From" email address, as described below.

3. Select a domain. The dropdown lists the Email domains available for the instance.

4. Enter the return path to check the return path email, as described below. For information about return path configuration, see Custom return path configuration.

5. Enter the "From"sender's name, as described below.

6. Optionally, click Use the 'To' name. See details below.

7. Optionally, configure the Advanced settings, as described below.

8. Click Save.

• Local part — A local part from an existing email account or that clearly states that it does not accept replies (for example, no-reply, DoNotReply), and therefore emails bounce automatically if recipients respond.

  You can also include a variable to use in emails. For example, to include the Unit's email account in the address, the local part might look like this: $orion_unit_email_name$@...

  Important: When using a variable on the "From" email address local part, some manual configurations must be done outside Admin Suite to allow Auto-reply emails to be sent for each possible value of the field. If you do not have access to configure the sending of Auto-reply emails, contact your Medallia expert. If you can configure Auto-reply emails, you must manually create an Auto Reply configuration for each possible value for this field to ensure auto replies work and verify the hard-coded values are consistent with values retrieved from Experience Cloud.

• Domain part — Select a subdomain from the available dropdown options. By default, the only subdomain available is the default for your instance. To use custom domains, contact your Medallia expert as some email masking configuration is required to prevent errors.

  Warning: Unless the company is configured for Email masking, always use the domain of your instance. Changing the domain can cause reply-to emails not to be processed, and can erroneously cause emails to be treated as spam.

  For more information, see Email masking.

• Name — Enter the name directly in the field.

• Variable — An available variable to use in emails, such as the Unit's group name or brand. For example, if the Unit group has a field whose Field ID is ug_orion_brandname, set this field to $ug_orion_brandname$ to use it as a variable.

1. Select Enable Reminder.

2. Choose a Reminder type that defines when to send the Reminder email, which can be:

   • After a time delay — After a certain period of time has passed from the time when the Invitation email was sent (measured in days, hours, and minutes). A Reminder email is sent based on the Invitation email date (e_delivered date) and, if more than one Reminder email is set, the subsequent ones are also based on that date. When sending a Reminder email, Experience Cloud sets the time for the next Reminder email; you can change the time for a subsequent Reminder email as long as the previous one has not been delivered yet.
   • At a specific date and time — The exact date and time when the Reminder email is sent. The time zone is set in UTC based on your device settings, and it is the one used to send the reminder email.

     Note: When adding more than one reminder email, you cannot to add a new reminder with a date in the future if there's at least one reminder in the past. Experience Cloud treats reminder emails a single entity instead of considering each reminder separately.
3. Select the email to send as Reminder email. The dropdown menu only lists Distributions of Reminder emails type.

   Tip: To instead pick an email based on the rules on emails, set the Reminder email field to Based on email rule. This setting overrides what is set in the Rule field of the Email. Note that this only applicable for the first Reminder email to avoid potentially conflicting rules.

4. Optionally, click Add a reminder to configure an additional Reminder email.

5. Click Save.

1. Select Enable Thank-you email.

2. Select the email to use from Thank you email. Note that the dropdown only lists Distributions of Thank you emails type.

   Tip: To instead pick an email based on the rules on emails, set the Thank-you email field to Based on email rule. This setting overrides what is set in the Rule field of the email.

3. Click Save.

1. Choose an Expiration type, which defines when a Distribution setting expires:

   • After a time delay — After a certain period of time has passed, measured in days, hours and minutes. The minimum time delay is 1 day (24 hours) and cannot exceed 90 days (2160 hours).

     The expiration timestamp is set when the invitation is created. When the expiration setting for the invitation is a Time Delay, the expiration time is relative to the time when the record was created (e_creationdate). For invitation-based surveys, this is the time just before the record goes to Sampling. If later the record is updated, the expiration time is calculated relative to the existing e_expirationdate timestamp.

     Note that explicitly remapping the Invitation date and/or Expires on date (e_expirationdate) after record creation does not change the expiration date of the survey. For more information, see Extend survey expiration dates.

   • At a specific date and time — The exact date and time when the setting expires. Note that the time zone set in UTC based on your device settings, and it is the one used to expire the survey.

     Tip: Internally, Experience Cloud converts and stores time in PST time zone.

     When configuring the expiration from outside of the desired timezone, you need to manually calculate the time difference from your current time zone.

2. Click Save.

X-Medallia-Company-Name: <company-name>
X-Medallia-Company-URL-Name: <company-url-name>