Get Support for Your Cleaning 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.

Below is a detailed breakdown of the Cleaner Booking App Support Form, explaining the purpose of each section, why specific questions are included, and how they help streamline customer support and issue resolution.

1. User Information

Purpose:

• Ensures the support team can identify the user and locate their account (if applicable).
• Helps prevent fraud or impersonation when handling sensitive issues (e.g., refunds, account access).

Key Insights:

• Full Name & Email: Necessary for verification and follow-up communication.
• Phone Number: Useful for urgent issues (e.g., cleaner no-show).
• User ID: Helps quickly pull up account details in the database.

Improvement Consideration:

• If the app uses OAuth (Google/Apple login), adding an option like "Logged in via [Google/Apple]" could help troubleshoot login issues.

2. Type of Issue

Purpose:

• Categorizes the problem for faster routing to the correct support team (e.g., technical vs. booking-related).

Key Insights:

• Login/Account Access: Indicates possible password resets, 2FA issues, or app authentication failures.
• Booking/Payment Failure: Points to gateway errors, declined cards, or app glitches during checkout.
• Cleaner No-Show/Late Arrival: Requires immediate escalation to operations teams.
• Service Quality Issue: May need follow-up with the cleaning provider.

Improvement Consideration:

• Adding sub-options (e.g., under "Payment Failure": "Card Declined," "Payment Processed but No Booking Confirmation") could further refine troubleshooting.

3. Detailed Problem Description

Purpose:

• Gathers context to reproduce and diagnose the issue.

Key Insights:

• "What were you trying to do?" Identifies the exact workflow where the problem occurred (e.g., booking, rescheduling).
• Frequency of Issue: Helps distinguish between one-time glitches and systemic bugs.
• Steps to Reproduce: Critical for developers to fix bugs (e.g., "App crashes when clicking 'Confirm Booking' after selecting a discount code").

Improvement Consideration:

• Adding a dropdown for "Were you able to complete the action?" (Yes/Partially/No) could clarify severity.

4. Booking Details

Purpose:

• Essential for resolving booking-specific issues (e.g., no-shows, double charges).

Key Insights:

• Booking Reference ID: Allows the team to pull up the exact transaction.
• Cleaner’s Name: Needed if the complaint is about a specific cleaner.
• Payment Method: Helps detect patterns (e.g., PayPal errors vs. card declines).

Improvement Consideration:

• Including "Was the cleaner informed about any special requests?" could help with service disputes.

5. Technical Information

Purpose:

• Identifies device-specific bugs (e.g., crashes only on iOS 16).

Key Insights:

• Device Type & OS Version: Helps pinpoint compatibility issues.
• App Version: Critical for determining if the user is on an outdated/buggy release.
• Internet Connection: Rules out connectivity-related failures.

Improvement Consideration:

• Adding "Did you try reinstalling the app?" could help rule out corruption issues.

6. Error Messages/Screenshots

Purpose:

• Provides visual proof of the issue (e.g., payment error codes).

Key Insights:

• Error Messages: Often contain codes that developers can cross-reference with logs.
• Screenshots: Helpful for UI/UX bugs (e.g., buttons not loading).

Improvement Consideration:

• A note like "Where did the error appear? (e.g., checkout screen, booking history)" could add clarity.

7. Additional Comments

Purpose:

• Captures unstructured feedback that may not fit elsewhere.

Key Insights:

• Users may describe workarounds they tried or emotional context (e.g., "This is the third time this happened!").

Improvement Consideration:

• Adding a satisfaction pre-rating (e.g., "How urgent is this issue?") could help prioritize responses.

Support Team Follow-Up (Internal Use)

Purpose:

• Streamlines internal workflows for tracking and resolution.

Key Insights:

• Issue Category & Priority: Ensures high-impact problems (e.g., payment failures) are escalated quickly.
• Resolution Notes: Helps maintain a knowledge base for recurring issues.

Improvement Consideration:

• Adding "Root Cause" (e.g., "API timeout," "Cleaner unresponsive") could improve analytics.

Overall Benefits of This Form

1. Faster Resolution: Structured data reduces back-and-forth emails.
2. Better Prioritization: Clear categories help triage critical issues.
3. Data-Driven Improvements: Identifies recurring bugs (e.g., "30% of crashes happen on Android 13").
4. User Confidence: Shows professionalism and thoroughness in support.

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.

(These fields are essential for efficient troubleshooting and ensuring a timely resolution.)

1. User Information

Mandatory Fields:

Email Address
User ID (if available)

Why?

• Email Address → Required for authentication, follow-up communication, and sending resolution updates.
• User ID → Helps instantly pull up the user’s booking history, transactions, and account details in the database.

Optional But Recommended:

• Full Name → Helps personalize support but isn’t always mandatory if the email/ID is sufficient.
• Phone Number → Critical for urgent issues (e.g., cleaner no-show) but not always mandatory for technical bugs.

2. Type of Issue

Mandatory Field:

At least one selection from the issue checklist

Why?

• Ensures the request is categorized correctly (e.g., technical vs. booking-related).
• Helps route the ticket to the right team (e.g., developers for crashes, customer service for refunds).

3. Booking Details (For Booking-Related Issues)

Mandatory Fields:

Booking Reference ID
Scheduled Cleaning Date & Time

Why?

• Booking Reference ID → The primary key to track the exact booking in the system.
• Scheduled Date & Time → Confirms whether the issue is about an upcoming, ongoing, or past booking.

Optional But Recommended:

• Cleaner’s Name → Needed if the complaint is about a specific cleaner.
• Payment Method → Helps detect payment gateway failures.

4. Technical Information (For App Crashes/Errors)

Mandatory Fields:

Device Type (iOS/Android)
App Version

Why?

• Device Type → Many bugs are OS-specific (e.g., crashes only on iPhones).
• App Version → Critical for identifying if the user is on an outdated or buggy release.

Optional But Recommended:

• Operating System Version → Some bugs occur only on specific OS versions (e.g., Android 13).
• Internet Connection Type → Helps rule out connectivity-related failures.

5. Error Messages/Screenshots (For Technical Issues)

Mandatory Field:

"Have you received any error messages?" (Yes/No + Description if Yes)

Why?

• Error messages often contain codes that developers can cross-reference with logs.
• If the answer is "No", the support team knows to look for other causes (e.g., silent crashes).

Optional But Recommended:

• Screenshot Upload → Visual proof is invaluable for UI/UX bugs.

6. Detailed Problem Description

Mandatory Field:

"What were you trying to do when the issue occurred?"

Why?

• Provides context (e.g., "Tried to book a cleaner but the app froze at checkout").
• Without this, the support team may waste time guessing the problem.

Optional But Recommended:

• Steps to Reproduce → Extremely helpful for developers but not always mandatory.
• Frequency of Issue → Helps distinguish one-off glitches from systemic bugs.

Why These Fields Are Mandatory?

1. Prevents Back-and-Forth Emails → Users provide all critical details upfront.
2. Faster Resolution → Support can immediately investigate instead of asking for basic info.
3. Better Ticket Routing → Ensures the issue goes to the right team (e.g., technical vs. operations).
4. Data Integrity → Mandatory fields ensure no key details are missing in support logs.

Optional But Highly Recommended Fields

• Phone Number → For urgent issues (e.g., cleaner no-show).
• Screenshots → Visual proof accelerates debugging.
• Steps to Reproduce → Crucial for developers fixing bugs.