Support for Your Mental Health App Journey

Thank you for reaching out. Our goal is to provide you with the best possible support. Please fill out this form as completely as possible to help us understand and resolve your issue quickly.

Section 1: Your Information & App Details

(This information is crucial for us to look up your account and device specifics.)

 

Full Name:

Email Address:

App Name:

App Version Number:

Date of Issue First Occurred:

Frequency of the Issue:

Section 2: Device & System Information

(Technical details help us identify conflicts and bugs.)

 

Device Type:

Device Model:

Operating System (OS) Version:

How did you download the app?

Section 3: Detailed Description of the Issue

(Please describe your problem in as much detail as you are comfortable with.)

 

Category of Issue: (Please select all that apply)

Technical/Functional Bug (e.g., app crashes, feature not working, login failure)

Account & Billing (e.g., subscription problems, payment issues, cannot access paid content)

Content & Functionality (e.g., question about a meditation, exercise doesn't seem to work, journal not saving)

Data & Privacy (e.g., data missing, concern about data security, request to delete data)

General Feedback & Suggestion (e.g., idea for a new feature, UI is confusing)

Urgent Mental Health Concern (Please see important note below)

Important Note Regarding Urgent Concerns:

This app is not designed for crisis situations and our support team is not comprised of licensed crisis counselors. If you are experiencing a mental health emergency, thinking about hurting yourself or others, or are in immediate danger, please contact your local emergency services or a crisis hotline immediately.

Please describe the issue in your own words: (What were you trying to do? What happened instead? What error message, if any, did you see?)

Steps to Reproduce the Issue: (Please list the exact steps you took before the problem occurred. This is extremely helpful for our developers.)

Screenshots or Screen Recordings: (Please attach any screenshots or screen recordings that show the problem.

Description / File Name

Upload File

A
B
1
 
 
2
 
 
3
 
 
4
 
 
5
 
 

Section 4: For Technical & Account Issues

(Only complete this section if your issue is related to technical problems, logging in, or payments.)

 

Are you logged into the app?

Yes, I am logged in.

No, I cannot log in.

I am logged in, but my subscription content is missing.

If you cannot log in, what happens?

"Invalid password" error

"User not found" error

App crashes after entering credentials

Is your issue related to a subscription or payment?

If yes, please describe the billing issue:

I was charged but my premium access wasn't unlocked.

I'm being charged after canceling my subscription.

I want to request a refund.

I need help changing my subscription plan.

Section 5: For Content & App Experience Issues

(Only complete this section if your issue is about the app's content, exercises, or your personal experience with it.)

 

What specific feature or content were you using? (e.g., "Anxiety Meditation Pack," "Sleep Story: Ocean Waves," "Mood Tracker," "Breathing Exercise Widget")

 

What was your expectation, and what was the actual result?

 

Expected:

Actual Result:

Have you successfully used this feature/content before?

Yes

No, this was my first time.

I'm not sure.

Section 6: Additional Information

Is there anything else you think we should know about your device, setup, or the issue? (e.g., "I have low storage space," "I use battery saver mode," "This only happens on WiFi," "I've reinstalled the app already.")

How would you prefer we contact you?

Email (at the address provided)

Push Notification (through the app)

No follow-up needed; I was just providing feedback.

 

Thank you for taking the time to provide these details. Your feedback is invaluable in helping us improve our app and your experience. A member of our support team will review your submission and be in touch shortly.

 

App Support Form Insights

Please remove this app support form insights section before publishing.


Here is a detailed breakdown and analysis of the provided Mental Health App Support Form. This insight covers its structure, psychological considerations, technical effectiveness, and potential areas for improvement.

Comprehensive Analysis of the Mental Health App Support Form

This form is expertly crafted to be more than just a bug report tool. It's a sophisticated communication channel designed for a sensitive industry, balancing technical diagnostics with user empathy.

1. Overall Structure and Flow

The form follows a logical, funnel-like structure that is optimal for support ticketing systems:

  • User-Centric Start: It begins with gratitude and a clear purpose, setting a positive and helpful tone from the outset.
  • Progressive Detail: It moves from simple, objective facts (user info, app version) to more complex, subjective descriptions of the problem. This prevents users from being overwhelmed immediately.
  • Conditional Sections: The use of "Only complete this section if..." is crucial. It prevents user fatigue and ensures the data collected is relevant, making the support agent's job of triaging tickets much easier.
  • Clear Conclusion: It manages expectations by informing the user of the next steps.

2. Key Strengths and Strategic Insights

a) Empathy and Crisis Management:
This is the most critical differentiator for a mental health app. The form explicitly includes:

  • A dedicated category for "Urgent Mental Health Concern." This allows the support team to immediately identify and appropriately handle these sensitive tickets, potentially escalating them to a human faster or providing a tailored, empathetic response with resources.
  • A prominent, clear disclaimer directing users in crisis to immediate, professional help. This is a vital ethical and liability safeguard for the company, demonstrating a responsible approach to user well-being.

b) Technical Precision for Rapid Diagnosis:
The form acts as a powerful diagnostic tool by explicitly asking for information that users often omit:

  • App Version & OS Version: These are the first things a developer asks for. A bug might only exist in version 2.1.0 and be fixed in 2.1.1, or only occur on iOS 17.
  • Frequency: Knowing if an issue is "Every time" or "Occasionally" points towards a consistent bug versus a race condition or network-dependent issue.
  • Steps to Reproduce: This is the gold standard for developers. If support can get a reproducible set of steps, the fix time is drastically reduced.
  • Request for Media: The prompt for screenshots or screen recordings is invaluable. A 10-second video can replace a paragraph of confusing text.

c) Effective Triage and Categorization:
The "Category of Issue" section is the backbone of an efficient support workflow. It allows for:

  • Automated Routing: Tickets can be automatically tagged and assigned to the correct team (e.g., billing issues go to the payments team, technical bugs go to developers, content feedback goes to product managers).
  • Priority Setting: A "Technical Bug" affecting all users is a P1 (high priority) issue, while a "General Suggestion" is important but not urgent.
  • Metric Tracking: The company can analyze these categories to see where most problems arise (e.g., "60% of our tickets are about billing"), providing direct insight for product improvement.

d) Segmentation of Problem Types:
Splitting "Technical" and "Content" issues into separate sections is brilliant.

  • Technical Section focuses on objective facts: login states, error messages, and payment statuses.
  • Content Section focuses on the subjective user experience: expectations vs. reality. This helps the content team understand if a meditation is ineffective, a UI is confusing, or a description is misleading.

3. Psychological and User Experience (UX) Considerations

  • Reduced Friction: Pre-defined checkboxes and dropdowns make the form faster to complete, increasing the likelihood that a frustrated user will actually submit it.
  • Empowering the User: By asking structured questions, it guides users who may not be tech-savvy to provide useful information without needing to know technical jargon.
  • Trust and Transparency: The professional design and clear communication build trust. The user feels heard because the form is asking detailed, relevant questions.

4. Potential Improvements & Considerations

While excellent, the form could be enhanced in a few ways:

  • Data Privacy Assurance: Adding a short line like, "All information you provide will be kept confidential and used solely to resolve your support request," could alleviate user concerns, especially given the sensitive nature of a mental health app.
  • "Last Successful Use" Question: For technical bugs, adding "When was the last time this feature worked correctly?" can help developers identify which app update introduced the regression.
  • Network Information: For issues related to streaming content or syncing data, a checkbox for "Wi-Fi" vs. "Cellular Data" could be useful.
  • Integration with Backend: In an ideal world, this form would be integrated with the app itself. The app could pre-fill data like App Version, Device Model, and OS Version automatically, removing the burden from the user.

Conclusion

This support form is a well-designed, strategic tool that effectively serves multiple audiences:

  • For Users: It provides a clear, structured, and empathetic path to get help.
  • For Support Agents: It provides organized, high-quality data, drastically reducing the number of back-and-forth emails needed to diagnose a problem.
  • For Developers & Product Managers: It delivers actionable, categorized feedback and bug reports that can directly inform software updates and product roadmaps.
  • For the Company: It manages risk, builds user trust, and provides valuable analytics on product performance and user experience pain points.

It successfully transcends a simple contact form by being a critical component of the app's overall user support and product development ecosystem.

Mandatory Questions Recommendation

Please remove this mandatory questions recommendation before publishing.


Based on the provided form, here are the questions that should be considered mandatory, along with a detailed explanation for each.

Mandatory Questions & Why They Are Essential

1. Email Address

  • Why Mandatory: This is the primary channel for support communication. Without an email address, the support team has no way to:
    • Ask for follow-up information.
    • Provide a solution or steps to resolve the issue.
    • Send a confirmation that the ticket has been received and is being processed.
    • Notify the user when a bug has been fixed.
  • Consequence of Omitting: The support request is useless. It becomes a message into a void with no way to deliver a response.

2. App Name

  • Why Mandatory: A company often develops more than one app. The support team needs to know exactly which product the user is having trouble with. The internal infrastructure, knowledge base, and development teams are different for each app.
  • Consequence of Omitting: The ticket would be misrouted or delayed significantly as agents try to guess which app is being discussed, based on perhaps vague descriptions.

3. Category of Issue

  • Why Mandatory: This is the single most important piece of information for triage. It instantly tells the support agent:
    • Urgency: A "Urgent Mental Health Concern" is handled with extreme care and speed, unlike a "General Feedback."
    • Routing: A billing issue is sent to the payments/finance team. A technical bug is sent to the development team. A content question is sent to a content specialist.
    • Context: It sets the frame for understanding the user's entire description.
  • Consequence of Omitting: The ticket lacks direction. It could be sent to the wrong team, who then have to re-route it, causing significant delays in response time.

4. Description of the Issue

  • Why Mandatory: This is the core of the ticket. All other questions simply provide context for this description. Without knowing what the problem is, the support team cannot even begin to help. A good description answers: "What were you trying to do?" and "What went wrong?"
  • Consequence of Omitting: The ticket contains device info and an email but zero information about the actual problem. The agent would have to reply with a single question: "What is the problem you are facing?" which is an inefficient and frustrating first interaction.

Highly Recommended (But Perhaps Not Strictly Mandatory)

The following questions are so critical to a quick resolution that the form should be designed to strongly encourage their completion (e.g., with an asterisk *), even if they aren't technically mandatory. A ticket missing this information will almost certainly require a slow, back-and-forth email chain.

  • App Version Number & OS Version: The vast majority of bugs are specific to a certain version of the app or operating system. Knowing this allows the support agent to:
    1. Immediately know if the user is on an old version with a known bug and advise them to update.
    2. If they are on the latest version, it confirms a new bug that needs to be reported to developers.
      Without this, the agent's first question will always be: "What version of the app and OS are you using?"
  • Device Type (e.g., iPhone, Android): The ecosystem (Apple vs. Google) is fundamentally different. Problems with subscriptions, notifications, and app distribution are entirely platform-specific. Sending an Android solution to an iPhone user is a waste of everyone's time.

Summary: The "Perfect" Mandatory Set

A well-designed form would likely make these fields mandatory:

  1. Email Address (For communication)
  2. App Name (For routing)
  3. Category of Issue (For triage and urgency)
  4. Description of the Issue (The core problem)

And then use smart design (like making the "Next" button inactive until these fields are filled) to strongly encourage the completion of the Device and OS Version fields, as the ticket is severely hampered without them.

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.