Help that is actually organised.

Understand the platform roles and the fastest way to start.

• Clients use NextSlot to discover barber shops, choose a barber or service, book appointments, join a live queue where enabled, manage bookings and contact support.
• Barber owners manage their shop profile, team, services, opening hours, availability, appointments, walk-ins, clients, products and business settings.
• Super Admin controls the overall platform, shops, owners, subscriptions, settings, media, integrations, releases, support tickets and system configuration.

Step-by-step booking flow for clients.

• Choose a locality or search for a barber/shop, then open the shop profile and select the required service.
• Select an available barber if the shop allows barber choice, or let the shop assign one when that option is enabled.
• Choose an available time slot, review the service, duration, price and booking details, then confirm.
• After confirmation, the appointment should appear in booking history and can support confirmation email plus calendar event integration when configured.
• If the shop reschedules or cancels an appointment, the client-facing appointment state should update rather than creating a second booking.

How locality browsing and search should behave.

• Use locality cards to narrow the list of shops by area. Cards should always keep image and text spacing clear on both dark and light themes.
• Search should return relevant shops, barbers or services and show a clear empty state when there is no match.
• If no result is found, clear the search or return to all localities rather than repeatedly submitting the same query.

Using walk-in queue features.

• When enabled by a barber shop, the live queue shows the current waiting state and an estimated position or waiting time.
• Joining the queue should create only one active queue record for the same client/shop session.
• Queue states can include waiting, called, in progress, completed, cancelled and no-show depending on the shop workflow.

Profile, bookings and communication.

• Keep contact details current so booking confirmations and updates reach the correct person.
• Use booking history for upcoming and previous appointments rather than creating duplicate bookings when a page is slow.
• Use Client Support for platform problems and include the exact page, time and screenshot where useful.

The mobile experience and what it is designed to cover.

• The NextSlot mobile app is intended to provide discovery, locality search, shop/barber profiles, bookings, live queue, account management, favourites, notifications and support in one mobile-first experience.
• Calendar integration is designed to support appointment confirmation and changes with Google Calendar and Outlook-compatible flows where configured.
• Push notifications can be used for booking confirmations, reminders, queue updates, reschedules and cancellations when notification services are enabled.
• The app should preserve the same booking and account data as the web platform through the NextSlot backend API.

Daily control for barber owners.

• Start from the owner dashboard to review today’s appointments, walk-ins, queue activity, team availability and operational alerts.
• Use the dashboard as an overview; edit services, staff, opening hours or shop details in their dedicated pages.
• Keep the shop status accurate so clients do not see bookable slots when the business is closed.

Public shop information and discovery.

• Maintain the shop name, locality, address, contact details, description, opening hours and public images.
• Choose the correct locality because it affects how clients discover the shop from locality browsing.
• Use clear current images and verify their crop on mobile after uploading.

Team profiles, schedules and availability.

• Each barber should have an active state, supported services, working schedule and public information where required.
• When a team member is unavailable, block the time or adjust availability rather than deleting historic records.
• Confirm service duration and price because these values affect slot generation and the client booking summary.

Bookable services and duration.

• Create a clear service name, description, price and realistic duration.
• Avoid duplicate services with slightly different names; edit the existing service when possible.
• After changing duration or staff assignment, test one client booking to confirm the available slots are correct.

Appointment operations and external calendar support.

• Use the appointment view to manage confirmed, completed, cancelled, no-show and rescheduled appointments.
• Where calendar sync is configured, updates should propagate instead of creating duplicate events.
• Before changing an appointment manually, check whether a client notification or calendar update is expected.

Operating the live queue.

• Add walk-ins with the correct client, service and barber when known.
• Move queue entries through waiting, called, in progress, completed, cancelled or no-show states promptly.
• Leaving completed clients in waiting state makes estimated queue information inaccurate.

Business-side client records.

• Client records support booking history and operational communication.
• Do not expose or export client information outside approved business purposes.
• Correct duplicates carefully so previous bookings remain connected to the right client.

How barber owners contact NextSlot support.

• Open Support Tickets from the Owner portal and create one ticket per problem.
• Choose the closest category and priority, describe the expected and actual result and add a screenshot if useful.
• Continue replies in the same ticket thread so the complete history remains together.

Super Admin responsibilities.

• Super Admin controls platform-wide settings, shops, users, owners, entitlements, feature flags, integrations, media, releases, support and operational configuration.
• Platform-wide changes should be tested on both desktop and mobile layouts and in both dark and light mode where supported.
• Use deployment backups before replacing shared layout files or global styles.

One canonical footer and logo configuration.

• Footer & Branding is the control point for the footer logo, click-through link, logo size, alt text and footer copy.
• The uploaded footer logo is reused across Admin, Owner, Wiki, Support and public sales pages.
• The logo hyperlink can be an internal path such as /sales/ or a full HTTPS URL.
• V2.4.4 anchors the footer to the bottom of short pages while keeping the same height across platform areas.

Ticket triage and resolution.

• Filter tickets by status, category, priority and search terms, then open a ticket for the complete thread.
• Use Reply for requester-visible communication and Internal Note for staff-only diagnostics.
• Assign tickets, change workflow status and add tags where relevant.
• Close a ticket only when it is resolved or no further action is appropriate.

Safe patch deployment.

• Use the supplied main shell to upload the complete payload, JSON configuration and PHP installer.
• The installer creates a timestamped backup before changing existing root/layout files.
• After a successful installer run, hard-refresh the browser and verify the changed pages independently.
• Do not run the installer if the shell reports any failed upload.

Safe platform use.

• Never send passwords, one-time codes, CVV numbers, full payment-card data or server credentials through support tickets.
• Treat private ticket access links and account reset links like passwords.
• Use the minimum personal information necessary when sharing screenshots or diagnostics.

What to capture when something is wrong.

• Record the page, exact action, expected result, actual result, approximate time and device/browser or app version.
• For visual issues, include whether dark mode or light mode was active and the screen size if known.
• Try one hard refresh after a platform patch before reporting that an old style remains.
• For search problems, report the text entered and what result should have appeared.

What this patch changes.

• Improves light-theme contrast and consistency across shared cards, navigation, fields and footer surfaces.
• Separates locality card images from their text content, repairs the global navigation search interaction and improves empty states.
• Rebuilds the Wiki with a structured desktop/mobile layout and role filtering.
• Anchors the shared footer to the bottom and adds individual detailed sales pages, including a full Mobile App page.