BILINGUAL INTAKE · HOW IT IS BUILT

One build, two languages: how a bilingual intake form is actually made

A Spanish form is easy. A Spanish form whose confirmation, reminder, voicemail, and reschedule link are also Spanish is the hard part, and it comes down to one decision made at build time. Here is that decision and what follows from it.

Published May 28, 2026 4 min read

THE SHORT ANSWER

A bilingual intake form is one form with two language layers, built together, not an English form and a translated copy. The language the person submits in is saved on their record as a tag, and every automated message after that reads the tag: the auto-reply, the confirmation, the reminder, the voice agent’s first turn, the reschedule link. The form is the cheap half. The tag is what makes the rest of the practice bilingual.

The decision that decides everything else

There are two ways to have a Spanish intake form. The first is to copy the English one, translate the labels, and publish it at a second URL. It works for exactly as long as it takes someone to submit it, because the submission lands in the same system as the English ones, triggers the same English auto-reply, and books into the same English confirmation. The person who chose Spanish on the form has been handed back to English by the second message.

The second way is to build one form with a language switch, where every label, every option, every error message, and the consent line exist in both languages in the same build, and where choosing a language does one extra thing: it writes that choice to the record. That is the whole difference. One approach produces a translated page; the other produces a data point the rest of the system can act on.

What the tag does downstream

The auto-reply fires in the tagged language within a minute, with real availability rather than a promise.
The confirmation and reminders use the tag, including the reschedule link and the page it opens.
The voice agent, if the person later calls, reads the tag and opens in that language instead of asking.
The pipeline card shows ES or EN, so whoever picks up a stalled inquiry knows which clinician or coordinator should call.
The report can finally split conversion by language, which is the number most bilingual practices have never seen.

Why the Spanish is written, not translated

A therapy intake form asks personal questions. What brings you here. Have you seen someone before. Is there anything we should know before the first session. Machine translation renders those grammatically and lands them wrong: too formal, too clinical, or with the wrong pronoun for a person who is already nervous about filling in a form. The Spanish on our forms is written by people from Miami, in usted, with the vocabulary a Cuban, Colombian, or Venezuelan client would use rather than the textbook word. It is then read by a native reviewer before it ships, because a form is the first thing a client sees and it should not read as an afterthought.

What a good Spanish portal does not solve

SimplePractice, which many therapy practices already run, ships a genuinely good Spanish client portal. It deserves the credit. It also starts after someone is a client and has logged in. The inquiry that arrives at 9:41 PM from someone who is not yet a client lands on the practice’s website form, and that form, its auto-reply, and its confirmation are a separate system. The portal being Spanish does not make the front door Spanish. This post is about the front door.

The four places a translated form breaks

The auto-reply, which is an English template in a different tool.
The booking page, which the calendar tool renders in the practice’s default language.
The voicemail greeting, which was recorded once, in English, years ago.
The reminder text, which is usually the same string for every patient regardless of how they came in.

A practice can fix all four by hand, once, and then watch them drift back as tools change and templates get copied. Or it can build the form so the language is data, and let every later step read it. The second is less work in total and it is the one that survives a staff change.

Check yours in ten minutes

Open your own website on a phone that is not on your network. Choose Spanish if the form offers it, submit a plausible inquiry, and write down the language of every message that comes back over the next day. Most practices that believe they are bilingual find the break at the second message. That is not a criticism; it is the normal result of a translated form, and it is what the tag fixes.

Questions we get asked about this

What is the difference between a translated form and a bilingual one?

A translated form is a second copy at a second URL that submits into the same English system. A bilingual form is one build where choosing a language also writes that choice to the record, so the auto-reply, confirmation, reminders, and voice agent can read it.

Who writes the Spanish?

People from Miami, in usted, with the vocabulary a Cuban, Colombian, or Venezuelan client would use. It is then read by a native reviewer before it ships. It is not machine translation.

SimplePractice already has a Spanish portal. Do we still need this?

The portal is genuinely good and starts after someone is a client and logs in. The inquiry that arrives before that, on the website form, is a separate system. This is about the front door, not the portal.

Where does the form break for most practices?

At the second message. The form passes; the auto-reply, sent by a different tool from an English template, is where the Spanish stops.

Bilingual Intake Forms The feature page: one build, both languages, the tag on every record. Read more Spanish portal vs. Spanish intake Where a good Spanish portal begins, and the gap before it. Read more

Want the ten-minute check run for you?

The free bilingual readiness scan submits a Spanish inquiry to your practice and reports the language of every message that follows. No call required.

Book a Consultation More posts