🎯Requests

Quick refresher on Requests

In Cycle, Requests are the actionable items your team will work on: features to build, bugs to fix, problems to understand, praise to celebrate, or improvements to consider. They help bridge the gap between raw user feedback and actual product delivery.

Requests are not feedback themselves, they are what gets delivered based on the feedback.

Where do Requests fit in the Cycle workflow?

Here’s how they slot into the core Cycle hierarchy:

1. Feedback – Raw input from users (from Intercom, Slack, Gong, etc.)

2. Quotes – Snippets of feedback that carry a specific signal

3. Requests – Structured items your team will act on

This separation allows you to:

• Extract only the relevant parts of feedback (quotes)

• Group related quotes into a single Request

• Turn that Request into something your team can track, scope, and deliver

Why Requests Matter

• Structured delivery – They let you organize and track what needs to be done

• Custom-fit for your team – Request types can adapt to different internal workflows

• Feedback traceability – Every Request can be traced back to real user needs

• Collaboration-friendly – PMs, designers, engineers, and CS can all work around shared, structured docs

---

Request Type Settings

1. Content Template

Use templates to standardize how each Request is written. Cycle’s rich editor supports reusable templates, like:

• 🌱 Feature: Problem to solve, Goals, User stories, Success criteria

• 🔴 Problem: Context, Impacted users, Frequency, Underlying cause

You can:

• Write your own from scratch

• Use templates from Cycle’s library

• Update them over time as your rituals evolve

---

2. Statuses

Request Types can have their own status flows, depending on how you treat each kind of work.

For example:

• 🌱 Feature: In consideration → Planned → In progress → Shipped → Loop closed

• 🔴 Problem: Investigating (→ Backlog) → In progress → Resolved → Loop closed

Statuses are used to:

• Reflect the state of the work

• Trigger automations (e.g., notify customers when loop is closed)

• Filter and visualize progress in views & dashboards

---

3. Properties

Each Request Type can include properties that help with filtering, triaging, and prioritization. These are fully customizable and can vary per type.

Example properties:

• 🌱 Feature: Timeline (Now / Soon / Later), Confidence, Complexity

• 🔴 Problem: Affected Module, Impacted customer segment

• 👏 Kudo: Source (User/Internal/Other), Mentioned feature

These show up in:

• Filtering & sorting fields in you Views & dashboards

---

4. Hierarchy

Cycle supports request hierarchies, so you can model your process clearly.

Examples:

• A 💡 Solution request can have multiple 🔴 Problem children

• A 🔴 Problem can include multiple Quotes and will be part of a single 💡 Solution

This lets you:

• Mirror internal team workflows & processes

• Organize complex Requests into sub-requests

• Slice data cleanly in views & dashboards

---

5. Link Settings (Feedback, Releases, AI)

For each Request Type, you can choose whether it:

• ✅ Can be linked to Feedback (Allows quotes to be directly associated with this request type)

• ✅ Can be linked to Releases (Allows the request type to be directly associated with a Release Note)

• ✅ Is enabled for AI extraction (Allows the AI to extract quotes for this request type from feedback)

For example:

• You might enable AI for Problems so Autopilot extracts them from feedback

• But disable AI for Solutions, since those should come from the team

• You can link Features to Releases, but skip this for Bugs or Praise if irrelevant

This gives you control over what the AI processes and what your team owns.

---

Tips to get the most out of Request Types

• Start with 2–3 Request Types to avoid overcomplication at the start

• Use emojis to make them visually scannable in Views

• Adjust templates/statuses based on your product development rituals

• Use hierarchy to reflect your team’s internal workflow and processes.

---

Cycle was designed to fit your workflow, not force one. Request Types let you bring structure to how your team turns feedback into real product outcomes.