> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/appointments/walk-in.md). # Walk In **Available on:** Desktop · Web · Phone A **walk-in** is a client who is being served **now** — whether they turned up without a booking, or arrived for one. Instead of an appointment, a walk-in creates a **job slip**: the record of the work being done, which is later billed. ## Starting a walk-in * In the menu, double-click **Appointments › Walk In** — the job slip starts one minute from now; or * in the Appointment Viewer, right-click a free time and choose **New Walkin** — the job slip starts 5 minutes after the time you clicked. (The right-click item is spelt **New Walkin**.) The **Create Jobslip** window opens. It works like Create Appointment, but its **date and time cannot be changed**, and the services are saved as **CheckedIn** (yellow in the diary). Pick the stylist for each service in **Stylist Selection** as usual. The job slip number uses the **Default Prefix** from Configuration (for example *AP*) unless you have used another prefix before. ## Who is the client? If **Confirm Customer Type** is ticked in Configuration, the first question is **Select Walk-In Type**: | Choice | What happens | | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Appointed Customer** | The client has a booking. The **Appointment Search** opens so you can find it and bring its services into the job slip — see *Bringing in a booking* below. | | **Walkin-Non Member** | A one-off client. The job slip is made out to the **Default Customer** set in Configuration — no search needed. | | **Walkin-Interest for Membership** | Comes without an appointment, but may already be a member or wants to become one. The customer search opens so you can find or add them. | If **Confirm Customer Type** is not ticked, the customer search opens straight away. Then add services exactly as for an appointment — see [Creating and Changing Appointments](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/appointments/creating-and-changing-appointments.md) — and click **OK**. If you add a package service and the package is not paid up enough, you are offered the payment window at that point; after paying, pick the service again. > **Example — a passer-by.** At 3:10 PM someone walks in for a beard trim. Double-click **Walk In** in the menu and choose *Walkin-Non Member*: the job slip is already in the name of your default walk-in customer. Pick *Beard Trim*, choose Ravi in Stylist Selection, and click **OK**. Ravi's column shows the trim from 3:11 PM in yellow — *CheckedIn*. ## Bringing in a booking (Attach Appointment) When a client who has booked arrives, you can bring their booking into the job slip instead of keying it again. Choose *Appointed Customer*, or click **Attach Appointment** in the job slip. The **Appointment Search** window opens. Find the booking by **Customer Name**, **Membership Series** and **Membership No(s).**, **Mobile No.**, **Date**, or by ticking **Customer Selection**, **Service Selection** or **Agent Selection** to pick from a list, then click **Search**. Pick the appointment and click **OK**: its services are added to the job slip, keeping their booked times and stylists. * The search lists only appointments at the **Filter Status** set in Configuration (for example *Confirmed*), and only today's if **Show Only Today's Appointments** is ticked. If you cannot find a booking, check those two settings. * A booking for a **different client** from the one on the job slip is refused: *"Linked customer doesn't match with the selected customer!"*. Not to be confused with **Search Appointment** in the Appointment Viewer, which jumps to a client's next booking in the diary. > **Example — a client who booked.** Neha booked a facial for 11:00 AM and arrives at 10:55. Double-click **Walk In**, choose *Appointed Customer*, type *Neha* and click **Search**. Her 11:00 facial is listed; pick it and click **OK**. The facial comes into the job slip at 11:00 with her stylist, and she is checked in — nothing to retype. Another way to check in a booked client is straight from the diary: right-click their appointment and **Set Status As › CheckedIn**. That creates the job slip for you — see [Check-In and Parameter Values](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/appointments/check-in-and-parameter-values.md). ## While saving * If **Show Parameter Values Before Checkin** is ticked, the **Parameter Values** window opens for the client's before/after details. * Then, if **Print Job Slip On Checkin** is ticked, you are asked *"Print Job Slip?"*. The walk-in now shows in the diary and in the **Job Slip Viewer**, ready to be completed and billed. ## On the web Walk In works the same way on the web and on a phone. Choose it from the menu, or long-press a free time in a stylist's column and pick **New Walkin**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/appointments/walk-in.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.