Support

Before contacting Flo support, it is useful to run a few checks. This helps quickly distinguish a usage issue from a technical anomaly.

First check

Check:

• whether the issue affects a single user or everyone;
• whether it happens on desktop, mobile, or both;
• whether the user has the correct role;
• whether the requested feature is active for your company;
• whether there are filters, dates, or statuses hiding the result;
• whether the issue persists after signing out and back in.

Information to send

When you open a request, include:

• company name;
• email of the user involved;
• page or section where the issue appears;
• action you were attempting;
• expected result;
• actual result;
• approximate date and time;
• screenshot or short video.

If the issue concerns bookings, also add the date, time, service, and user name.

If it concerns properties, add the internal code or property title.

Priority

Flag as urgent only issues that truly block operations, for example:

• all company users unable to sign in;
• inability to manage the day's bookings;
• critical data not visible or not editable;
• incorrect publication of sensitive information.

Non-blocking requests can be handled as improvements or routine checks.

Change requests

When asking for a functional change, try to describe:

• which operational problem you want to solve;
• who uses that feature;
• how often it happens;
• what the desired behavior would be;
• whether there is a real deadline.

The clearer the context, the easier it is to evaluate the best solution.