Cycle's help center
LegalCompany
  • 🧱Cycle core
    • πŸš€Capturing Feedback
    • πŸ› οΈProcessing Feedback
    • πŸ€”Prioritizing Insights
    • 🀩Closing the Loop
  • 🧭Guides
    • πŸŒ†Views
    • ✨AI-powered editor
    • πŸ€–Cycle Ask
    • πŸ“’Release Notes & Changelog
    • 🚦Cycle Dashboards
    • πŸ‘±Customers
    • πŸ””Notifications
    • πŸ“–Cycle Glossary
  • βš™οΈSettings
    • 🧩Initial setup
    • πŸ’ΌGeneral
    • 🧠AI Prompts
    • πŸ“‚Product Areas
    • πŸ‘·Customer Sync
      • Customer Data Ingestion
      • Salesforce
      • HubSpot
    • 🏷️Properties
    • πŸ”—Integrations
      • Feedback Sources
        • Chrome extension
        • Cycle Notetaker
        • Email
        • Gong
        • HubSpot
        • Intercom
        • Modjo
        • Salesforce
        • Slack
        • Zapier
        • Zendesk
      • Product Delivery Tools
        • GitHub
        • Linear
        • Notion
Powered by GitBook
On this page
  • 🧾 Feedback
  • βœ‚οΈ Quote
  • πŸ“Œ Request
  • πŸ‘οΈ View
  • πŸ“‚ Section
  • πŸ› οΈ Maker
  • πŸ‘₯ Collaborator
  • πŸ§‘β€πŸ’Ό Customer (CRM Entity)
  • πŸ”— Integration
  • 🧠 Cycle Autopilot
  • πŸ—‚οΈ Product Areas
  • 🧩 Product Categories
  • πŸ“Š Dashboards
  • πŸ€– Cycle Ask
  • πŸ“ Custom Prompts
  • πŸ”„ Closing the Loop
  • πŸ“’ Changelog
  • πŸ—’οΈ Release Notes
  • 🏝️ Feedback Island

Was this helpful?

  1. Guides

Cycle Glossary

This is a non-exhaustive list of some Cycle terms you may encounter.

This glossary provides definitions for key terms used within Cycle, reflecting the latest features and terminology.


🧾 Feedback

  • The raw, unfiltered voice of users or teammates.

  • Serves as the β€œraw material” before extracting quotes and connecting them to features.

  • Can come from various sources like messages, comments, tickets, screenshots, transcripts, voice notes, or recordings.


βœ‚οΈ Quote

  • Atomic, actionable pieces of information pulled from Feedback.

  • Each Quote is linked to a Request.


πŸ“Œ Request

  • The core unit of product work in Cycle.

  • Linked to one or more Quotes.

  • Can be any type like Bug, Feature, Need, Project, Kudo, or custom types defined by the team.

  • Represents the actionable β€œto-dos” that teams track, discuss, and ship.


πŸ‘οΈ View

  • A collection of Feedbacks, Quotes, or Requests.

  • Configurable by β€œMakers” only.

  • Supports grouping, filtering, sorting.

  • Can be displayed as List or Kanban views.


πŸ“‚ Section

  • A collection of views.

  • Can be renamed and rearranged via drag-and-drop.

  • New views can be created by hovering over a section and clicking β€œ+”.


πŸ› οΈ Maker

  • A special role that allows setting up views, managing roles, and editing billing information.

  • Makers can add unlimited makers & collaborators for free.


πŸ‘₯ Collaborator

  • A role that can perform most actions in Cycle except setting up views, creating quotes, changing user roles, and managing billing information.


πŸ§‘β€πŸ’Ό Customer (CRM Entity)

  • Customers are people synced from your CRM (e.g., HubSpot).

  • They’re tied to Feedback to show who said what, and when.

  • Customers belong to Companies, which are also synced.

  • These entities help enrich feedback with context like account details, segments, etc.


πŸ”— Integration

  • Connections with external tools (e.g., Slack, Intercom, HubSpot, Zendesk) that automatically route feedback into the Cycle Inbox.

  • Can be set up in settings under β€œIntegrations.”

  • Delivery tool integrations (e.g., Linear, GitHub, Jira) can be embedded in a doc to facilitate collaboration with developers.


🧠 Cycle Autopilot

  • An AI-powered engine that processes new feedback in the Inbox.

  • Extracts key Quotes and links them to appropriate Requests.

  • Suggests creating new Requests if no match exists.

  • Leverages Product Areas for triaging Feedback.


πŸ—‚οΈ Product Areas

  • Segments dividing a product into clear, non-overlapping buckets (e.g., Billing, User Management, Integrations).

  • Help teams own specific areas and route feedback accordingly.

  • Should ideally follow the MECE (Mutually Exclusive, Collectively Exhaustive) principle.


🧩 Product Categories

  • Groups that encompass multiple Product Areas, typically aligned with teams or squads (e.g., Platform, Customer Experience).


πŸ“Š Dashboards

  • Customizable command centers in Cycle.

  • Used to visualize, filter, and analyze customer feedback, quotes, and requests.

  • Provide a single source of truth for data-driven product decisions.


πŸ€– Cycle Ask

  • An AI tool that allows querying the entire workspace or specific items (Feedback, Requests) in plain language.

  • Provides source-backed answers, summaries, and insights from customer data.


πŸ“ Custom Prompts

  • AI prompts that extract value from documents in Cycle, such as summaries, insights, or analyses.

  • Feedback-level Prompts: Configured to run automatically on new feedback from specified sources, displaying results in the feedback interface.

  • Request-level Prompts: Linked to specific Request types, executable with one click from a Request item to generate summaries, drafts, or analyses.


πŸ”„ Closing the Loop

  • The process of informing customers and stakeholders when their feedback has led to action or a product change.

  • Facilitated through automatic updates and notifications via integrations like Slack, Intercom, and email.


πŸ“’ Changelog

  • A public or private record of changes and updates made to the product.

  • Often generated from Release Notes.


πŸ—’οΈ Release Notes

  • Documentation announcing and describing new features or changes in a product release.

  • Often drafted in Cycle with AI assistance.


🏝️ Feedback Island

  • A feature allowing manual drag-and-drop of various file types (images, PDFs, audio, videos, links) into Cycle.

  • Cycle processes these files (OCR for text, transcription for audio/video) to capture feedback.

PreviousNotificationsNextInitial setup

Last updated 4 days ago

Was this helpful?

🧭
πŸ“–