TOURPAQ SUPPORT
Welcome to the Tourpaq Support Guide!
At Tourpaq, we are dedicated to ensuring that you, as our valued user, have the best experience possible with our platform. Your satisfaction is at the core of what we do, and we strive to provide outstanding support to match.
However, in order to assist you effectively and resolve any issues as quickly as possible, we need your cooperation and commitment to follow the guidelines laid out in this guide. You play an essential role in this process. Your clear and detailed description of any bug or issue helps our team understand the problem, pinpoint the cause, and work towards a swift solution.
Below we have made a guide designed to walk you through the process of creating a proper support ticket and to highlight the information that will be most helpful to us. By adhering to these guidelines, you empower our team to provide you with the timely and effective assistance you deserve.
General Tips:
Be Clear and Concise: Use plain language and be as specific as possible without unnecessary jargon.
UseBullets or Numbering: Organize information in a way that's easy to read and follow.
Attach Supporting Materials: If you're referring to documents or other files, make sure to attach them to the ticket.
Be Patient and Courteous: Our developers will get to your issue as soon as possible. Being respectful and understanding can foster better communication.
Thank you for your cooperation!
Welcome to the Tourpaq Support Guide!
Followt hese steps to create a support ticket that will facilitate a swift andefficient response from our support & development team:
Subject Line: Clearly describe the issue in the subject line. A well-written subject helps our developers understand the problem at a glance.
User Information: Provide your name, contact details, and role, in case the support team needs to reach out for further clarification.
Description of the Issue:
Summary: Provide a concise summary of the problem.
Detailed Description: Describe the issue in detail, including any error messages, unusual behavior, and when the problem first occurred.
Steps to Reproduce: List the steps taken that led to the issue. If possible, include screenshots or videosto illustrate the problem.
System Information: Share information about the operating system, browser (if applicable), and any other relevant system details that could affect the software's performance.
Log Files: If possible, attach relevant log files or snippets of logs that capture the error. This can provide critical insights into the problem.
Expected Behavior: Describe what you expected to happen, as this can help developers understand what went wrong.
Attemptsto Resolve: Share any steps you've already taken to resolve the issue, along with the results. This can prevent duplicate efforts and provide additional context.
Additional Information: Include any other information that might be helpful, such as related incidents, specific configurations, or previous correspondence on the issue.
Have any question?
Do you offer dedicated support?
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nec urna pellentesque integer adipiscing ullamcorper ornare est. Vitae neque, turpis diam condimentum. Ultrices non ac consequat, etiam. Egestas mauris eget aliquet eget neque. Blandit semper fermentum quisque.
Do you offer discounts for startups?
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nec urna pellentesque integer adipiscing ullamcorper ornare est. Vitae neque, turpis diam condimentum. Ultrices non ac consequat, etiam. Egestas mauris eget aliquet eget neque. Blandit semper fermentum quisque.
Can I request a higher tier plan?
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nec urna pellentesque integer adipiscing ullamcorper ornare est. Vitae neque, turpis diam condimentum. Ultrices non ac consequat, etiam. Egestas mauris eget aliquet eget neque. Blandit semper fermentum quisque.
Is your product GDPR-compliant?
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nec urna pellentesque integer adipiscing ullamcorper ornare est. Vitae neque, turpis diam condimentum. Ultrices non ac consequat, etiam. Egestas mauris eget aliquet eget neque. Blandit semper fermentum quisque.