Daily workflow

Tags, saved replies, and settings

Keep the support queue readable with workspace tags, reusable replies, inbox-scoped guidance, and a clear settings overview for managers.

Browse documentation
5 minDaily workflow

Create tags

Tags are organization-wide labels. Create them from Tags, choose one of the preset colors, and apply them from a ticket's side panel.

Common tag patterns

  • Product areas such as billing, onboarding, deliverability, or API.
  • Operational states such as waiting-on-customer, needs-engineering, or refund-review.
  • Customer tiers such as VIP, trial, or enterprise.

Start with a small tag set that agents can remember while replying. Keep tags that change priority, ownership, reporting, or the next action on a ticket, and remove labels that no longer guide the work.

Save reusable replies

Saved replies live in Library. Give each reply a title, body, and optional inbox scope. Workspace-wide replies appear for every inbox, while inbox-scoped replies are meant for a specific queue.

Current behavior

The library creates and lists saved replies. The ticket screen links back to the library, but inserting a saved reply directly into the composer is not wired in the current UI.

Write saved replies as reusable starting points rather than final scripts. They work best for repeatable setup steps, billing explanations, and security answers, with room for the agent to add the customer's domain, ticket context, and the exact thing they already tried.

Use settings for workspace context

Workspace
See name, slug, plan, subscription state, creation date, and your current role.
Session
See the signed-in Google identity, switch workspaces, or sign out.
Billing state
Trial, active, past due, canceled, and paused states are shown when present on the workspace.

Settings gives managers a quick view of the workspace name, their own role, the plan state, and connected inbox setup. After changing workspace or inbox settings, send a test ticket through the queue to confirm replies still route through Resend.