Two different language problems, solved two different ways
There are actually two separate language problems at an independent motel, and they usually get talked about as one. The first is guest-facing: a traveler texts or calls in Spanish and needs an answer in that language, right now, whether or not anyone on staff speaks it. The second is operator-facing: a large share of independent motel owners in the US, particularly AAHOA members, are first- or second-generation immigrants who may prefer running their own dashboard in Hindi, Gujarati, or Spanish rather than English.
Suzy addresses both, but with two different mechanisms, because they're genuinely different problems with different guarantees.
Guest-facing: automatic language detection
Detected automatically
A lightweight detector reads the guest's first message and identifies Spanish before any AI processing happens, at effectively zero added cost or delay.
Response matches
Once detected, Suzy's replies are generated in that language, grounded in the same property FAQ data she'd use in English, not a separate, thinner translation layer.
Preference remembered
A guest's detected language is saved to their reservation, so it stays consistent across the rest of their conversation, not re-detected message by message.
No staff required
None of this depends on a bilingual employee being on shift. It works the same at 3am as it does at 3pm.
Operator-facing: a dashboard in your language
Four dashboard languages
The operator dashboard is available in English, Spanish, Hindi, and Gujarati, switchable from the dashboard header at any time.
Every screen, not a partial translation
Headings, labels, buttons, empty states, and messages are translated consistently across the dashboard, not just a handful of top-level pages.
Built for AAHOA's actual membership
This exists because a real, sizable share of the independent motel owner community runs their business day to day in a language other than English.