What a business glossary is, and is not
Picture a small business that serves customers in English and Spanish. The website calls it an "estimate." The invoice template calls it a "quote." In Spanish, one staff member writes "cotización," another writes "presupuesto," and the automatic text message says "estimado." A customer reads three different words and wonders whether she got three different documents. When the business adds an AI tool to draft replies, it picks a fourth word.
That scene is an original illustration, not a TwoQM client and not a measured result. Nobody in it made a translation mistake. Each word was reasonable. The problem was that nobody decided which words the business uses, so every person and every tool decided on its own.
This article is about fixing that with one shared glossary that your templates, forms, staff, and AI drafts all follow. It works for any bilingual business: contractors, clinics' front offices, property managers, restaurants, insurance agencies, retailers.
A business glossary is a short list of the terms that matter to your customers and your operations, with the one approved English word and the one approved Spanish word for each. It is not a dictionary and it is not a style guide for every sentence. Think of 30 to 80 terms, not 3,000.
Good candidates are words that show up in documents, statuses, and money conversations:
Document names: estimate, invoice, receipt, work order, agreement.
Statuses: scheduled, in progress, waiting on parts, ready for pickup, closed.
Money terms: deposit, balance due, refund, store credit, late fee.
Service names exactly as you sell them.
Policy words: cancellation, no-show, warranty, return.
One row per term
Keep each entry simple and in one place:
English term and Spanish term you approve.
Avoid: other words people use that you do not want in customer-facing text.
Where it appears: website, forms, invoices, text templates, emails, signs.
Note: when it matters, a one-line explanation, such as "use 'usted' in all customer messages."
Owner and date: who approved it and when.
The "avoid" column does most of the work. It tells a new hire, a template editor, or an AI tool exactly which synonyms to replace.
Decide register once
Spanish has choices English does not, and customers notice when they change mid-conversation. Decide once and write it down:
Formal "usted" or familiar "tú" in customer messages.
Regional vocabulary your customers actually use. In the Rio Grande Valley that may differ from what a generic translation tool picks.
Whether you keep certain English terms that customers already use, such as a product name.
The article on bilingual front-desk scripts and call queues shows the same idea applied to phone scripts in a front office.
Make your systems read from it
A glossary in a binder helps a little. A glossary your systems use helps a lot:
Statuses and pick lists are stored once as codes, with an English label and a Spanish label from the glossary. Staff and customers see their own language for the same status.
Templates for texts, emails, and invoices use the approved terms. When a term changes, you update the templates that list it in the "where it appears" column.
Forms on your website use the same field names in both languages, so data lands in the same place.
Reports read the same codes, so nobody translates notes before adding them up.
Give the glossary to your AI drafts
If you use AI to draft replies, summaries, or notices, include the glossary in the instructions it follows: use these terms, avoid these words, use this register. Then check the drafts. The article on AI-drafted follow-ups with human send approval walks through keeping a person in charge of every send.
AI can draft in both languages with your terms, flag a draft that uses a word from the "avoid" column, and suggest new terms when it sees the same word come up again and again.
AI does not approve new glossary terms, publish final translations of contracts or policies, or send messages on its own. A bilingual person on your team does.
Keep it current
Review the glossary when you add a service, change a policy, or switch tools. Add a term when staff ask "how do we say this?" more than once. Retire terms you no longer use instead of leaving them to confuse people. Legal documents, contracts, and official notices still need review by a qualified bilingual professional; the glossary keeps everyday wording consistent, it does not replace that review.
Where TwoQM fits
Business automation can keep your text and email templates in step with the glossary. AI automation can draft bilingual messages that follow your terms for staff review. Connected systems can share the same status codes and labels across the tools you already use, and custom software can add a glossary screen where your team approves terms in one place. What fits your setup is confirmed during scoping.
Where to start this week
Pull five things customers receive from you: an estimate, an invoice, a reminder text, a confirmation email, and one web form. Highlight every term that appears in both languages. Wherever the same idea uses different words, pick one in each language, write it in a shared list, and note who approved it.
TwoQM builds automation, AI tools, connected systems, and custom software for small businesses in the Rio Grande Valley and beyond. Pricing explains how business apps, systems, and custom software are scoped.
Talk Through Your Bilingual Templates · Explore TwoQM Business Automation