e-satisfaction

Statuses & settings

Settings is where you shape the workflow your team uses to track alerts. Statuses are the colored labels you move an issue through — from the moment it's raised to the moment it's resolved — and this is where you define them so they fit the way your team actually works.

Settings are scoped to the workspace selected at the top of the sidebar, so each workspace can have a workflow that suits it.

What statuses are

A status is a label an issue carries while your team works it — for example New → In progress → Closed — and each one has its own color so it stands out in a list. Statuses power the status dropdown and the status filter on the Issues queue, giving everyone a shared, at-a-glance sense of where each issue sits.

Two kinds of status

System statuses

System statuses are built in and shared across every workspace and organization. You'll see them marked with a Systemic lock. You can't rename, recolor or delete them — but they're always available to use, so every team starts from a consistent baseline.

Workspace statuses

Workspace statuses are the custom statuses you create for a workspace. Each has a title, an optional description, and a color, and they're fully editable. Use them to mirror your own process — for example Awaiting customer, Escalated to ops or Won back.

Managing your workspace statuses

The Settings page shows the system statuses for reference (read-only) alongside your workspace's own statuses, where you do all the editing.

Create a status

Add a new status with a title, an optional description, and a color so it stands out in your lists.

Edit as your process evolves

Rename, recolor or update any workspace status's description at any time as your workflow changes.

Delete and migrate

Remove a status you no longer need — choosing where its issues should go first, so none are ever left without one.

Once your statuses are set, your team uses them in Issues & triage to track and resolve issues, and every change is recorded in each issue's status history.

Deleting a status safely

Issues may already be sitting on a status, so deleting one is handled carefully. When you delete a status, you choose a destination status to move its issues to, then type DELETE to confirm. Every affected issue is migrated to the destination first, and only then is the status removed — so your workflow stays intact and no issue is ever left stranded.

Deletion moves every affected issue

You can't simply remove a status that's in use. Pick a destination status and type DELETE to confirm — Alerts migrates every issue on the old status to the destination before deleting it.

Managing statuses across your organization

Statuses are defined per workspace, but organization admins can shape them everywhere from one place.

Global Settings Admin only

Organization admins get a Global Settings page to manage alert statuses across every workspace at once — ideal when you want a consistent set of labels rolled out organization-wide.

To make that easy, identical statuses (same title, description and color) are grouped together, with the list of workspaces using each:

  • Editing a group updates that status in every workspace that has it, so a rename or recolor lands everywhere in one go.
  • Saving a status to a workspace that doesn't have it yet creates it there — so an admin can roll a brand-new status out across all workspaces from a single screen.

It's the fastest way to spot where teams have defined the same status and keep your organization's workflows consistent.

How it all fits together

Putting the pieces in plain terms:

  • Statuses are defined per workspace, so each team can tailor its workflow.
  • System statuses are available everywhere, giving every workspace a shared starting point.
  • Organization admins can manage workspace statuses across all workspaces at once from Global Settings.

Who can edit what

  • Workspace statuses — anyone with access to that workspace's Settings can create, edit and delete them.
  • Global Settings — organization admins only. Admin only

For more on roles and who has access to a workspace, see Workspaces & users.