Case note3 sections · 2 min readBy Dezső Mező · Published October 3, 2026.mdAutomationn8nBookingIntake
The leak is always the same shape: an enquiry arrives at 8pm, gets answered at noon the next day, and the two-day email thread about finding a time kills the intent that made them write. This is the intake pipeline pattern we build: the moment a form submits, a webhook turns it into a structured lead — name, problem, preferred window — pings the owner instantly, and offers the booking link in the auto-reply so the caller picks a slot while the intent is warm.
01Structure the intake at the source
The form asks for what a first reply would ask anyway: name, email, and 'what is the problem' with an example placeholder. Structured in means no clarifying round-trip — the owner opens the notification already knowing whether it is a fit.
02Reply in seconds, not hours
The auto-reply does three jobs: confirms receipt in the customer's language, sets the expectation ('you will hear from me today'), and offers the calendar. Booking intent is perishable — the link at minute zero converts the same person who ghosts by hour twelve.
03Log it where the next person looks
Every enquiry lands in one place — a row, a card, a channel — with the full message, not a notification that says 'check the inbox'. The pipeline ends where a human starts, and the human sees context, not a ping.
What to take away
- Ask at intake what a first reply would ask anyway.
- The auto-reply carries the booking link — intent is perishable.
- The owner gets the full message, not a 'check the inbox' ping.
- Every enquiry in one place, with context.
More from the lab
Browse all entries
Self-hosted n8n or Zapier — where the bill actually differs
The invoice pipeline that ended the Friday admin block
From WhatsApp chaos to a real order pipeline
MCP servers in production, not in the demo
Want this looked at on your own system?Start a conversation
