Support Tickets in FlexBookz

Introduction

The Support Tickets feature in FlexBookz lets you submit, track and manage requests for help from the FlexBookz support team. It is designed to keep support conversations organized, provide visibility into progress, and speed up resolution of issues related to scheduling, payments, integrations, or account settings. This documentation explains how the system works, provides step-by-step instructions for creating tickets, includes practical examples and use cases, and offers tips and troubleshooting guidance.

How it Works

The support tickets system is the central communication channel between your business and our support engineers. Each request becomes a ticket with a unique reference number and a set of attributes you can use to describe urgency and context. Tickets allow you to exchange messages, attach files such as screenshots or logs, and track status changes from Open to In Progress to Resolved.

Key Ticket Elements

• Ticket number: A unique identifier (for example #TICKET-2025-0001).

• Subject: Short title describing the issue.

• Description: Detailed explanation, steps to reproduce, and expected vs actual behavior.

• Status: e.g. Open, In Progress, Resolved, Closed.

• Priority: Low, Medium, or High, indicating urgency.

• Category: e.g. General Question, Technical Bug, Billing.

• Attachments: Screenshots, logs, or exported CSVs to illustrate the issue.

Examples and Use Cases

• Booking widget not loading: Customer reports the booking widget returns a 404 or displays a blank area on their website.

• POS integration issue: Transactions recorded in the POS are not syncing with FlexBookz orders.

• Staff availability mismatch: Staff appears available in the system but clients cannot book specific time slots.

• Billing question: A discrepancy in an invoice or subscription charge.

Tip: When possible, include the URL, screenshots, browser version, and a short sequence of steps to reproduce the issue — it significantly reduces resolution time.

Step-by-Step Guide

1. Open the left navigation and go to Support > Support Tickets.

2. Click the + Create Ticket button to open the new ticket form.

3. Complete the ticket form fields:

   • Subject: Write a concise title (e.g. Booking widget fails to load on mobile).

   • Description: Provide a detailed explanation. Include steps to reproduce, expected result, and actual result. Example template:

     Issue Summary:
     Steps to Reproduce:
     1. Go to https://example.com/booking
     2. Click the "Book Now" button
     Expected Result:
     Booking widget opens
     Actual Result:
     Blank area shown; console shows 404 to /widget.js
     Browser/Device:
     Chrome 117 on Android 14
     Attachments:
     screenshot.png, console.log
     

   • Category: Select the most relevant category (Technical, Billing, Account).

   • Priority: Set priority based on business impact (Low, Medium, High).

   • Attachments: Upload screenshots, exported logs, or CSVs that demonstrate the problem.

4. Click Submit to create the ticket. You will receive a confirmation message and a ticket number (for example #TICKET-2025-0420).

5. Track the ticket in the tickets overview. Use filters to view tickets by Status, Priority, or Category.

6. Reply to comments from the support team inside the ticket thread. Attach any follow-up files or additional logs directly to the ticket.

7. When the issue is resolved to your satisfaction, mark the ticket as Resolved or Closed depending on your internal process.

Tips & Best Practices

• Use a clear subject line: A concise subject helps engineers triage faster (e.g. Inventory not updating after sale).

• Provide reproducible steps: Describe exact steps, environment (browser, device), and any recent changes (new plugins, API keys rotated).

• Attach evidence: Screenshots, exported CSVs, or browser console logs are often crucial for diagnosing issues.

• Set an accurate priority: Reserve High priority for outages or issues that stop revenue generation or operations.

• Search first: Check the Helpdesk & FAQ and existing tickets for similar issues to avoid duplicates.

• Keep communications in one place: Use the ticket thread rather than separate emails to avoid losing context.

• Link related records: If the issue affects a specific client or location, reference the customer or location ID and link to the CRM record.

• Follow up respectfully: If you need to escalate, add a comment explaining the business impact and request prioritization.

Troubleshooting

• Cannot create a ticket: Verify you are logged in and have support permissions. Admins can manage user roles under Account Settings > Users.

• Ticket missing from overview: Check active filters at the top of the tickets list (Status, Priority, Date range) and reset them to show all tickets.

• No updates on a ticket: First check if the support team has requested more information. Add the requested details or reach out using your account contact channels.

• Attachments fail to upload: Ensure file sizes are within limits and the file type is allowed. Try compressing large screenshots or zipping log files before uploading.

• Incorrect status shown: Refresh the page or re-open the ticket. If the status still seems wrong, comment on the ticket to request clarification.

• Urgent business-impacting issue: If response time is critical, mark the ticket High priority and include explicit impact details (expected revenue loss, number of affected customers). If you have a support SLA or a dedicated account manager, copy them in the ticket.

If you need further assistance or have feedback about the support experience, open a ticket and describe your suggestion — we use customer feedback to improve our support workflows and the FlexBookz platform.