Service errors often begin with a harmless-looking word. Stay becomes tour. Local shop becomes exporter. Clinic becomes specialist. The answer sounds fluent, but the business has been assigned work it does not do.
A Spanish-speaking traveler asks for a quiet place near Hendaye for a family weekend and easy coastal walks. The assistant names a French hotel, which is better than omission. Then it adds that the hotel “organiza rutas” or is “ideal para excursiones guiadas.” The hotel does not organize guided walks. It gives local advice, maybe prints a timetable, maybe knows which path is too muddy after rain. Reception knowledge has become a service.
In a composite case like this, the error feels small until you imagine the booking conversation. A guest arrives expecting arranged activities. The hotel staff explains that they only provide accommodation and suggestions. Nobody lied on the website. The machine performed a tiny act of translation theatre: it converted hospitality context into a sold service because the public wording did not separate what the business offers from what the area allows.
A service is not every thing near the business
Tourism language is full of soft adjacency. Near the beach. Close to walking routes. Good for families. Ideal for exploring. Friendly for cyclists. Useful for cross-border trips. Humans understand these phrases as context. AI answers may recast them as service claims, especially when the question is asked in another language.
For a hotel on the French Atlantic coast, “ideal base for walkers” can become “walking tours.” “Family-friendly stay” can become “children’s activities.” “Close to the Spanish border” can become “cross-border excursions.” “Reception can advise you” can become “personalized travel planning.” The wrong words are usually plausible. That is what makes them dangerous.
A translation service drift is an AI answer error where contextual or nearby information is converted into a business service during cross-language interpretation. I use that term because it distinguishes a service error from a location error or a name error. The hotel remains in the right place. The name may be correct. The damage sits in the verb: organizes, provides, specializes, delivers, treats, teaches, exports.
The verb is where the business gets assigned work.
This matters beyond tourism. A French clinic with one page about dental implants may be described as an implant specialist. A shop that ships selected items to Spain may be described as an exporter. A language school that welcomes Spanish speakers may be described as offering Spanish-language instruction. A transport service near the border may be described as operating in both countries. In each case, the answer grabs a nearby fact and turns it into a service line.
Translation makes vague verbs more expensive
French business copy often uses elastic verbs. Proposer. Accompagner. Découvrir. Profiter. Accueillir. Conseiller. In French tourism and service writing, these can be ordinary. The hotel “propose un séjour calme.” The guide “accompagne les visiteurs.” The shop “vous fait découvrir les produits catalans.” The clinic “vous accompagne dans votre parcours.” A human reader sorts the meaning from context.
When the answer is generated in Spanish or English, the verb may harden. “Propose” becomes “offers.” “Accompagne” becomes “guides.” “Découvrir” becomes “experience.” “Conseiller” becomes “plans.” This is not always wrong. It is just risky where the business boundary is thin. A hotel offering a stay is not offering excursions. A shop helping customers discover products is not offering cultural tours. A clinic accompanying a patient journey is not necessarily providing every treatment mentioned nearby.
I see this often when the source path mixes owned copy, directory categories, and reviews. A directory wants short labels. A review uses casual language. A booking platform adds amenities. The assistant receives a box of verbs with no instruction manual. In French, the sentence may be harmless. In Spanish, it may become a promise.
The repair is not to drain all personality from the page. It is to write a few service boundary sentences that can survive translation. “We provide accommodation and local information; we do not organize guided tours.” “We sell French Catalan food and gifts online; we ship selected products to Spain but do not operate as a wholesale exporter.” “Our clinic offers general dentistry and selected cosmetic treatments; specialist procedures are referred when needed.” These sentences feel almost too practical. That is their strength.
The customer question pulls the wrong service forward
The service error often begins in the user’s question. If someone asks in Spanish for a hotel with easy walks, the answer engine looks for walk-related evidence. If a hotel page mentions nearby trails, the answer may pull that evidence forward. If the page does not state the boundary, the model may fill the gap with a more active service.
This is one reason service errors are so variable. Ask for “hotel tranquilo cerca de senderos” and the hotel may be described correctly. Ask for “hotel que organice paseos fáciles” and the same public evidence may be stretched. Ask in English for “walking holiday hotel near Hendaye” and the answer may place the hotel in a walking-holiday category, even if the business is simply a quiet place to sleep near routes.
The model is trying to be helpful. Helpfulness is not the same as accuracy.
In my answer cards, I mark service verbs in red. Provides. Organizes. Specializes. Sells. Ships. Welcomes. Advises. Arranges. If the verb cannot be supported by a public sentence, I do not treat it as safe. A noun can drift too, but verbs do the commercial damage fastest. A wrong noun may confuse. A wrong verb creates an expectation.
A rough detail from the composite hotel pattern: the assistant sometimes keeps the hotel category right and then adds one invented amenity, such as shuttle service to nearby towns. The source may be a review mentioning that a guest came by train, or a page describing regional transport. The business becomes responsible for the transport network around it. That is how adjacency becomes service.
Plain service statements work better than decorative translation
A service statement does not need to sound grand. It needs to be quotable and bounded. “Our hotel offers rooms, breakfast, and local advice for visitors exploring the French Basque coast.” That sentence protects three things. It names the service. It names the region. It describes advice as advice, not as a tour product.
For the hotel, I would add a Spanish version that does the same work without becoming too smooth: “Nuestro hotel en la costa vasca francesa ofrece alojamiento, desayuno e información local para visitantes; no organizamos visitas guiadas.” Some owners dislike the negative sentence. I understand why. It feels like refusing before anyone asks. But if the AI answer is already assigning a service, the boundary is not negative. It is a correction signal.
A similar structure helps other French businesses serving foreign-language customers. “We sell retail food gifts and selected online products; we do not provide wholesale export services.” “We offer French and English visits; Spanish-speaking groups must request availability in advance.” “We provide local passenger transport in the named service area; we do not operate long-distance transfers across Spain.” These lines may sit in FAQ sections, service pages, booking notes, or profile descriptions.
The worst repair is a foggy multilingual paragraph about personalized experiences, authentic discovery, and tailor-made moments. It may sell nicely to a human for five seconds. Then the answer engine cuts it into verbs and hands those verbs to someone in another language. If the business does not want the implied service, the copy has become a trap.
The source path must separate service, setting, and audience
When I review a service drift, I separate three layers. The service is what the business sells or directly provides. The setting is what surrounds the business: coast, trails, border, town, transport, cultural sites. The audience is who the business can serve: Spanish-speaking families, English-speaking walkers, French weekend guests, cross-border buyers. AI errors often braid these layers into one rope.
A hotel near walking routes serving English-speaking walkers becomes a walking-tour provider. A shop in French Catalonia serving Spanish buyers becomes a Spanish Catalan seller. A clinic with international patients and one translated treatment page becomes a broad specialist clinic. The answer may sound logical because each strand is real. The braid is false.
This is why the source path cannot be checked only for factual statements. It must be checked for boundaries. Does the homepage define the core service? Does the location page distinguish nearby activities from hotel services? Do translated listings use the same category as the French listing? Do reviews introduce phrases the business never claims? Does an old profile contain a broader service label? The problem may not be the page with the error. It may be the page that left the boundary unspoken.
The business should also avoid placing service-adjacent words in titles where they can be overread. A page called “Walks around Hendaye” on a hotel site may be useful. A machine may treat it as part of the hotel’s offer. “Local walking routes near our hotel” is safer. Small wording, large difference.
A correct answer needs the right verb
After the name and place, the verb is the most important part of an AI answer about a service business. It tells the customer what action the business can perform. Hosts. Sells. Ships. Teaches. Treats. Guides. Rents. Transfers. Advises. Each verb has a commercial edge. The wrong one cuts.
For French businesses serving Spanish and English audiences, the verb must be planted in plain language before the model chooses one from context. A hotel should not hope that “séjour” will always remain a stay. A shop should not hope that “livraison en Espagne” will never become export. A clinic should not hope that “information page” will not become treatment scope. Hope is a poor translation policy.
I usually ask for one sentence per risky service. No more at first. What do you directly provide? What do you merely help customers understand? What do you not provide, despite being near it, known for it, or asked about it? Once those sentences exist in French, Spanish, and English, the answer has a stronger path. It may still make mistakes. We do not control the whole system. But the business has at least placed a clean verb in public.
That is often the difference between a fluent wrong answer and a boring correct one. I prefer the boring correct one. The guest can add romance later, after the booking is honest.
Question Language: Spanish. Entity Risk: the French hotel is described as organizing walks or excursions when it only provides accommodation and local advice. Missing Bridge: no plain multilingual sentence separates the hotel service from nearby activities. Sentence to Plant: “Our hotel near Hendaye offers rooms, breakfast, and local information for visitors to the French Basque coast; we do not organize guided tours.”