Skip to main content

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 empty

I need a way to automatically detect and follow up on these empty submissions. Specifically, I’m exploring:

  1. How to set up a workflow that reads the body of the email
  2. How to detect the absence of details in key fields
  3. How to trigger an automatic response requesting more information

Here's what a typical empy bug report email looks like:
 

Subject: Bug: Critical: User provided subject

Email Body:
User: {{user_email}}
Build number: BE 5.0.0 / FE 5.2.99
Date/Time: 19/09/2024 12:02:10 PM
Priority: Critical

Steps 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!

Hi @Patrick H12, It’s Mat from the Support Engineering Team 😀

Have you considered creating an Intercom tickets with those fields set to required?

That might resolve your issues with the unfulfilled bug report questions.


I’ve thought about it. Currently users are presented with this screen when a crash occurs. Is it currently possible to invoke a specific ticket creation type via the API?


@Patrick H12  absolutely, just look at our documentation here.


Reply