Skip to main content

Workspace Settings: Labels, Statuses & Team Organization

Customize your Revo workspace with Labels and Statuses to organize issues, meetings, and feedback. Create custom tags and workflow stages in team settings to classify work, improve searchability, and keep your team aligned on priorities.

Updated over a month ago

Overview

Workspace Settings give you full control over how your team organizes and tracks work in Revo. By defining Labels and Statuses, you create a shared vocabulary that helps everyone filter, prioritize, and understand progress at a glance.

Why this matters for email:
When drafting status updates or customer replies, Revo references your Labels and Statuses to provide accurate context. If a customer asks about a bug, Revo can say "The login issue (labeled 'P0-Customer') moved to 'In QA' this morning and ships Friday" instead of generic status language.


Labels: Organizing Your Work

What are Labels?

Labels are custom tags you apply to Issues, Meetings, User Feedback, Contexts, Insights and Workflows to categorize and group related work. They make it simple to filter, search, and prioritize information across your workspace.

Why Use Labels?

Organize Clearly:
Categorize tickets, meetings, feedback, workflows, insights or contexts by theme, priority, or department.

Improve Searchability:
Quickly find all items tagged "Mobile Bugs" or "Customer Requests" with a single filter.

Prioritize Effectively:
Highlight urgent issues or key customer pain points with labels like "P0" or "Revenue Impact."

Collaborate Better:
Consistent labeling keeps your team aligned and ensures nothing slips through the cracks.

Email Intelligence:
When customers email about a specific topic, Revo can filter to only labeled issues or feedback for hyper-relevant context in draft responses.


How to Create Labels

  1. Click your Team Name at the top-left to open the main menu

  2. Select Team Settings from the dropdown

  3. Click Labels in the left sidebar

  4. Click + New Label button

  5. Add a name, description, choose a color and select from the list to which item you want to apply it : Issues, Feedback, Meetings, Contexts, Insights or Workflows

You can create as many labels as needed and apply them consistently across your workspace.

You can also add a list of labels by uploading a csv file.


Label Best Practices

Use clear, descriptive names:
✅ Good: "Mobile Bugs," "Onboarding Requests," "High Priority"
❌ Bad: "Stuff," "Misc," "TBD"

Keep your list organized:
Review and clean your label library periodically. Archive unused labels to prevent clutter.

Encourage team consistency:
Set guidelines for when to use specific labels so everyone tags work the same way.

Combine with @ mentions:
In Chat, you can query labeled work: "@issues with label: P0, what's blocking them?" or "Show me all @meetings labeled Customer Interview from last month."


Statuses: Tracking Progress

What are Statuses?

Statuses represent the current stage of completion for an Issue. They provide clear visibility into what's actively being worked on, what's blocked, and what's completed.

Why Use Statuses?

Track Progress:
Instantly see where each issue stands in the workflow.

Improve Transparency:
Keep everyone aligned on what's in progress, blocked, or shipped.

Support Sprint Workflows:
Align statuses with your team's sprint or agile process (e.g., Backlog → Todo → In Progress → Done).

Customize for Your Process:
Define statuses that reflect how your team actually works, not generic templates.

Email Accuracy:
When drafting updates, Revo cites exact statuses. It won't say "almost done" if the issue is still in "Blocked" status


Common Status Examples

To Do: Work hasn't started yet
In Progress: Actively being worked on
In QA: Under review or testing
Blocked: Paused due to dependency or blocker
Done: Completed and shipped

You can create custom statuses that match your team's workflow (e.g., "Design Review," "Awaiting Approval," "Deployed").


How to Create Statuses

  1. Click your Team Name at the top-left to open the main menu

  2. Select Team Settings from the dropdown

  3. Click Statuses in the left sidebar

  4. Revo organizes statuses into six main categories: Backlog, Unstarted, Started, Completed, Canceled, and Triage. Each category includes default statuses that you can edit, delete, or expand by adding new statuses to match your team's specific workflow.

Statuses can be updated or refined anytime as your process evolves, ensuring they stay relevant to your team's workflow.


How Labels & Statuses Power Email Drafts

Real-World Example

Customer email: "What's the status of the mobile app bug I reported last week?"

Revo checks:

  • Issues labeled "Mobile Bugs" and "Customer-Acme"

  • Current status of matching issues

  • Related meeting notes or Slack discussions

Revo drafts:
"The mobile login bug you reported (Issue MOB-234, labeled 'P0-Customer') moved to 'In QA' yesterday. Our QA team is running final tests today, and we're on track to deploy the fix Friday morning. I'll send you a confirmation email as soon as it's live."

Context used:

  • Label filters (Mobile Bugs + Customer-Acme)

  • Status tracking (In QA)

  • Cycle timeline (Friday deployment)

Without labels/statuses: Generic "We're working on it" response
With labels/statuses: Specific, cited, timeline-accurate draft


Best Practices for Workspace Organization

Use Labels for Cross-Functional Visibility

Create labels that span departments:

  • "Customer-Reported" (helps CS track external bugs)

  • "Revenue-Impact" (helps sales understand priority)

  • "Design-Dependent" (helps PMs track design bottlenecks)

When these teams email asking for updates, Revo can filter by their relevant labels for accurate context.

Align Statuses with Your Sprint Process

If you run two-week sprints, ensure statuses match your team's actual workflow. Don't use "Code Review" if your team doesn't have that step. Keep it real.

Use Labels in Workflows

Set up automated workflows that trigger based on labels:

  • When an issue gets labeled "P0," post to #engineering Slack immediately

  • When feedback gets labeled "Feature Request," add it to your roadmap backlog

  • When a meeting gets labeled "Customer Interview," auto-generate a summary for the sales team


Frequently Asked Questions

Can I apply multiple labels to one issue?

Yes. Issues, meetings, feedback, insights, workflows and contexts can have multiple labels. For example, an issue could be labeled "Mobile," "P0," and "Customer-Acme" simultaneously for precise filtering.

Can I change a label's color or name after creating it?

Yes. Go to Settings → Labels, click the label you want to edit, and update the name or color. Changes apply across all items using that label.

How do labels help with @ mentions in Chat?

You can query labeled items directly: "@label: Mobile Bugs" or "@label: Customer Interview from last month" for precise, scoped results.

Did this answer your question?