Greeting Czech customers by name: „Ahoj, Eliško“, not „Ahoj, Eliška“

Every email tool in the world offers you a {{first_name}} merge tag. And every Czech customer can tell at a glance what falls out of it: "Ahoj, Eliška." "Dobrý den, Petr." A greeting that was supposed to feel personal, and instead announces: a machine wrote this and nobody read it afterwards.

Czech inflects names in a greeting. The correct forms are "Ahoj, Eliško", "Dobrý den, Petře", "Milá Lucie". The fifth grammatical case — the vocative — is precisely the detail that English-first platforms don't handle, because English doesn't have it.

If you sell into the Czech, Slovak, or Polish market, this one detail separates brands that localized from brands that ran Google Translate.

The wrong case is worse than no name

Addressing customers by name is one of email's best-measured techniques: a name in the subject line or greeting consistently lifts open rates and signals the message isn't a broadcast. But that mechanism only works when the result is linguistically correct.

"Ahoj, Eliška" is the uncanny valley of personalization. The customer sees that you tried to be personal, and simultaneously sees that nobody checked the output. That's a worse impression than a neutral "Dobrý den" — an impersonal greeting at least doesn't pretend.

For a brand built on detail — and premium brands are all built on detail — the grammatical case in a greeting is the same calling card as typography or packaging.

Why it's harder than it looks

The vocative isn't "add an -e at the end":

• Petr → Petře, but Marek → Marku, Ondřej → Ondřeji, and Jiří → Jiří (unchanged).
• Jana → Jano, but Lucie → Lucie, Carmen → Carmen.
• Diminutives and familiar forms live their own lives: Katka → Katko, Honza → Honzo.
• And then there are names Czech rules simply don't know: Kevin, Ayşe, Wei. For those, the only correct answer is to leave the name alone — or skip the name entirely.

This can't be maintained by hand. A lookup table with the twenty most common names covers part of the database, but breaks exactly on the names where the mistake is most visible.

How to solve it properly

The right answer is a declension database with rules for derived forms and a safe fallback. For the Czech market that's Vocato — a free app that declines Czech, Slovak, and Polish names, and also determines gender and name days.

Charm uses it as the foundation of its whole personalization layer: customers are greeted in the correct case in the loyalty hub and in emails, and a name day can become an automatic reward. You configure nothing — the first name from the order is enough.

A checklist for greetings that don't betray you

1. Fallback first. When the name is missing or unknown to the database, the greeting must degrade gracefully: "Dobrý den" with no name, no empty {{first_name}}, no first-case fallback.
2. Leave foreign names alone. "Ahoj, Kevine" is fine only when you're sure; otherwise "Ahoj" without the name.
3. Decide the register once. "Ahoj, Eliško" and "Dobrý den, pane Nováku" are two different brands. Which one are you — and does it hold everywhere? (We wrote a separate piece on formal vs. informal address.)
4. Check every surface. Emails are the start — greetings also appear in the loyalty hub, in notifications, on receipts. A system that declines names only in the newsletter hasn't solved the problem, just hidden it.
5. Test on the treacherous names. Jiří, Lucie, Honza, Carmen, Kevin. Five names reveal more than a hundred Eliškas.

A vocative greeting is the kind of detail a customer never consciously praises — but subconsciously registers every single time. And in a category where most apps speak Czech like Google Translate from 2014, it's the cheapest way to sound like a brand that means it.