Pattern: front-desk intake

This is a teaching pattern, composited from the way small service desks describe their morning. It is not a client case. It does not report time saved, money saved, or a before-and-after. If you need the rules for reading a page like this, start with how to read an honest build.

In short. The desk still owns the intake. A draft assembles the fields the shop already collects. A person files it. Nothing about a customer is promised by the draft alone.

The problem

The phone rings while someone is also watching the door. The intake lives in a notebook, a text thread, and a memory of what the caller said about access, pets, or which location. Later, a different person creates the job and calls back because a field was missing. The owner sees the gap at night, when they are the one retyping.

The pain is not “we need AI.” The pain is a job that starts twice.

What a build of this shape contains

A build of this shape usually has four parts:

• A short list of fields the shop already requires: who, where, what they need, when, and the access note.
• A draft that fills those fields from the notes the desk already captured, in the order the job board expects.
• A place the draft waits. It does not create the job by itself during a first pilot.
• A named person who files it, or sends it back with one line about what was wrong.

The source material is the shop’s own examples: three good intakes and three that had to be redone. Without those, the draft imitates a generic call center. With them, it sounds like the desk.

What it does not contain, in the honest first version: automatic scheduling, a price, or a text to the customer. Those are later decisions, each with their own checkpoint.

What it replaced

In a build that held, the second cold start is what changes. The person creating the job starts from a draft instead of from a blank form and a memory. The notebook may still exist during the shadow. The pattern does not require you to throw it away on Monday to look modern.

If the desk still retypes every field because the draft is wrong, nothing has been replaced yet. That is a revise-or-stop moment, described in the build pillar. Do not keep a spectator draft because the demo looked tidy.

What’s still human

The person at the desk still hears the tone of the caller. They still decide whether the job is real, whether the time window is a promise the shop can keep, and whether the access note is complete enough to send someone out. The draft does not meet the customer. The draft does not apologize.

Angry, odd, or high-dollar calls stay fully human. The pattern gets worse if you force them through the same template to be consistent. Consistency is for the ordinary path.

If you want this built with you

A front-desk pattern becomes custom work when the draft has to land in the system you already run, under your name, across more than one location, or with someone other than you watching it next month. That is a discovery conversation — custom build, whitelabel screens, or Managed AI — not a claim that a magazine page installed anything.

Bring three real intakes with the names removed. The evaluation prep sheet is the rest of the list. Leave the invented before-and-after at the shop. There is not one.