Therapist website design: the reason box

A person considering therapy is often tired, unsure whether the problem is serious enough, and wary of strangers. A form that opens with a required box asking for the reason for coming asks them to explain themselves before any person has answered. Some leave at that box and do not come back. Booking tools add a second barrier. A date of birth, a phone number and an insurance field can appear before any time is shown, so a visitor who only wants to know whether there is space cannot find out without giving those details first.

• Is a reason for coming required before a visitor can send a message?
• Does the page say what a first session involves, in plain words, above the form?
• Can a visitor see whether consultation times are open before giving a date of birth?
• Does booking ask for a text code? A simulated visitor cannot receive one.
• Is the cancellation rule on the booking page, not only in a footer document?

A first session is the most unfamiliar thing on the page, and most practice sites describe the therapist rather than the session. A visitor wants to know what happens in the room, how long it lasts, whether they will be asked to talk about their history on the first day, and whether they can stop. Those answers do much of the work of getting someone to book. If they sit in a long biography or behind an about page, the visitor has to hunt for them while already unsure. Read your homepage and ask whether a stranger could describe a first session after one minute.

The contact form is usually where the first barrier sits. A required box that asks why someone is reaching out forces an answer before the visitor knows whether the practice has space or what happens next. The visitor is also asked to trust that the message is private, and a form they do not understand is a poor place to extend that trust. If a warning appears about who reads the message, it should say so plainly and before the box, not in small print after it. Make the box optional, and let the consultation times come first.

Some booking tools ask for a date of birth, an insurance field and an emergency contact before they show a time. A visitor who is only checking availability has to give those details to learn whether there is any time at all. Other tools send a text code to confirm the booking. A simulated visitor has an email inbox but cannot receive a text, so the run stops at that code, and a real visitor without a phone to hand stops there too. Note the step, and check whether an email option exists, so a visitor is never stopped by a channel they cannot use.

Practices add forms over time: a waitlist, a new service, a second location, or an intake questionnaire from a new provider. Each addition can put a required question above the time a visitor needs to see. Run the same visitor from the homepage after each new form, and again after a change to the booking tool. The run shows whether a consultation time is still reachable before any personal detail is asked for.