Skip to main content
Use Settings → Notifications to save your delivery preferences for operational alerts. These settings are separate from the customer email channel and from Evelin’s tool integrations.

Choose your delivery preferences

  1. Open Settings → Notifications.
  2. Find the relevant category: Conversations, SLA, AI, Billing, Team, Knowledge, or CSAT.
  3. Review its Email, Slack, and Push switches.
  4. Select Save preferences, then reopen the page to check the saved choices.
The category switches are personal to your account. The In-app column is read-only: changing another delivery channel does not remove notifications already recorded in Protodesk. A category label does not guarantee that every event described beside it currently generates an alert.

Understand delivery availability

  • In-app: use the notification bell to review alerts that Protodesk has recorded for you. An alert must be generated and addressed to you before it can appear.
  • Push: requires a supported app/device registered for your account, notification permission on that device, and an active delivery service. Enabling Push here alone does not register a browser or phone.
  • Email and Slack: the page exposes preference controls, but saving them is not confirmation that operational alerts are being delivered through those channels. Confirm availability and a successful delivery for your workspace before relying on them.
  • Daily digest: the switch and delivery time can be saved, but a recurring digest is not a verified delivery capability of the current release. Do not use it as your only queue-monitoring process.

Quiet hours

Enable Quiet hours, set From and Until, and select Save preferences. Check your timezone in Settings → Account; it is separate from the workspace’s business-hours timezone. The supported push delivery path defers notifications during the quiet-hours window. In-app records remain available. The page also mentions email suppression, but do not assume this controls every email sent by Protodesk or blocks security and account messages.

Slack integration is workspace-wide

The Slack integration section stores a workspace destination, unlike your personal category switches. Ask an owner or admin to manage it. A saved webhook is not proof of successful alert delivery and does not connect Slack as an Evelin tool. Treat webhook URLs as credentials. Never include one in a Help Center article, customer reply, screenshot, or support report. Confirm operational Slack alert support before adding a destination.

If an alert is missing

Check the correct workspace and account, look in the notification bell, and confirm that the event was expected to notify you. For push, also check device permissions, sign-in, category preference, and quiet hours. Record the event time, timezone, category, and affected conversation link for support; omit credentials and unnecessary customer content. See email preferences for account-email choices and SLA policies for warning and breach limitations.