BILINGUAL INTAKE · POSITIONING
Spanish portal vs. Spanish intake: the gap Clio leaves open
Clio, which many South Florida firms already run on, ships a genuinely good Spanish client portal. It begins at engagement. Everything that decides whether there is an engagement happens before it, and that is a different problem with different rules.
This is a fairness-first argument. Clio built real Spanish product capability, not a translated page, and it deserves to be described accurately. The gap this piece points at is a matter of when the portal starts, not how good it is.
What the portal does well
It gives an existing client a Spanish-language experience once they are inside it: navigation, client-facing paperwork, secure messaging, built for Spanish rather than machine-translated over an English interface. That is real product work, and it is why Clio is the incumbent worth taking seriously on Spanish rather than dismissing.
Where the portal begins
At login. A client portal is, by definition, a thing a client logs into, so it starts after the engagement agreement is signed: after the person found the firm, reached out, got a reply, was screened for conflicts, sat through a consultation, heard the fee explained, and signed. Everything the portal does well, it does for someone who has already cleared all of those steps.
ENGAGEMENT IS THE LINE
What happens before login, at a law firm specifically
The Spanish inquiry that arrives at 9:41 PM lands somewhere the portal has no reach: a website form, the main line, a voicemail, a text, a chat widget. It is sent by someone with no account and no reason yet to trust the firm with one. What happens to it is decided by whatever the firm’s front door is at that hour, and by the four things that have to happen before a portal invitation would ever be appropriate:
- The reply. Someone or something answers, in Spanish or not, within a minute or the next morning. What it says is governed by the Florida Bar’s advertising rules, which the portal never has to think about because the portal talks to clients, not prospects.
- The conflict check. Before the attorney hears the facts, the firm needs the other side’s name. A Spanish intake that does not ask for it, or asks in a translation nobody reviewed, means the check happens in the consult, after an hour the firm cannot bill.
- The consultation. Booked, reminded, and held in the language the person chose, with an attorney or interpreter who was told in advance.
- The fee conversation and the agreement. A contingency percentage or a retainer deposit explained in Spanish, and an engagement agreement the person can read. This is the last step before the portal, and it is the one that most often fails in a half-translated intake.
Why the portal does not simply move earlier
Because it is built around an authenticated account, which is what makes it a reasonable place to hold case paperwork, billing, and privileged messages. Extending that to someone who has not decided to hire the firm would mean asking a stranger to create an account before they trust you, or running a separate unauthenticated system for the inquiry stage. The second one is a different build, not an extension of the portal, and most legal software treats it as somebody else’s problem.
There is also a confidentiality reason the two stay separate. Information a prospective client shares during intake is protected under Rule 4-1.18 even if no engagement follows, and it needs to be handled that way. But it is not yet the client file, and putting it in the client system before the conflict check clears is how a firm ends up with the other side’s facts in its own case management software.
Why a translated form does not close the gap
Because the inquiry stage has more moving parts than one form. The autoresponder, the booking page, the reminder, the reschedule link, the voicemail greeting, the document list, and the retainer email are separate pieces built at separate times. Translate only the form, and a Spanish-speaking person watches the firm’s Spanish disappear one screen after they submit. It reads, fairly or not, as a firm that tried and stopped.
Machine-translated Spanish has its own tell for a Miami-Dade reader. It reads as literal rather than local. That is a separate problem from the timing gap this piece is about, but they compound: a firm can have a fine portal and a form that gives the wrong first impression, because the two were never built by the same hand.
Is LegalCRM.pro the only bilingual intake option?
No, and it would be false to say so. Clio’s Spanish portal is real, and other tools handle pieces of bilingual communication reasonably well. What we are specifically building for is the stretch before anyone is a client: the inquiry tagged by language and answered in it, the conflict-check fields captured in that language, the consultation and the retainer follow-up carried in it, and the hand-off into Clio or MyCase when the matter opens. That is a narrower claim than "the only bilingual system", and it is the one this piece is making.
Where this leaves a firm evaluating both
Evaluate what each tool is built to do, at which stage, rather than treating "bilingual" as one checkbox. A portal that serves clients well in Spanish and an intake that answers prospective clients in Spanish are not competing claims. They cover different halves of the same relationship, and a firm that only checks the post-login half is not checking the half where people decide whether to become a client at all.
- A portal answers "how do I serve the client I already have, in Spanish?"
- Intake answers "how do I reply to, screen, consult, and sign the person who has not decided yet, in Spanish, without saying anything the Bar would read as a promise?"
- Neither question makes the other unnecessary. They sit on opposite sides of the signature.
Related
Running Clio and want the intake half?
A 30-minute demo shows the hand-off: the inquiry, the screening, the retainer, and the matter opening in Clio with the file already started.