Zapof

Support for Your Accommodation App

This form is designed to help our support team gather all the necessary information to quickly and efficiently resolve any issues you may be experiencing with our accommodation application. Please provide as much detail as possible.

1. Contact and Account Information

Your Full Name:

Your Account ID:

Email Address Associated with Your Account:

2. Technical Information

App Name and Version:

Device Type and Model:

Operating System (OS) and Version:

Internet Connection Type:

3. Issue Details

Type of Issue (please select all that apply):

Please provide a detailed description of the problem: (What were you trying to do? What happened instead? When did you first notice this issue?)

Step-by-Step Instructions to Reproduce the Issue: (Please list the exact steps you took before the issue occurred. For example: 1. Opened the app. 2. Searched for "Paris". 3. Tapped on the first listing. 4. The app froze.)

Any Error Messages Received: (Please provide the exact text of any error messages, even if they seem unimportant.)

How often does this issue occur?

4. Booking/Reservation Information

Booking Reference Number:

Accommodation Name:

City and Country of Accommodation:

Check-in Date:

Check-out Date:

Did the booking appear as "Confirmed" in your app?

5. Payment/Billing Information

Date of Transaction:

Transaction Amount:

Last 4 digits of the payment method used:

What is the status of the transaction in your bank or card statement?

Did you receive a payment confirmation email?

6. Screenshots and Attachments

Please attach any relevant screenshots or a short video demonstrating the issue. Screenshots of the problem, any error messages, or payment confirmations are very helpful.

Description / File Name

Upload File

A
B
1
 
 
2
 
 
3
 
 
4
 
 
5
 
 
 

By providing this information, you are helping us to quickly diagnose and fix the problem. Thank you for your patience and for helping us improve the app!

App Support Form Insights

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.



The form is very well-designed and follows several key best practices for creating a powerful and user-friendly support tool.

Strategic Structure and Flow

The form's greatest strength is its logical and intuitive flow. By breaking down the request into distinct, numbered sections (1 to 6), it guides the user through the process without overwhelming them.

  • Section 1 (Contact) & Section 2 (Technical): These are placed first because they are the most critical for initial ticket creation and triage. A support agent can immediately identify the user and their technical environment, which are often the first things needed to begin troubleshooting.
  • Section 3 (Issue Details): This is the core of the form. The use of checkboxes for issue types and the follow-up, open-ended questions about reproduction steps and error messages is highly effective. It combines the speed of pre-defined categories with the crucial detail of free-form text.
  • Section 4 (Booking) & Section 5 (Payment): Placing these sections after the general issue details is an excellent example of progressive data collection. Not every user will have a booking or payment issue. By labeling these as "if applicable," the form avoids a cluttered, intimidating wall of fields for the majority of users.
  • Section 6 (Attachments): This is strategically placed at the end as a final, optional, but highly valuable piece of information. The prompt explicitly encourages screenshots, which can drastically reduce resolution time.

Emphasis on Actionable Data

Every question in the form is designed to collect data that is immediately useful for the support team.

  • Device and OS Information: This is essential for debugging. Issues often vary across different platforms (e.g., iOS vs. Android) or even specific OS versions.
  • Step-by-Step Instructions: This is the most valuable part of the form for a developer or QA team. It provides a clear, repeatable path to reproduce the bug, eliminating the need for a lengthy back-and-forth conversation with the user.
  • "One-time vs. Happens every time" question: This simple question helps the support team differentiate between a transient server-side issue or network glitch and a persistent, client-side bug that requires a code fix.

Mandatory Questions Recommendation

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.


Here is a breakdown of the functionally mandatory questions and why they are so critical:


  1. Email Address: This is the most crucial piece of information. It allows the support team to find your account in their system, verify your identity, and, most importantly, reply to you with a resolution or follow-up questions.
  2. App Name and Version, Operating System (OS) and Version: These are essential for debugging. Issues can be specific to certain app versions or operating systems. Knowing this information helps the support team quickly determine if it's a known bug with a specific build or if the issue is unique to your device.
  3. Type of Issue: This helps the support team categorize the problem immediately and route the ticket to the correct team (e.g., a technical developer vs. a billing specialist).
  4. Detailed Description of the Problem: This is the heart of the support request. A detailed description gives the support team the context they need. Without it, the other information on the form is just data without a purpose.
  5. Step-by-Step Instructions to Reproduce the Issue: This is the single most important piece of information for engineers. It allows them to replicate the problem on their end, which is the fastest and most efficient way to diagnose the root cause and fix it.

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.