Skip to content
Help Center
Submit a request Sign in

Configure agent messages and notifications

Messaging & notifications creates time-sensitive content for agent or community feeds. Feed visibility and the alert sent at creation are separate behaviors, so choose scope and timing with care.

Applies to: Supportbench Core. Location: Settings → Configuration → Messaging & Notifications. Managing these messages requires Administer messages and notifications.

Before you begin

  • Prepare the complete notice, intended feed audience and expiry before creating it. Creation alerts active agents across the account even when Team or Community limits feed visibility.
  • Choose Message for feed content or Notification for a dismissible notice. Coordinate timing; the creation alert is a real operational effect.

Configure and verify

  1. Open Settings → Configuration → Messaging & Notifications and choose New message.
  2. In Details, enter Name, choose Type and Priority, and set Expiry where needed. A blank new expiry means no expiry; clearing an existing expiry does not remove its saved value.
  3. In Audience, review Community message and Team. These control feed visibility; they do not narrow the creation alert to only that Team.
  4. In Content, write the affected service, required action, timing and person to contact. Review customer-facing wording if Community message is selected.
  5. Choose Save Changes when ready for the creation alert. Inspect the saved record’s Audit details and the intended feed result.
  6. Review the notice when the situation ends. Notifications leave this list after creation and clear for agents after viewing or dismissing; do not create duplicates just because the record is no longer listed.

Settings reference

Message details and audience

SettingWhat it controlsHow to choose
NameInternal name, up to 50 characters.Use a recognizable subject.
TypeMessage or Notification. Notifications leave this list after creation and clear after agents view or dismiss them.Choose persistent feed content or a dismissible notification according to the purpose.
PriorityImportance; blank uses Medium.Reserve high priority for messages requiring prompt attention.
ExpiryOptional end time. New blank means no expiry; clearing an existing value preserves its current expiry.Choose a definite expiry for temporary information and verify the saved value.
Community messageShows the message in the community feed; a saved Team value is retained.Review customer-facing wording before enabling.
TeamLimits feed visibility through the Team hierarchy.Choose the intended feed audience, but do not assume it limits creation alerts.
ContentFormatted message body.State the action, affected audience and timing clearly.
AuditOriginal creator and latest modification.Use it to trace changes to an active message.

Behavior to know

  • Creating any message alerts active agents across the account. Team and Community settings limit feed visibility, not creation-alert recipients.

Recommended use

  • Use notifications for actionable information, not routine repetition. Every creation can interrupt active agents outside the selected Team.
  • Keep a clear expiry for temporary content and verify the saved value when revising an existing notice.

Worked example

  1. For a scheduled equipment-maintenance window, write the affected service, start/end time and escalation contact in one concise notice.
  2. Choose the intended feed audience and a definite expiry, while accounting for the all-account creation alert.
  3. Create the notice at the agreed time and verify its feed visibility with an appropriate reader.
  4. After the maintenance ends, verify that the active message and expiry still describe the current situation.

Troubleshooting

ProblemWhat to check
The wrong agents received an alertCreation alerts active agents across the account. Team/Community feed settings do not narrow that alert.
A Notification disappeared from this listThat is the documented lifecycle; check the recipient experience before creating another notice.
Clearing Expiry did not remove itClearing an existing value preserves the previous expiry. Check the saved value and use the available controls to make the intended explicit change.
The intended reader cannot see the feed itemCheck Team hierarchy, Community message and the reader’s context, separately from creation alerts.
I cannot create or edit a noticeCheck Administer messages and notifications.
  • Organization → Configure agent roles and division access
  • Configuration → Configure workflows and automation

Was this article helpful?