All use cases

Handling bug reports using Linear

Agents

Customer agent

Internal agent

Categories

Resolving troubleshooting tickets

Generating reports

Executing actions in tools

Share

Copy link

Description

Handling bug reports manually is chaotic - you need to check if the bug is already known, link tickets to Linear issues, keep engineering updated on impact, and remember to follow up with customers when bugs are fixed. Things fall through the cracks, customers get frustrated, and engineers lack the context they need.

You can configure both the Customer agent and Internal agent to handle bugs end-to-end by connecting Linear and setting up scheduled tasks for pattern detection and follow-ups.

The Customer agent automatically links incoming bug reports to existing Linear issues and informs customers. The Internal agent identifies bug patterns, creates new Linear issues, and queues follow-up messages when bugs are resolved - closing the loop with every affected customer.

Example

Customer agent

Internal agent

Configuration

Tools

Link support ticket to Linear issue

Linear

Link ticket to Linear issue for tracking and automated follow-ups.

Search in existing Linear issues

Linear

Search Linear for bugs, feature requests, or product updates.

Search knowledge

Parahelp

Search help center and internal knowledge snippets.

Memory

Bug reports

When you receive a bug report, use the

Linear: Search in existing Linear issues

tool to check if a matching issue already exists (only issues with the

parahelp_agent

label are searchable). If a matching issue is found, use the

Linear: Link support ticket to Linear issue

tool to attach the ticket as new evidence and use the

Ticketing: Reply to ticket

tool to inform the customer that the issue is known and being worked on. If no match exists and the bug is confirmed, use the

Ticketing: Transfer ticket

tool to transfer to the team for triage.

Simulation

  1. Customer action: Ticketing - Submit query ("My video generated in the wrong language")

  2. Agent action: Parahelp - Search memory

  3. Agent action: Linear - Searched existing issues ("wrong language audio")

  4. Agent action: Linear - Linked ticket to existing issue

  5. Agent action: Ticketing - Send ticket response ("I've identified this as a known issue our team is actively working on. I've added your report to help our engineers investigate. You'll be notified when it's resolved. Sorry for the inconvenience!")

Example

Customer agent

Internal agent

Configuration

Tools

Link support ticket to Linear issue

Linear

Link ticket to Linear issue for tracking and automated follow-ups.

Search in existing Linear issues

Linear

Search Linear for bugs, feature requests, or product updates.

Search knowledge

Parahelp

Search help center and internal knowledge snippets.

Memory

Bug reports

When you receive a bug report, use the

Linear: Search in existing Linear issues

tool to check if a matching issue already exists (only issues with the

parahelp_agent

label are searchable). If a matching issue is found, use the

Linear: Link support ticket to Linear issue

tool to attach the ticket as new evidence and use the

Ticketing: Reply to ticket

tool to inform the customer that the issue is known and being worked on. If no match exists and the bug is confirmed, use the

Ticketing: Transfer ticket

tool to transfer to the team for triage.

Simulation

  1. Customer action: Ticketing - Submit query ("My video generated in the wrong language")

  2. Agent action: Parahelp - Search memory

  3. Agent action: Linear - Searched existing issues ("wrong language audio")

  4. Agent action: Linear - Linked ticket to existing issue

  5. Agent action: Ticketing - Send ticket response ("I've identified this as a known issue our team is actively working on. I've added your report to help our engineers investigate. You'll be notified when it's resolved. Sorry for the inconvenience!")

Example

Customer agent

Internal agent

Configuration

Tools

Link support ticket to Linear issue

Linear

Link ticket to Linear issue for tracking and automated follow-ups.

Search in existing Linear issues

Linear

Search Linear for bugs, feature requests, or product updates.

Search knowledge

Parahelp

Search help center and internal knowledge snippets.

Memory

Bug reports

When you receive a bug report, use the

Linear: Search in existing Linear issues

tool to check if a matching issue already exists (only issues with the

parahelp_agent

label are searchable). If a matching issue is found, use the

Linear: Link support ticket to Linear issue

tool to attach the ticket as new evidence and use the

Ticketing: Reply to ticket

tool to inform the customer that the issue is known and being worked on. If no match exists and the bug is confirmed, use the

Ticketing: Transfer ticket

tool to transfer to the team for triage.

Simulation

  1. Customer action: Ticketing - Submit query ("My video generated in the wrong language")

  2. Agent action: Parahelp - Search memory

  3. Agent action: Linear - Searched existing issues ("wrong language audio")

  4. Agent action: Linear - Linked ticket to existing issue

  5. Agent action: Ticketing - Send ticket response ("I've identified this as a known issue our team is actively working on. I've added your report to help our engineers investigate. You'll be notified when it's resolved. Sorry for the inconvenience!")

Example

Customer agent

Internal agent

Configuration

Tools

Link support ticket to Linear issue

Linear

Link ticket to Linear issue for tracking and automated follow-ups.

Search in existing Linear issues

Linear

Search Linear for bugs, feature requests, or product updates.

Search knowledge

Parahelp

Search help center and internal knowledge snippets.

Memory

Bug reports

When you receive a bug report, use the

Linear: Search in existing Linear issues

tool to check if a matching issue already exists (only issues with the

parahelp_agent

label are searchable). If a matching issue is found, use the

Linear: Link support ticket to Linear issue

tool to attach the ticket as new evidence and use the

Ticketing: Reply to ticket

tool to inform the customer that the issue is known and being worked on. If no match exists and the bug is confirmed, use the

Ticketing: Transfer ticket

tool to transfer to the team for triage.

Simulation

  1. Customer action: Ticketing - Submit query ("My video generated in the wrong language")

  2. Agent action: Parahelp - Search memory

  3. Agent action: Linear - Searched existing issues ("wrong language audio")

  4. Agent action: Linear - Linked ticket to existing issue

  5. Agent action: Ticketing - Send ticket response ("I've identified this as a known issue our team is actively working on. I've added your report to help our engineers investigate. You'll be notified when it's resolved. Sorry for the inconvenience!")

Supercharge your customer support team like many others.

Book a demo

Book a demo

Book a demo