Automating Follow-ups for Empty Bug Reports: Trigger Ideas Needed!

Patrick H12 · 2024-09-19T02:31:30+00:00

We're facing a common issue with our in-app bug reporting system, and I'm hoping the community can help brainstorm a solution.The problem: 90% of users submit bug reports without providing crucial details Our standard form includes fields for: Steps to reproduce Actual results Expected results Most submissions have these fields emptyI need a way to automatically detect and follow up on these empty submissions. Specifically, I’m exploring:How to set up a workflow that reads the body of the email How to detect the absence of details in key fields How to trigger an automatic response requesting more informationHere's what a typical empy bug report email looks like: Subject: Bug: Critical: User provided subjectEmail Body:User: {{user_email}}Build number: BE 5.0.0 / FE 5.2.99Date/Time: 19/09/2024 12:02:10 PMPriority: CriticalSteps to reproduce: Actual result: Expected result: Is it possible to create a trigger based on the absence of details under "Steps to reproduce," "Actual result," and "Expected result"? If so, how would you approach this? Any ideas, code snippets, or Intercom-specific solutions would be greatly appreciated!

Automating Follow-ups for Empty Bug Reports: Trigger Ideas Needed! | Community

Join the Intercom Community 🎉

Intercom Customers and Employees

Login to the community

Intercom Customers and Employees

Scanning file for viruses.

This file cannot be downloaded