The fear around automating onboarding is always the same: it becomes impersonal. That fear is justified, but it's aimed at the wrong spot. What a customer experiences as impersonal is rarely that an email was sent automatically. It's that they had to say the same thing three times.

This piece walks through the chain as it actually looks in practice: form, system, confirmation, scheduling. For each step, what should happen and where it goes wrong.

01 / the diagnosisWhy does onboarding feel messy?

Because the information sits in four places at once and is complete in none of them.

Part of it is in the email exchange where the meeting was actually arranged. Part is in the head of whoever had the conversation. Part is in a form the customer half filled in. And part is nowhere, because nobody asked for it.

The result is that the first real meeting starts with a quarter hour of reconstruction. To the customer this feels like a company that doesn't know who they are, which is exactly the feeling you were trying to prevent with warm manual emails.

Impersonal isn't that an email arrives automatically. Impersonal is that you'd already been given the answer.

02 / the chainWhat happens between yes and the first meeting?

Four steps. They seem trivial, which is exactly why they're rarely designed.

At most companies, steps 1 and 4 exist but separately, and step 2 is missing entirely. Then you have a form that sends an email and a calendar that knows nothing about that form. That's not a chain but two loose pieces with a human tying them together, every single time.

03 / the formWhat do you ask, and what do you not ask?

Only ask what you need to make the first meeting useful. Not what might once be handy.

This is where most onboardings go wrong. A form with eighteen fields gets half filled in or abandoned, and then the email exchange you wanted to prevent starts anyway. A form with six fields gets completed.

Two rules of thumb that make the most difference in practice:

• Don't ask what you already know. Name, company and email address you usually already have from the first contact. A form that asks for it anyway tells the customer nothing was kept track of.
• Don't ask what you'll only use three months from now. That can come later, in a context where the customer understands why it's being asked. Right now it just costs you completion rate.

What does belong in every form is one open field with a good question in it. Not "comments," but something like: what needs to be different in six months compared to now. That one answer is often worth more than the ten structured fields above it, because it's in the customer's own words.

04 / the confirmationHow does an automatic email stay personal?

By being specific. Not by sounding warm.

A confirmation email that says "we've received your submission and will get in touch as soon as possible" says nothing, and everyone notices. An email that says what's happening now, who's doing it and when, reads as a company that has things under control, even though it was sent automatically.

Three things that make a confirmation concrete:

And the line we hold ourselves to: a system may confirm, remind and prepare. It doesn't write a substantive reply on your behalf without you having seen it. Why that's not a technical limitation but a choice is explained in why we don't publish automatically on your behalf.

05 / the schedulingWhy the calendar is the real bottleneck

Because it's the only step where two calendars need to line up, and by email that fails in three rounds almost every time.

Let the customer choose from what's actually free. That sounds obvious and in practice isn't: many companies send three proposed times that are already taken by the time the reply comes in. A live calendar where the customer books themselves shaves off, on average, several days of lead time and a handful of messages from everyone's inbox.

Watch for two things when setting it up. Build in a minimum buffer time, otherwise there's a meeting at eight tomorrow morning nobody knew about. And make sure the meeting confirmation carries the same information as the form confirmation: what, when, with whom, and where the customer needs to go.

The customer doesn't notice that it's automated. They notice that it's correct.

06 / the lineWhat you'd better not automate

Three things, and they have one thing in common: judgment is involved.

The decision whether you say yes. Anyone who accepts a customer based on a form ends up accepting customers who don't fit. That costs more later than it saves now.

The first substantive reply. A system may draft, not send. The difference between a draft you check and a message that goes out the door on your behalf is exactly the difference between time saved and reputational risk.

The bad news. A rejection, a delay, a price that ends up higher than discussed. That should come from a human, even if it takes more time.

How we build such a chain step by step is on the page about our approach. Automate what repeats and involves no judgment call. Leave what depends on who's sitting across from you. That line isn't technically determined and isn't hard to draw, but it does need to be drawn before you start building. How you take apart an existing process along that line is covered in your tools don't talk to each other.

This text was produced with AI assistance and reviewed and approved by a human before publication.