Get Help with Your Education App

Important Note:

This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.

AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.

This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.

Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.

Strategic Questioning for Effective Troubleshooting

The form includes specific questions designed to narrow down issues and provide actionable insights to the support team.

User Information

• Full Name & Email Address: Basic contact information for follow-up.
• Your Role: Understanding the user's role (Student, Teacher, Administrator, etc.) is critical in an educational setting. Different roles might have different permissions, access levels, or workflows, which can significantly impact how an issue manifests or needs to be resolved.
• Institution/Organization Name (Optional): This helps support teams identify if the issue is widespread within a specific institution or related to institutional-level configurations.

App Information

• App Name & App Version: Essential for identifying the exact software being used. Knowing the version helps determine if the issue is already fixed in a newer release or is specific to an older build.
• Platform (iOS, Android, Web, Desktop): Crucial for replicating the environment and understanding platform-specific bugs.
• Device Model & Operating System Version: Provides granular detail about the user's hardware and software environment, which is often key to debugging compatibility or performance issues.

Issue Details

• Type of Issue: Categorizing the issue (Bug/Error, Performance, Login, Content, Crash, etc.) helps triage the support request to the correct team or specialist.
• Severity of Issue: Prioritizing issues based on impact (Critical, High, Medium, Low) allows the support team to address the most impactful problems first.
• Date and Time of Issue Occurrence: Helps correlate issues with server logs, system updates, or other events.
• Detailed Description of the Issue (Steps to reproduce, expected behavior, actual behavior): This is arguably the most important field. By asking for specific steps, the form guides the user to provide a clear, repeatable path to the issue, which is invaluable for developers.
• Any Error Messages Displayed?: Copying exact error messages is extremely helpful for developers to pinpoint the root cause quickly.
• Screenshots or Video (if applicable): Visual evidence can often convey more information than text alone, especially for UI/UX bugs or complex workflows. The form correctly notes that actual file uploads would be handled separately, which is a practical consideration for web forms.

Contextual Information

• What were you trying to achieve when the issue occurred?: This question helps understand the user's intent and workflow, providing context that might reveal user error or unexpected system interactions.
• Have you tried any troubleshooting steps?: Prevents support from suggesting steps the user has already taken, saving time and frustration for both parties.
• Is this issue reproducible?: Helps determine the consistency of the bug. An "always" reproducible bug is easier to fix than a "rarely" occurring one.
• Does this issue affect other users?: Indicates the scope of the problem – isolated to one user or a broader system issue.

Important Note:

This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.

Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.

Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.

The mandatory questions on this app support form are those marked with the required attribute. These fields are essential because they provide the fundamental information needed for the support team to understand, categorize, and begin resolving an issue.

Here are the mandatory questions and why they are crucial:

1. Full Name
2. • Why mandatory: This is basic contact information. The support team needs to know who they are assisting to personalize communication and track the request.
2. Email Address
3. • Why mandatory: This is the primary channel for the support team to communicate updates, ask follow-up questions, and provide solutions to the user. Without it, resolving the issue becomes impossible.
3. Your Role
4. • Why mandatory: In an educational context, the user's role (Student, Teacher, Administrator, etc.) is critical. It helps the support team understand the user's permissions, typical workflows, and potential impact of the issue. A problem for a student might be different from the same problem for a teacher or administrator due to varying access levels or responsibilities within the app.
4. App Name
5. • Why mandatory: If an organization offers multiple applications, knowing the specific app is fundamental. It ensures the support request is directed to the correct product team and that the troubleshooting steps are relevant to that particular application.
5. App Version
6. • Why mandatory: Software bugs are often version-specific. Knowing the exact app version helps the support team determine if the issue is a known bug that has already been fixed in a newer release, or if it's a new issue specific to that version. It also helps in replicating the environment.
6. Platform
7. • Why mandatory: Issues can be highly dependent on the operating system or environment the app is running on (iOS, Android, Web, Desktop). This information is vital for diagnosing platform-specific bugs and providing accurate troubleshooting steps.
7. Type of Issue
8. • Why mandatory: This categorizes the problem (e.g., Bug/Error, Performance Issue, Login Issue, App Crashes). It helps the support team triage the request, prioritize it, and assign it to the appropriate specialist or department (e.g., development, content, IT).
8. Severity of Issue
9. • Why mandatory: This allows the support team to understand the impact of the issue on the user's ability to use the app. Critical issues (app unusable, data loss) will be prioritized over low-severity issues (cosmetic inconveniences), ensuring that the most impactful problems are addressed first.
9. Detailed Description of the Issue
10. • Why mandatory: This is the most crucial field for understanding the problem. By asking for "Steps to reproduce, expected behavior, actual behavior," the form guides the user to provide actionable information. Without a clear description and steps to replicate, troubleshooting becomes a lengthy and often frustrating process of guesswork.
10. Is this issue reproducible?
11. • Why mandatory: Knowing if an issue can be consistently reproduced (Always, Sometimes, Rarely, Not reproducible) is vital for debugging. Reproducible bugs are generally easier to diagnose and fix, while intermittent issues require more effort and potentially different diagnostic approaches.
11. Does this issue affect other users?
12. • Why mandatory: This question helps determine the scope of the problem. If it's affecting multiple users, it might indicate a broader system outage, a server-side issue, or a widespread bug, warranting a higher priority and different investigation methods compared to an isolated user-specific problem.

These mandatory fields ensure that the support team receives a foundational set of data that allows them to efficiently understand, categorize, and begin the process of resolving the user's problem.