Working surface

Inquiry & booking

Common search: intake or booking flow — incomplete messages create back-and-forth before the team can reply usefully.

Try it in 20 seconds Change the request type. Watch missing details, readiness, and reply context change.

  1. Try this Switch request type, pick a slot, and add contact details.
  2. Watch what changes Readiness score and preview fields change with each choice.
  3. See what the team receives Routing, missing details, and suggested first reply in one packet.

Team receives Request type, readiness, missing details, and suggested first reply.

Can grow from one intake path into urgency, location, service, or calendar-aware routing.

Before
missing details and back-and-forth
After
readiness, missing fields, routing, and reply context in one packet
Try this
Change request type, slot, and contact fields.
What changes
The first reply can happen with less chasing.
Intake — demo Ref. INT-24018
  1. 1Reason
  2. 2Schedule / stay
  3. 3Contact
  4. 4Review

Type of request

Topic

First call — website

Preferred contact

Email, callback OK

Urgency

Normal — this week

Preferred time window

Structured fields instead of long email threads — for practice, stay, or consulting.

About this example

Nothing is really submitted here. Try a small interaction — real fields, routing, and handover are agreed per project.

Studio pattern. Real client builds are shaped around scope, field logic, and handover.