Your Feedback Shapes Our Medical App

Thank you for contacting our support team. To help us resolve your issue as quickly as possible, please provide as much detail as you can below.

User and Account Information

Your Name:

Your Email Address:

Account/User ID:

Are you a subscribed user?

Technical Information

App Name:

App Version:

Device Model:

Operating System Version:

How did you install the app?

Problem Description

Please provide a detailed description of the problem:

(Please describe exactly what you were trying to do, what happened instead, and what you expected to happen. Include any error messages you saw.)

Detailed Questions to Help Us Pinpoint the Issue

If you selected "Search/Content Issue," please answer the following:

What specific term were you searching for?

Was the search term found, but the result was incorrect or incomplete?

Yes, it was incorrect or incomplete.

No, the search term was not found at all.

I'm not sure.

Did the app fail to find the term at all?

Yes, it did not find the term.

No, it found the term, but the results were incorrect.

Can you provide the correct information or a reference to what the content should be?

If you selected "Functionality/Feature Issue," please answer the following:

What specific feature is not working? (e.g., bookmarking, adding notes, clinical calculators, drug interaction checker)

For clinical calculators, what specific values were you entering?

For the drug interaction checker, what drugs were you comparing?

For note-taking or highlighting, what content were you trying to save?

If you selected "Performance," please answer the following:

Does the app crash or freeze at a specific point or action?

Yes, it happens at a specific point.

No, it seems to crash or freeze randomly.

If yes, please describe the specific action that causes the issue:

Is the app slow when performing a particular action (e.g., opening a specific section, running a search)?

Yes, it's slow when performing a specific action.

No, the app is generally slow all the time.

Does this happen every time you use the app, or only sometimes?

Every time (It happens consistently)

Sometimes (It happens intermittently)

If you selected "Account/Subscription Issue," please answer the following:

Can you describe the problem you are having with your account or subscription?

Have you tried restoring your purchase?

Yes

Can you provide a copy of your purchase receipt (without exposing sensitive information)?

Choose a file or drop it here

Steps to Reproduce the Problem

This is the most helpful section for our developers. Please describe the exact steps, in order, that we can follow to see the issue you are facing.

Screenshots or Screen Recording

Do you have a screenshot or screen recording that demonstrates the problem?

Yes

If so, please attach any relevant screenshots or screen recordings.

	Description / File Name	Upload File
	A	B
1
2
3
4
5

App Support Form Insights

Please remove this app support form insights section before publishing.

Here's a detailed breakdown of the insights behind each section:

1. User & Technical Information

The first two sections are all about establishing the context of the issue. By collecting the user's name, email, account ID, and subscription status right at the start, you can immediately identify them in your system. The technical information—App Version, Device Model, and Operating System—is crucial. This is the first thing a developer needs to know to try and reproduce a bug. An issue on iOS 17.4 might not exist on Android 14, and a bug in version 2.5.1 might have already been fixed in a newer release.

2. Problem Description and Detailed Questions

These sections form the core of the diagnostic process.

Primary Issue: This serves as a triage. The user's selection (e.g., "Performance," "Search/Content") allows the ticket to be automatically routed to the correct support queue or development team. This saves time and ensures the right person sees the report.
Detailed Description: This is the user's opportunity to tell their story. The free-text box is vital for getting the full narrative and any context that doesn't fit into a pre-defined category.
Conditional Questions: This is where the form becomes powerful. By only showing relevant questions based on the user's initial selection, you get specific, actionable data without cluttering the form. For example, if someone reports a "Functionality" issue with a clinical calculator, asking for the exact values they entered is the most important piece of information for a developer to replicate the bug.

3. Steps to Reproduce & Screenshots

These are the "golden nuggets" of any bug report. For a developer, the ability to reproduce a bug is often half the battle. The structured, numbered list forces the user to think logically about the sequence of events leading to the problem, providing a clear and repeatable path for your QA team or developers.

Finally, requesting a screenshot or screen recording is invaluable. A picture is worth a thousand words, and visual evidence of an error message or a misaligned element can immediately reveal the problem, saving significant time compared to trying to decipher a purely textual description.

Mandatory Questions Recommendation

Please remove this mandatory questions recommendation before publishing.

Based on the support form you provided, here are the mandatory questions and the reasoning behind why they are so important.

Your Email Address: This is the most critical piece of information. Without a valid email, your support team cannot follow up with the customer, request more details (like screenshots), or inform them when the issue has been resolved. It's the primary channel for communication.
App Version, Device Model, and Operating System Version: This group of questions is foundational for technical support. They tell your developers the exact environment where the problem occurred. A bug on a specific version of Android or a certain iPad model might not exist anywhere else. Without this information, a developer can't even begin to replicate the issue, making it almost impossible to fix.
Primary Issue and Detailed Description of the Problem: This is the core of the support ticket. "Primary Issue" helps you triage and route the ticket correctly, while the "Detailed Description" provides the narrative of the problem. Without knowing what happened, your team is flying blind. This is the first step in understanding the user's experience and the symptoms they're observing.

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.