All use cases

Handling feature requests

Agents

Customer agent

Internal agent

Categories

Resolving general tickets

Generating reports

Executing actions in tools

Share

Copy link

Description

Handling feature requests manually is messy - you need to check if the feature already exists, tag tickets consistently, aggregate feedback for the product team, and remember to notify customers when features ship. Without a system, valuable feedback gets lost and customers never hear back.

You can configure both the Customer agent and Internal agent to handle feature requests end-to-end by setting up ticket tagging and scheduled tasks for aggregation and follow-ups.

The Customer agent automatically checks if features exist, tags requests consistently, and thanks customers. The Internal agent aggregates requests into summaries for your product team and queues follow-up messages when features ship - so customers know their feedback mattered.

Example

Customer agent

Internal agent

Configuration

Tools

Search knowledge

Parahelp

Search help center and internal knowledge snippets.

Memory

Feature requests

When you receive a feature request, first use the

Parahelp: Search knowledge

tool to check if the requested feature already exists in the product. If it does, inform the customer how to use it and provide relevant documentation. If the feature doesn't exist, use the

Ticketing: Add ticket tag

tool to tag the ticket with "feature-request" and the relevant feature category (e.g., "feature-request:integrations"). Use the

Ticketing: Reply to ticket

tool to thank the customer for their feedback and let them know it has been shared with the product team.

Simulation

  1. Customer action: Ticketing - Submit query ("It would be great if you added dark mode!")

  2. Agent action: Parahelp - Search memory

  3. Agent action: Parahelp - Search knowledge (checked if dark mode exists)

  4. Agent action: Ticketing - Added tag ("feature-request:ui")

  5. Agent action: Ticketing - Send ticket response ("Thanks for the suggestion! Dark mode is a popular request and I've shared your feedback with our product team. We'll notify you if it gets added. Let me know if there's anything else I can help with!")

Example

Customer agent

Internal agent

Configuration

Tools

Search knowledge

Parahelp

Search help center and internal knowledge snippets.

Memory

Feature requests

When you receive a feature request, first use the

Parahelp: Search knowledge

tool to check if the requested feature already exists in the product. If it does, inform the customer how to use it and provide relevant documentation. If the feature doesn't exist, use the

Ticketing: Add ticket tag

tool to tag the ticket with "feature-request" and the relevant feature category (e.g., "feature-request:integrations"). Use the

Ticketing: Reply to ticket

tool to thank the customer for their feedback and let them know it has been shared with the product team.

Simulation

  1. Customer action: Ticketing - Submit query ("It would be great if you added dark mode!")

  2. Agent action: Parahelp - Search memory

  3. Agent action: Parahelp - Search knowledge (checked if dark mode exists)

  4. Agent action: Ticketing - Added tag ("feature-request:ui")

  5. Agent action: Ticketing - Send ticket response ("Thanks for the suggestion! Dark mode is a popular request and I've shared your feedback with our product team. We'll notify you if it gets added. Let me know if there's anything else I can help with!")

Example

Customer agent

Internal agent

Configuration

Tools

Search knowledge

Parahelp

Search help center and internal knowledge snippets.

Memory

Feature requests

When you receive a feature request, first use the

Parahelp: Search knowledge

tool to check if the requested feature already exists in the product. If it does, inform the customer how to use it and provide relevant documentation. If the feature doesn't exist, use the

Ticketing: Add ticket tag

tool to tag the ticket with "feature-request" and the relevant feature category (e.g., "feature-request:integrations"). Use the

Ticketing: Reply to ticket

tool to thank the customer for their feedback and let them know it has been shared with the product team.

Simulation

  1. Customer action: Ticketing - Submit query ("It would be great if you added dark mode!")

  2. Agent action: Parahelp - Search memory

  3. Agent action: Parahelp - Search knowledge (checked if dark mode exists)

  4. Agent action: Ticketing - Added tag ("feature-request:ui")

  5. Agent action: Ticketing - Send ticket response ("Thanks for the suggestion! Dark mode is a popular request and I've shared your feedback with our product team. We'll notify you if it gets added. Let me know if there's anything else I can help with!")

Example

Customer agent

Internal agent

Configuration

Tools

Search knowledge

Parahelp

Search help center and internal knowledge snippets.

Memory

Feature requests

When you receive a feature request, first use the

Parahelp: Search knowledge

tool to check if the requested feature already exists in the product. If it does, inform the customer how to use it and provide relevant documentation. If the feature doesn't exist, use the

Ticketing: Add ticket tag

tool to tag the ticket with "feature-request" and the relevant feature category (e.g., "feature-request:integrations"). Use the

Ticketing: Reply to ticket

tool to thank the customer for their feedback and let them know it has been shared with the product team.

Simulation

  1. Customer action: Ticketing - Submit query ("It would be great if you added dark mode!")

  2. Agent action: Parahelp - Search memory

  3. Agent action: Parahelp - Search knowledge (checked if dark mode exists)

  4. Agent action: Ticketing - Added tag ("feature-request:ui")

  5. Agent action: Ticketing - Send ticket response ("Thanks for the suggestion! Dark mode is a popular request and I've shared your feedback with our product team. We'll notify you if it gets added. Let me know if there's anything else I can help with!")

Supercharge your customer support team like many others.