How can we help?

Account roles control access to areas such as bookings, customers, reports and settings. Review team access regularly and remove permissions no longer needed.

Only account users with settings permission should change the field-owner profile, payment setup and other operator-wide configuration.

Use individual user accounts, strong passwords and two-factor authentication where available. Never share Stripe credentials or customer exports through insecure channels.

Use customer data only for legitimate field operations and consented marketing, keep access limited and follow applicable data-protection law and DogFieldHQ terms.

Include the operator name, page, booking or record ID, approximate time, steps taken, expected result and any safe screenshot. Remove card details and unnecessary personal data.

No. Use the appropriate emergency service for immediate danger and your own on-site procedure for field incidents. Contact DogFieldHQ for platform and account support.

Email support with the workflow, problem, frequency and desired outcome. That context is more useful than a solution alone and helps DogFieldHQ assess the request.

FAQ content is structured and version controlled with the application. It is reviewed through code changes rather than edited in a separate FAQ administration dashboard.

Edit the field's recurring availability and set opening and closing times for the days you operate. Available slots are generated from those windows.

Use a date-specific availability override for seasonal or exceptional hours. Review the resulting customer slots after saving.

Create a field closure covering the relevant date or time range. Closures block overlapping slots without changing the normal weekly schedule.

Yes. The location availability policy can prevent customers from booking sessions that begin too soon.

Yes. Set the maximum booking-advance window in the location's availability policy. Dates beyond it are not offered.

Yes. Configure the booking buffer in the location availability policy. Slot generation uses it to keep sessions apart.

Slot checks consider active bookings, holds, closures, hours and buffers. The database also enforces an overlap constraint for active booking records.

A field must be visible to accept customer bookings. Turn it on only when its details, prices, schedule and payment setup are ready.

Users with booking permission can add an operator booking, select or create the customer and dog records, then choose an available field and session.

Operator bookings can be edited using the available booking controls and permissions. Availability is checked when date, time, field or duration changes.

Open the booking and use the cancel action if your role allows it. Record a clear reason and handle any payment refund separately where appropriate.

A customer can request cancellation for an eligible future booking. Review the pending request and approve or decline it; approval cancels the booking but does not silently promise a refund.

Open a paid booking and use the refund control. DogFieldHQ supports full or partial refunds up to the remaining refundable Stripe amount.

No. Ordinary direct-charge customer refunds retain the application fee. Refunding an application fee is a separate platform decision so it cannot happen accidentally.

Customer records bring together contact details, dogs, booking history, spend summaries, activity notes and relevant sent emails within your operator account.

Yes. The operator customer area supports search and practical filters so you can find records without browsing every customer.

Use the customer activity controls to record appropriate operational notes. Avoid sensitive or unnecessary personal data.

Users with the relevant access can send an email from the customer record. Sent messages are recorded for operational context.

Create an operator account, add your operator profile, location and at least one field, configure availability and pricing, connect Stripe and review your launch checklist.

Add the trading name, contact email, website and brand settings customers need. Keep contact details current because they support customer communication and Stripe setup.

From the operator area, create a location and complete its address, arrival information, marketplace description and other available settings.

Open a location and add a field. Configure its name, description, visibility, durations, prices, capacity, fence details, rules and availability.

Yes. Use the duplicate action on a field to create a starting copy, then review all details, pricing and availability before making it visible.

It shows whether key operator, location, field, availability, payment and marketplace information is complete. Treat it as a readiness guide, not a replacement for reviewing your listing.

DogFieldHQ supports account users and roles. Give each person their own access and only the permissions they need for bookings, customers, reports or settings.

Email support@dogfieldhq.co.uk with the operator name, relevant booking or record ID, what you expected and what happened. Never include full card details.

The dashboard summarises operational status, field readiness, booking activity and useful next actions for the current operator account.

Today provides an operational view of the day's bookings and field activity so staff can see what is happening next.

Yes. Use the operator bookings workspace to narrow records by the available status, date and field controls.

The reports area calculates booking count, revenue, average order value, utilisation and related period comparisons from counted bookings and payments.

Booking revenue, application fees, refunds, Stripe processing and payout timing are different measures. Use booking payment records together with the Stripe Dashboard when reconciling.

DogFieldHQ records booking source and creator context. Marketplace and settlement reporting can focus on customer-originated counted bookings.

DogFieldHQ records audit and activity information for selected operational and platform actions. Coverage depends on the action; do not treat it as a substitute for your own compliance records.

The operator area includes birthday, review-request and return-customer journeys. Configure content and eligibility carefully and respect customer preferences.

Edit the field, enable the durations you offer and enter a price for each enabled duration. A duration must have a valid price before the field can use it.

Yes. Duration flags and prices belong to each field, so fields at the same location can be configured differently.

Open Discounts in the operator area and create the code using the available value, validity and usage settings. Review it before sharing it with customers.

Yes. Discount records support controlled validity. A code outside its allowed conditions will not be applied to a new booking.

Existing bookings keep their recorded cost and fee snapshot. Price changes apply when later bookings are created.

Yes. Fee handling is configured for the location. Choose whether the fee is added to the customer's base price or absorbed from the operator amount.

Open your operator settings and start Stripe Connect onboarding. Complete the information Stripe requests, then return to DogFieldHQ so the account status can be refreshed.

Customer card payments are created for the operator's connected Stripe account. Stripe handles payment processing, verification and the operator's payout relationship.

DogFieldHQ tracks whether the connected account can accept charges and receive payouts, plus whether Stripe reports outstanding requirements. Follow the prompt to complete missing Stripe information.

Operator-owned Standard connected accounts are managed by signing in at dashboard.stripe.com. DogFieldHQ links bookings to payment status but does not replace the Stripe Dashboard.

Yes. Return to the Stripe Connect area and continue onboarding. DogFieldHQ creates a fresh account link when needed because Stripe onboarding links expire.

A successful Stripe payment is recorded against the booking with amount, currency, charge or payment-intent references, application fee and payment status.

Your configured percentage and fixed amount are snapshotted on the booking. Location settings determine whether the customer pays that fee on top or you absorb it.

DogFieldHQ uses connected-account direct charges for marketplace bookings. The operator's connected account owns the charge while DogFieldHQ can collect its configured application fee.

A customer-created booking may briefly reserve availability while payment completes. If the hold expires without successful payment, it can be marked abandoned so the slot becomes available again.

Use the operator payment view for booking payment records and Stripe for settlement and payout detail. DogFieldHQ also maintains platform settlement reporting for operational reconciliation.

Use your public DogFieldHQ location URL behind a Book now link or button on your website, social profile or customer messages.

Yes. DogFieldHQ provides an embed script and location availability widget. Customers choose available details in the widget and continue into the secure booking flow.

The widget requests availability from DogFieldHQ for the selected location and field, so closures, bookings and configured policies affect the slots shown.

Complete the operator, location and field details, images, pricing, availability, access guidance and Stripe readiness, then review the marketplace checklist.

Use the review request in operator settings after completing the launch checklist. DogFieldHQ reviews the listing before approval.

No. Submission and approval are separate. The platform can keep an operator or location out of discovery until review is complete and marketplace visibility is enabled.

Manage images from the location area. Use accurate, current images that help customers understand access, boundaries and facilities.

Operator settings support branding colours and related presentation details. Check contrast and readability after changes, especially for customer booking pages.