Thank you for contacting support!
Please fill out this form with as much detail as possible to help us resolve your issue efficiently.
(Required for account verification and follow-up)
Full Name:
Email Address:
Phone Number:
Account Number:
(Helps us identify the app version and platform)
App Name:
Platform:
iOS (Apple App Store)
Android (Google Play Store)
Web Browser
Other:
App Version:
Device Model:
Operating System Version:
(Select the most relevant category)
Login/Account Issues (Forgot password, account locked, etc.)
Booking & Scheduling Problems (Can't book, wrong time slots, double bookings)
Payment Issues (Failed transactions, refund requests)
Notifications Not Working (No confirmations, reminders, or alerts)
App Crashes/Freezes (App closes unexpectedly or becomes unresponsive)
Performance Issues (Slow loading, lagging)
Service Provider Issues (No availability, wrong details)
Cancellation/Refund Problems
Other:
(Provide as much detail as possible)
When did the issue first occur?
Steps to Reproduce the Issue (What were you doing when the problem happened?)
Steps You Took | ||
|---|---|---|
1 | ||
2 | ||
3 | ||
4 | ||
5 |
Error Messages Received (If any, please provide exact wording)
Have you tried any troubleshooting steps? (e.g., restarting the app, reinstalling, checking internet)
How frequently does this issue occur?
Every time
Occasionally
First time
(Helpful for diagnosing the issue)
Internet Connection Type:
Wi-Fi
Mobile Data
Other:
Screenshots/Video Recording (Upload if possible)
File Name | Upload File | ||
|---|---|---|---|
1 | |||
2 |
Booking Reference Number (if applicable):
Phone Call
In-App Chat
Once completed, please submit this form, and our support team will respond as soon as possible.
Thank you for your patience and cooperation!
App Support Form Insights
Remove this app support form insights section before publishing.
Here’s a detailed breakdown of the Service Booking App Support Form, explaining the purpose, structure, and reasoning behind each section to ensure effective troubleshooting and customer support:
Purpose:
Key Insights:
Why It Matters:
Without this, support cannot confirm legitimacy or access account-specific data (e.g., past bookings, payment history).
Purpose:
Key Insights:
Why It Matters:
A crash on an iPhone 15 running iOS 17 could differ from the same crash on an older device, requiring tailored fixes.
Purpose:
Key Insights:
Why It Matters:
Prioritizes high-impact issues (e.g., payment failures over UI tweaks).
Purpose:
Key Insights:
Why It Matters:
Vague descriptions ("App doesn’t work") delay resolution. Structured steps save time.
Purpose:
Key Insights:
Why It Matters:
A screenshot of a payment error with a timestamp can pinpoint backend failures.
Purpose:
Key Insights:
Why It Matters:
Improves customer satisfaction by aligning with their comfort level.
Mandatory Questions Recommendation
Please remove this mandatory questions recommendation before publishing.
To ensure efficient troubleshooting and timely resolution, the following fields should be mandatory (marked as required) in the support form. Each serves a critical purpose in diagnosing and resolving issues effectively.
Full Name – Ensures accountability and personalized support.
Email Address – Required for follow-up communication and ticket tracking.
Why?
Phone Number & User ID – Optional because:
App Name – Critical to identify which app has the issue (if the company offers multiple).
Platform (iOS/Android/Web) – Determines OS-specific troubleshooting steps.
App Version – Bugs may be version-specific; updates often fix known issues.
Device Model & OS Version – Helps replicate the issue (e.g., "iPhone 15 on iOS 17.4").
Why?
Select a Problem Category – Routes the ticket to the right team (e.g., payments vs. technical).
Why?
Steps to Reproduce the Issue – Essential for debugging (e.g., "App crashes after clicking ‘Pay Now’").
Frequency of Issue – Indicates severity (e.g., "Every time" vs. "Occasionally").
Why?
Error Messages – Optional if none appear, but highly recommended.
Booking Reference Number – Required only for booking/payment issues to pull transaction logs.
Why?
Screenshots – Optional but strongly encouraged for visual bugs.
How to Contact You – Ensures support responds via the user’s preferred channel.
Why?