Design concept · signup and pricing are not connectedCurrent version

The product

Run the visit.
Understand the operation.

SlotLogix connects the work before, during and after a booking, with tools for the people running the fields.

Before a visit

Make the available
time work for your site.

Set opening hours and booking durations for each field. Configure pricing and supported rules, and let visitors choose from the available times.

Eligible gap-filling and shared-access features can account for buffers and site constraints where enabled.

Availability and pricing

Around the booking

Keep the visit
and its detail together.

Take online payments through Stripe, manage supported credit and promotions, and work from the original booking when arranging a refund.

Visitors use their secure link to check details or reschedule within your rules.

Payments and visitor tools

On the ground

Manage the arrival,
the message and the team.

Configure gate codes and access windows, review communication deliveries, and give team members the permissions they need.

Booking-linked incident reporting and supported travel warnings add context where those features are enabled.

Access and operations

Beyond the calendar

Turn activity into
something you can use.

Review utilisation, compare reporting periods and explore demand. Advisory findings can explain why something was flagged and suggest where to investigate next.

The operator decides what to change. Suggestions do not automatically alter prices or opening hours.

Reporting and insights

Built for the practical details

Two fields.
One shared entrance.

A free slot is only useful if the arrival works. Shared-access rules can account for the space and time visitors need around a visit.

Explore smarter availability

Example site arrangement

Field OneField Two
Shared entrance & car park

Configure arrival and departure separation around the layout of your site.

Illustrative arrangement. Shared-access features require the relevant configuration and enabled access.

One practical example

Taking bookings.
Still finding quiet time.

How an operator can move from an observation to a considered decision, using the reporting and insight workflow.

1 / Establish the position

Compare booked and available time.

A booking count needs context. Utilisation helps show how much of the configured opening time is being used.

2 / Investigate the pattern

Look at the evidence.

A supported insight includes the finding, its explanation and evidence. Use reporting to investigate the periods that need attention.

3 / Decide what to change

Keep control of the next step.

Review pricing or opening hours, or leave them as they are. Findings can be snoozed, dismissed or marked as acted on.

This describes a supported advisory workflow, not a customer result or a promise of improved revenue. Reporting and insight access depend on enabled features and data coverage.

Make it yours before you launch.

Prepare your fields and explore the experience first. Subscribe when you are ready to accept real bookings.

See how setup works