Articles on: Workspace & integrations

Every notification your team can get

This is the full list of events your team can be notified about: 26 events in eight groups. On the Team members tab of Settings › Workspace › Notifications, you choose which of them a new team member starts with, and after that each team member can change their own settings. Your clients have a list of their own; see Every notification your clients can get.


Channels


Each event can arrive through three channels, and you switch it on or off separately for each of them. All channels switches an event on or off in all three at once.


Channel

Where it arrives

In-app

The bell in the top bar and the Notifications screen.

Browser

A desktop notification from the browser. The person has to allow notifications in their browser first.

Email

The person's email address.


Events


The events are grouped by the part of Zendo they come from. The descriptions are the ones Zendo shows next to each event.


Requests


Event

Zendo's description

New request created

When a new request is submitted.

Status changed

When a request moves to a different status.

Assigned to a request

When a request is assigned to you.

New request message

When a new message is sent in a request.

New request note

When a new internal note is added to a request.

Mentioned in a request

When someone mentions you in a request.

Intake Form sent in a request

When an Intake Form is sent into a request to be completed.

Request archived

When a request is archived.

Request restored

When an archived request is restored.


Chats


Chats are the conversations in Messages, where you talk to a client outside any request. See Message clients outside a request.


Event

Zendo's description

New chat message

When a new direct chat message is sent. Messages in requests are covered under Requests.

New chat note

When a new internal note is added to a chat.

Mentioned in a chat

When someone mentions you in a chat.


In requests as well as in chats, notes and mentions are separate events from messages. So if your team works a lot in internal notes, you can be notified about notes without being notified about every client message.


Quotes


Event

Zendo's description

New quote issued

When a new quote is issued.

Quote updated

When an issued quote is updated.

Quote approved or rejected

When a client approves or rejects a quote.

Quote paid

When a quote is paid.


Invoices


Event

Zendo's description

New invoice issued

When an invoice is issued, paid or voided, including invoices for quotes and subscription renewals.


This is the only invoice event, and it covers issued, paid and voided invoices together. You cannot be notified about paid invoices only.


Subscriptions


Event

Zendo's description

New subscription created

When a subscription starts for the first time.

Subscription payment failed

When a recurring subscription payment fails.

Subscription paused

When a subscription is paused.

Subscription resumed

When a paused subscription resumes.

Subscription canceled

When a subscription is canceled and will not renew.


Orders


Event

Zendo's description

New order placed

When a new order is placed through the Front Desk.


Forms


Event

Zendo's description

New form submission

When someone submits an Intake Form.


Workspace


Event

Zendo's description

Team member joined

When an invited team member activates their account.

Client joined

When an invited client activates their account.


Defaults apply to the whole team


Settings › Workspace › Notifications has no settings for a single person or a single role. Each person changes their own notifications in their own settings. A team member who never does this keeps your defaults; one who does replaces them with their own choices, and Zendo does not tell you about it.


Notifications do not change requests


A notification only tells a person that something happened. To make something happen to a request — post a message, move it to another status or send a form — you need an automation, which is set up on the request type. See Automate a request type.



Updated on: 09/11/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!