Feature Requests from Calls

What does this mean?

Facilitates the seamless incorporation of feedback into product plans, ensuring requests are efficiently prioritized with comprehensive context preserved.

How it works?

Transcribes customer calls to detect, de-duplicate, and route feature requests into the product backlog, keeping context intact for tagging customer specifics, motivations, and scenarios.

Workflow steps

Step 1: Trigger on call completion

The Workflow activates automatically when a customer call ends, using a Meeting Ended trigger or integration with your call recording platform (such as Gong) to capture the conversation.

Step 2: Transcribe and analyze the call

Cassidy processes the call recording to generate a full transcript, then identifies any feature requests mentioned during the conversation.

Step 3: Extract request details and context

The Workflow pulls out key information for each feature request—including the customer's name, company, use case, motivation, and specific scenarios—preserving the full context behind the ask.

Step 4: De-duplicate against existing requests

Cassidy checks the extracted requests against your product backlog to identify duplicates, linking new mentions to existing items or flagging truly new requests for addition.

Step 5: Route to product backlog

The Workflow creates or updates backlog items in your project management tool (such as Jira) with the feature request details, customer tags, and relevant context for prioritization.

Step 6: Notify the product team

A notification is sent via Slack or email to alert the product team of new or updated feature requests, giving them immediate visibility into customer feedback without manual effort.