Describe your arrival process and Makeform creates a customer check in form for names, appointments, and visit reasons. Give reception a consistent record, route each visitor, and replace the clipboard with a tablet-ready form.
Send arrival records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting point, adjust its prompt, or send it to the Makeform builder. Each example shows a practical arrival flow.
Audience
Customers arriving for a scheduled service
Format
Tablet check-in with appointment matching
Prompt size
231 chars
Example form structure
Tablet check-in with appointment matching
Customer name and mobile number
Appointment date and time
Booking or reference number
Reason for today's visit
Anything the team should know?
Suggested routing tags
Scheduled arrival
Walk-in
Needs assistance
Ask for an appointment time and host name separately. Reception can scan structured answers faster than a single open-text response.
Step 1
Arrive
customer opens the form or uses the lobby tablet
Step 2
Identify
name and appointment details match the visit
Step 3
Route
visit reason points reception to the right team
Step 4
Welcome
confirmation sets a clear next step
A calmer front desk
Connect each customer to an appointment, capture why they came, and give staff enough context to respond.
Required identity, appointment, and visit-reason fields give reception consistent information.
Separate appointments, walk-ins, deliveries, and support visits with a service choice.
Notify reception or connect arrivals to the tools your team watches.
Built around the visit
Choose the closest check-in flow, then edit the wording, choices, and confirmation message to match what happens at your location.
Match a customer to a date, time, reference number, service, and expected staff member.
Capture company, host, meeting purpose, and contact information at reception.
Collect the requested service and a short explanation without asking for appointment details that do not apply.
Record customer interests and the assigned representative so the conversation starts with context.
Check-in workflow
Collect what staff use, test the customer device, and make the next step clear.
Describe who checks in, the relevant appointments, and what reception needs.
Require essentials, keep notes optional, and show booking fields only for appointments.
On the lobby device, submit one sample appointment and one walk-in.
Choose the submission destination, reviewer, and post-submit customer instruction.
Digital form vs paper sheet
The best method depends on whether you only need attendance or need to match an arrival, understand the request, and alert the right person.
Field guide
Use fields that match the arrival, explain the visit, or complete the handoff.
Customer identity
Collect a full name and one useful contact method. Add a booking or order reference only when it helps staff match records.
Appointment match
Ask about appointment status first. Scheduled customers provide booking details; walk-ins skip to service and visit reason.
Visit reason
List real services for fast routing, then add an optional note for details a dropdown cannot capture.
Internal handoff
Choose the destination with the form. Reception may see every arrival while hosts need only relevant submissions.
Customer instruction
Confirm receipt and give one instruction, such as taking a seat. Avoid estimated waits unless they come from a reliable source.
Shared-device setup
Open the tablet directly to the form, use short labels, and ensure each customer starts with a blank form.
Related tools
Connect arrival to booking, guest registration, queues, and follow-up with dedicated form starting points.
Create a straightforward attendance record for visitors, members, or customers.
Open toolCollect requested dates, services, and contact details before customers arrive.
Open toolRegister guests with identity, contact, and visit details in advance or on arrival.
Open toolCapture interest and contact details when an appointment or space is unavailable.
Open toolAsk customers about the experience after their appointment or visit is complete.
Open toolGather preferred times and visit reasons when staff confirm appointments manually.
Open toolFAQ
Practical answers for reception teams, service counters, offices, and showrooms improving their arrival process.
Customers complete it when they arrive for an appointment, service, pickup, or walk-in visit. It captures identity, booking details, host, and visit reason so reception can route the arrival.
Include full name, useful contact details, appointment status, booking time or reference, and visit reason. Add the host or department when it changes routing.
Ask about appointment status first. Show booking and host fields to scheduled customers; send walk-ins to service and visit-reason questions. Both paths can share the same confirmation.
Yes. Open the published form on the tablet, use short tappable choices, and test the full path there. Ensure every customer starts with a blank form.
Confirm receipt and give one next step: take a seat, speak with reception, or wait for a name. Avoid a specific wait promise without dependable timing data.
Yes. Makeform offers unlimited free forms and responses. You can generate, edit, publish, and use the form without a response cap; the paid tier removes the Makeform badge.
A sign-in sheet records who arrived and when. A check-in form adds booking matching, service, host, and visit context for staff who need to act.
You can connect arrivals to tools such as Google Sheets, Slack, or Zapier. Choose one operational source of truth, then test an appointment and a walk-in.
Make every arrival easier to route.
