Connect
Booking tool10:30 · party of four
Record arrives with source and timestamp
Product · Patron operations
The shared patron record. Every part of the venue.
Wayside joins bookings, waivers, POS transactions, activity, and memberships around the person. Staff see the arrival; operators record the next decision; later visits can be traced back.
PROPERTY ROUTE
01Arrival
02Range bay
03F&B counter
04Event desk
05Monday review
System architecture
Connect the shift. Carry the patron record.
Provider systems remain authoritative for bookings, payments, waivers, and activity. Wayside joins the approved fields needed at the next staff handoff.
AVERY · SATURDAYBOOKING → DESK → DECISION → LATER VISIT
Recognize
WaysideAvery · active member
Staff see identity, access, and recent visits
Act
Shift leadWelcome + next step
A named operator records the decision
Measure
WaysideVisit · +12 days
Response and visit each keep their own time
PROVIDER OWNERSTAFF HANDOFFRECORDED RESULT
Three operating responsibilities
01
Know the patron
Give whoever greets the guest identity, membership, household, recent visits, and the source behind each fact.
02
Run the visit
Put arrivals, access changes, event inquiries, and expiring value in front of the staff member responsible for them.
03
Trace what followed
Keep the operator’s decision, the patron’s response, and the next recorded visit as separate events, each with its own time.
LIVE FOUNDATION
Shared foundation
The record no single system can build.
BOOKING · PURCHASE · WAIVER · MEMBERSHIP · VISIT
A booking, order, waiver, membership, and range session can belong to Avery while each provider remains authoritative for its own record.
- Every event shows its provider and timestamp
- Every recommendation shows its operator decision
- Every module reads from the same patron registry
Available now. The shared patron relationship is the foundation every module reads from.
OPERATOR REVIEW
The Return Worker
Approve one draft at a time. Then approve the workflow.
The Return Worker prepares a draft from approved context: an attended event, expiring access, a quiet regular. The owner or shift lead edits, approves, or skips it. Once a workflow has proven itself, they approve it for a whole segment and review the exceptions.
The approved action, the response, the return signal, and the outcome stay on the same patron record, each with its own time.
A Wayside Return Worker draft waiting for the operator to approve, edit, or skip it
At the desk, on a phone
The same record, in a back pocket.
The operator app runs on a phone at the door, the range bay, or the patio. Overview, Today, and the patron record are the same views the office sees, sized for a shift.
Everfield Club & Grounds · demo venue
01LIVE FOUNDATIONPatron record 02FIRST HANDOFFStaff view 03NEXT SURFACEAfter evidence
Rollout plan
Prove a handoff. Then add another surface.
- 01
Trace the arrival Name the booking, provider, staff desk, and missing fact.
- 02
Connect the minimum fields Bring in the exact source data required at that handoff.
- 03
Put the view on shift Test it with the staff member who owns the next decision.
- 04
Record the result Record what changed before another module is added.
What runs on the record
Six surfaces. One record. Every action in order.
The record is the product. Each surface reads from it and writes back to it, with the source of every fact visible and the venue where it runs named.
- Connected
- Every connected system keeps its own record. Wayside reads approved fields and names their source, so the register, the booking tool, and the waiver flow stay exactly where they are.
- Configured
- Each venue turns on the surfaces it needs, with rules and staff views set for that property.
- Reviewed
- The Return Worker prepares the draft; the owner or shift lead approves, edits, or skips it. Response and return are recorded when the venue records them.
RECORD Shared patron record One patron across every connected system
DESK Today operating view Arrivals, expiring access, and changes sorted for the shift
MODULES Venue modules Memberships, bookings, events, ordering, experiences, stored value; switched on per property
WORKER Return workflow The Return Worker drafts; the operator approves, edits, or skips before anything goes out
WORKER Visit coordination Household, dependents, room, and timing on one itinerary
RECEIPT Outcome receipt Approved action, response, return, and outcome on one record, in order
A few useful answers
Before we map your venue.
The short version of the platform, the connections, and how work starts on your property.
What is Wayside?
Wayside is patron operations software for experience venues. It joins bookings, purchases, memberships, visits, and messages on one patron record, giving staff the history behind a guest's arrival and operators a place to choose the next action.
Find your kind of venueDoes Wayside replace our POS or booking system?
No. Your POS, booking, and waiver tools keep their own records. Wayside joins approved activity from those systems around one patron; venue modules add the operating surfaces your property needs.
See the venue modulesWhich systems connect to Wayside?
Clover, Select Pi, Square, Stripe, Google Workspace, and Mailchimp are connected integrations, activated per venue. Each connection has venue-approved access, a defined set of fields, and a test on your property.
Explore the connection boardWho decides what gets sent to a patron?
The Return Worker prepares a welcome, renewal, invitation, or follow-up from recorded patron activity. The owner or shift lead approves, edits, or skips it. Responses and later visits stay with the decision as the venue records them.
See the return workflowWhere is Wayside running?
Wayside runs at The Acres in Cincinnati, where mini golf, a driving range, food and drink, events, and memberships share one property. Clover commerce and Select Pi range activity feed the patron record.
Read The Acres field studyHow do we get started?
Start with a 20-minute working session with a Wayside founder. Bring the systems you run and one real reservation, visit, or membership change. Leave with the first connection worth testing mapped out.
Map your venueBring the desk where the record breaks.
Map your venue →
Leave with the provider, fields, staff view, and first test marked. A working session with a founder. No sales demo.