How to Take a Walk-In Booking
Walk-ins double-book the last chair when the desk and the calendar disagree
Two people at the desk can promise the same stylist and chair. A paper diary does not stop the second save. The guest who arrives second waits, and the deposit conversation starts from a booking that should not exist.
A walk-in written only as a customer sale has no start time, no resource, and no check-in. Reports for today’s load and no-shows cannot see it.
Staff who search Sunday through Monday morning accidentally include the next day when the range ends at midnight, so a closed day looks open.
Why this happens
- The walk-in is written outside the front desk, so resources are not checked.
- A named resource is skipped when the offering needs every required type to be free.
- The booking is left unconfirmed and never appears on check-ins due.
- The person’s name is typed with no email or phone, so the next visit cannot match the same party.
Biznsbook addresses this through Front desk, calendar day grid, check-in when Booking Management is licensed — locations, resources, offerings, and hours sit on the same company as parties, sales, and the public booking page.
Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.
Step-by-step: Take a Walk-In Booking
Built for front desks and owners taking appointments, rentals, classes, and stays in Biznsbook Booking Management.
- Open the day calendar. Bookings, then Calendar. The day view lists resources. A free cell opens the front desk for that time.
- Or open Front desk directly. Pick the offering, optionally a named resource, the guest, and the start.
- Save to check in. Save checks the guest in immediately. The booking is no longer only a request sitting on the list.
- Use the list for the rest of the day. Bookings shows today, unconfirmed, and check-ins due. Open a row to confirm, check in, complete, reschedule, cancel, or mark a no-show.
- Repeat when they come back on a pattern. Repeat a booking weekly or every two weeks. You can move one visit or the rest of the series.
- Offer the waitlist when the seat is full. When a seat frees, the next person is offered it until the hold expires.
- Finish the visit. Complete the booking when the work is done. Completing can also issue consumable add-ons through inventory when those add-ons are marked as stock items.
Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen names in this guide match Bookings in the product: Calendar, Bookings, Front desk, Waitlist, Reports, and Settings.
Common mistakes to avoid
- Mistake 1: The walk-in is written outside the front desk, so resources are not checked. Repeating this each month usually shows up first in today's booking list or the no-show rate.
- Mistake 2: A named resource is skipped when the offering needs every required type to be free. Repeating this each month usually shows up first in today's booking list or the no-show rate.
- Mistake 3: The booking is left unconfirmed and never appears on check-ins due. Repeating this each month usually shows up first in today's booking list or the no-show rate.
- Mistake 4: The person’s name is typed with no email or phone, so the next visit cannot match the same party. Repeating this each month usually shows up first in today's booking list or the no-show rate.
Track recurring exceptions in month-end notes; each should map to a control above.
Best practices that hold up as you scale
- Open the day calendar — Bookings, then Calendar.
- Or open Front desk directly — Pick the offering, optionally a named resource, the guest, and the start.
- Save to check in — Save checks the guest in immediately.
- Use the list for the rest of the day — Bookings shows today, unconfirmed, and check-ins due.
- Repeat when they come back on a pattern — Repeat a booking weekly or every two weeks.
Teams that set weekly hours before sharing links, take card deposits into their Stripe account, and keep personal calendars synced as busy blocks avoid double-books and missing Meet links.
How Biznsbook supports this workflow
Front desk is documented in Biznsbook Booking Management capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
calendar day grid is documented in Biznsbook Booking Management capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
check-in is documented in Biznsbook Booking Management capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
Booking permissions cover view, manage, setup, policy override, refund, reports, and sensitive intake answers. Sales, POS, and Accounting are used only when those modules are licensed.
Suggested implementation timeline
- Week 1: Document current process gaps and configure Front desk with finance owner sign-off.
- Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
- Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
- Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
- Ongoing: Monthly review using day-of list and leadership dashboard.
Calendar, list, and front desk
The calendar is the day grid of resources. It does not replace the list. The list is where you confirm, check in, complete, reschedule, cancel, or mark a no-show after the row exists. The front desk is the short path for someone standing in front of you.
Appointment slots need every required resource type to be free unless you pick a named resource. A time-range rental uses the window you enter. A session uses the published occurrence and its seat count. A stay uses the stay dates. A request does not use the slot grid.
After the walk-in is saved
You can record a deposit, send a pay link, send the balance to the open POS session, or create a draft sales invoice when those modules are licensed. Email can include a calendar file. WhatsApp sends when that channel is configured.
Reports then count the visit in today’s load, utilisation, occupancy for stays, revenue booked versus collected, and the no-show rate. Party 360 shows the same booking on the person’s profile.
If the walk-in gives an email or phone that already belongs to a customer, that customer party is linked and the type stays Customer. If nothing matches, the front desk creates a Booker. You can still type a name with no contact details, but the next visit will not find the same party until you add an email or phone. Open the booking afterward to record a deposit or send the balance to the open cashier session.
Metrics to track monthly
- Today's booking count
- Utilisation (booked time over open time)
- Stay occupancy
- Revenue booked versus revenue collected
- No-show rate and deposits held
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Spreadsheet / manual books vs integrated ERP
Compare typical manual finance work with Biznsbook Front desk and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Where you type it | ❌ A notebook line | ✅ Front desk or a free calendar cell |
| Check-in | ❌ A tick in the margin | ✅ Save on the front desk checks the guest in |
| Last seat | ❌ Whoever spoke last | ✅ A second confirm of the same seat is rejected |
| Later visits | ❌ Copy the row by hand | ✅ Weekly or fortnightly series with one series id |
| Full class | ❌ A name on a sticky note | ✅ Waitlist offer until the hold expires |
| Who they are | ❌ A new customer every time | ✅ Match email or phone, otherwise a Booker |
Day-of list
Use the today view for who is on the floor, unconfirmed for requests still waiting, and check-ins due for people who should already be here. No-show is a status on the booking, not a deleted row.
Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.
Frequently asked questions
Does front desk save confirm and check in?
Save on the front desk checks the guest in immediately. Use the booking list when you still need to confirm a request that is not a walk-in.
Can two staff confirm the last seat?
No. Confirm and hold lock the resource span. A second confirm of the last seat or an overlapping span is rejected.
How do I move one visit in a series?
Open the booking and reschedule that visit, or move the rest of the series. Weekly and fortnightly visits share one series.
What if Sales is not licensed?
The booking still completes. It then shows an operational balance only. A draft invoice is available when Sales is licensed.
How this differs by industry
Retail
A clinic front desk can drop a walk-in onto the free stylist cell and check them in without sending them through the public page.
Wholesale & distribution
A counter can book a short time-range pickup window for a trade customer who is already a party, matching them by phone so the type stays Customer.
Manufacturing
A service desk can check in a machine booking against a named bay when that resource is free for the whole span.