Spanish-speaking guests and staff in US restaurants: language at the table

In many US restaurants Spanish is spoken on both sides of the pass: by guests at the tables and by the people cooking for them. Serving it well means two jobs. For guests, add Spanish descriptions and let them ask questions in Spanish. For staff, make sure tickets and notes read clearly to a kitchen that may work in Spanish first. WaiterPilot’s chat answered in Spanish in our test, but its guest buttons are English or Arabic, not Spanish, and we’ll say exactly where that matters.

How many guests and staff speak Spanish?

Short answer: about one in eight people in the US speaks Spanish at home, and so does about one in five restaurant workers.

The US Census Bureau found that 22% of people aged 5 and older spoke a language other than English at home, and about 61% of them spoke Spanish (US Census Bureau, 2025). Multiply the two: 22% × 61% ≈ 13%, or roughly one person in eight. Not all of them need help with an English menu. In 2024, 60.9% of people who spoke another language at home said they speak English “very well” (USAFacts, from Census data, 2026). The rest may read your menu more slowly, or prefer to ask in Spanish.

On your team, the share is higher. The National Restaurant Association, analyzing 2024 Census data, found that 30% of restaurant and foodservice employees speak a language other than English at home, against 25% of all workers, and 21% speak Spanish. Among chefs the share speaking another language is 46%, among cooks 39%. And 23% of restaurant employees were born outside the US, including 19% of waitstaff (NRA, Mar 2026).

So the question isn’t only “can my Spanish-speaking guests order?”. It’s also “can my kitchen read what they ordered?”.

Where does language get in the way?

Short answer: at four points: reading the menu, asking about a dish, the note on the ticket, and the bill.

A Spanish menu fixes the first row. The other three need either bilingual staff on every shift, or a way for guests to ask in Spanish and for tickets to read clearly in both languages.

Which Spanish should the menu use?

Short answer: the Spanish of the guests you serve most, with the English word kept next to any food word that changes from country to country.

Spanish food vocabulary differs between Mexico, the Caribbean, South America and Spain. A guest from Madrid and a guest from Monterrey can read the same word differently, or not recognize it. These differences come up most on US menus:

Two rules handle most of it. Write for the guests you see, and keep the English word in brackets when in doubt: “camarones (shrimp)”. Describe dishes by what’s in them, because “chicken, rice, black beans, mild” reads clearly in any variety of Spanish.

How does WaiterPilot handle Spanish?

Short answer: the chat speaks Spanish; the buttons and dish names don’t.

Guests scan the QR code on their table, the menu opens in the phone’s browser, and they can ask about your menu in their own words. The chat replies in the language the guest writes in, and answers from your menu. When the menu doesn’t cover a question, it tells the guest to ask a staff member.

In our 15 Oct 2026 test at BroadNet.AI’s own demo café, a guest asked “Hola, ¿qué jugos naturales tienen? ¿Cuál me recomiendas?” and got the answer in Spanish, with the juices listed under their English names, as written on the menu. That was one test, at one restaurant, with a drinks question. We have tested English, Arabic (several dialects) and Spanish so far.

Be clear on the rest:

That last line deserves its own sentence. For allergies, WaiterPilot gives what your menu says and asks the guest to confirm with staff, in the guest’s language. Your staff have the final word.

If you need the guest screen itself in Spanish, a menu translation tool does that: MENU TIGER, for example, advertised menus auto-translated “into 30+ foreign languages” as published on 15 Oct 2026 (MENU TIGER pricing). If your team needs Spanish staff screens, some POS systems offer them: Toast’s help center lists English, Spanish, French and Simplified Chinese for its devices, and notes that “menu names and items are not translated” (Toast support).

A worked example: bilingual dish names at Casa Olivo

Casa Olivo is a fictional restaurant (an example, not a customer). The kitchen, menu and evening below are an illustration written for this post.

Casa Olivo has 40 dishes and a kitchen of five cooks, three of whom read Spanish more easily than English. Its servers hear Spanish at several tables every night.

The change. The owner rewrites every dish name in both languages on the menu, English first, and adds a short Spanish line to each description. Because dish names show as written on the menu, both languages now appear in the chat, on the board and on the kitchen screen. Nothing is translated on the fly; the menu simply says both.

Friday, 19:40, table 6. A guest writes: “¿El pollo pica? Lo quiero sin cebolla.” (Is the chicken spicy? I want it without onion.) The chat answers in Spanish from the description: the menu marks the dish as mild. It asks which side the guest wants, because the dish has a required choice, and the guest picks rice.

Here is the ticket at each step:

Before the change, the same ticket said “Grilled chicken, Side: Rice, note: sin cebolla”: English names and a Spanish note. Most kitchens cope, but mixed tickets are where small mistakes start. With bilingual names, every cook reads every line in the language they know best.

What it cost. One afternoon: 40 dish names and 40 short descriptions, checked by a bilingual member of staff. When a dish changes, the owner edits it once, in both languages.

How do you handle allergies across two languages?

Short answer: the same way in both: a member of staff confirms every allergy at the table, and the kitchen checks it.

Language gaps make allergies riskier, and telling staff isn’t always enough even without one. In a registry study of 2,827 people with food allergies, 53.9% of the reactions that happened in restaurants occurred even though the guest had told staff about the allergy (Oriel et al., FARE, 2020). Add a second language at the table and a third in the kitchen, and the chances of a misunderstanding go up.

Three habits help. Teach every server the one Spanish question on the card below, “¿Tiene alguna alergia?”, and the answer they must act on. Write allergens into dish descriptions in both languages, so the chat and the printed menu both say the same thing. And treat any note that might be about an allergy as a stop: a person goes to the table before the order is confirmed, whatever language the note is in.

WaiterPilot doesn’t change who decides. The chat gives what your menu says and asks the guest to confirm with staff. Your staff have the final say.

A phrase card for both sides of the pass

Print it twice: once for the floor, once for the kitchen.

What to do next

1. Count the Spanish-speaking tables on two busy nights.
2. Ask your cooks which language they’d rather read on a ticket.
3. Write dish names in both languages for your top 15 dishes, then the rest.
4. Print the phrase card for the floor and the kitchen.
5. Agree who checks notes at the first order of each table.

To see a Spanish question answered next to English and Arabic, read our multilingual ordering test. For guests from further away, see the checklist for serving tourists and our comparison of a translated menu and a multilingual chat. Then try a sample order or see how it works. WaiterPilot costs $200 per location per month after 30 days free, with 0% commission.