Multilingual wedding RSVPs that actually speak your guests' language
Wedding guest lists rarely fit into one language. AisleReply runs your RSVP conversation over WhatsApp in 50+ languages - Hindi, Punjabi, Urdu, Polish, Arabic, Mandarin, Yoruba and many more - so every guest replies in the language they actually think in, and you see everything translated, tidy and caterer-ready on a single English dashboard.
Start your multilingual RSVPThe problem multilingual couples actually face
If your guest list spans more than one language, you already know what's coming. Your Punjabi grandparents won't navigate a wedding website. Your partner's mum in Warsaw would *much* rather not type in English. Your Lebanese aunt is going to send a voice note. Your Nigerian uncle prefers to ring rather than fiddle with a form. And there's always one cousin you end up phoning to translate for someone else, which works fine until you have forty other things to do that week.
The usual workarounds are *all a bit awkward*. A translated paper card flatters nobody and almost guarantees lost replies. A multilingual wedding website still expects guests to find it, read it, choose a language, tap through tabs and complete a form - which is precisely what the people you most want to hear from will quietly avoid. And asking a relative to act as a translator turns a moment of joy into yet another small obligation for someone who was already on the favours list.
The honest truth is that multilingual guest lists need a *different shape of RSVP entirely* - one that meets people where they are, in the apps they already use, in the language they already speak.
How AisleReply handles multilingual weddings
AisleReply is built around a conversation, not a form. Every guest receives a friendly WhatsApp message from your wedding assistant. They reply however they like - in whatever language, in whatever style, with whatever questions - and the assistant understands and responds in the same language, naturally.
There are no tabs to navigate, no dropdowns to find, no language picker to misclick. Your aunt in Lahore writes in Urdu; the assistant writes back in Urdu. Your cousin in Lyon writes in French; the assistant switches to French and stays there. A Hindi-speaking uncle who throws in a few English words doesn't have to start over - the assistant handles the mixing the same way a bilingual cousin would.
Behind the scenes, every reply lands on *your* dashboard in English, with the original message preserved alongside the translation. Headcounts, dietary needs and event choices are normalised so you can see at a glance who's coming, who needs halal, who's bringing children and who hasn't replied yet - regardless of which of fifty languages they wrote in.
Languages we speak fluently
AisleReply supports more than fifty languages out of the box, on every plan, at no extra cost. The list below covers the languages most often requested at UK weddings - if a language you need isn't shown, it almost certainly works. Ask us.
- EnglishEnglish
- Hindiहिन्दी
- Punjabiਪੰਜਾਬੀ
- Urduاردو
- Bengaliবাংলা
- Tamilதமிழ்
- Gujaratiગુજરાતી
- Polishpolski
- Romanianromână
- Arabicالعربية
- Persian (Farsi)فارسی
- Hebrewעברית
- TurkishTürkçe
- Mandarin中文
- Cantonese廣東話
- Korean한국어
- Japanese日本語
- Vietnamesetiếng Việt
- Thaiไทย
- YorubaYorùbá
- IgboIgbo
- SwahiliKiswahili
- Spanishespañol
- Frenchfrançais
- Portugueseportuguês
- Italianitaliano
- GermanDeutsch
- DutchNederlands
- Russianрусский
- Ukrainianукраїнська
- Greekελληνικά
- Malayalamമലയാളം
What this looks like in practice
A worked example, because this is easier to *see* than to describe. Imagine your cousin Tomasz lives in Kraków. His English is fine for ordering coffee but he'd rather not draft a wedding reply in it. He receives a friendly WhatsApp message about your wedding in Polish.
Assistant → Tomasz
Cześć Tomasz! Anna i James serdecznie zapraszają Ciebie z osobą towarzyszącą na &slash;lub 14 września w Cotswolds oraz na śniadanie weselne wieczorem. Daj znać - czy będziesz mógł przyjść?
Tomasz → Assistant
Tak, ja i moja żona, oboje wegetarianie, będziemy na obu wydarzeniach. Dziękujemy!
A few seconds later, on your dashboard in London, that exchange appears as a clean row:
Tomasz Kowalski — Attending (2 of 2)
Plus one: wife (vegetarian)
Events: Ceremony, Reception
Dietary: 2 × vegetarian
Original reply (Polish)
"Tak, ja i moja żona, oboje wegetarianie, będziemy na obu wydarzeniach."
English translation
"Yes, me and my wife, both vegetarian, will be at both events."
Tomasz felt looked after. You didn't have to chase, translate or interpret. The caterer gets "2 × vegetarian" in plain English on the export. Nobody had to ask a cousin for help.
Right-to-left support, properly done
Arabic, Hebrew, Urdu and Persian (Farsi)
Right-to-left languages aren't an afterthought. Messages render in the correct direction inside WhatsApp, punctuation sits where it should, and the assistant replies in the matching script - whether that's Arabic العربية, Hebrew עברית, Urdu اردو or Persian فارسی. On your dashboard, the original right-to-left message is shown alongside an English translation, both rendered correctly, so nothing looks broken or backwards.
How is this different from a translated form?
A translated wedding website is *better than nothing*, but it still asks the guest to do most of the work. They have to find the link. Tap through. Pick a language. Read the page. Find the RSVP button. Fill the form. Submit it. Get an error. Try again.
Forms are designed for *people who like forms*. That's not most wedding guests, and it's almost never the relatives whose RSVPs you most want to lock in early.
Translated form
Guest must find the website, choose a language, complete fields in the right order, and remember to submit. The less tech-confident guests quietly don't.
AisleReply conversation
Guest receives a WhatsApp message in their language. They reply however feels natural - one sentence, three sentences, a voice note. Done.
The difference shows up in the response rate. Conversations get finished. Forms get abandoned. For the half of your guest list that lives outside the comfort zone of English-language web forms, that gap is the *whole* difference between hearing back and chasing for weeks.
Pricing
Multilingual support is included on every plan. There is no language add-on, no per-guest language fee, and no upgrade gate. Choose the plan that fits the *size* of your guest list, not the *languages* on it.
-
Essential — £149
For smaller weddings. Full multilingual assistant, dashboard, caterer-ready export. -
Standard — £349
The most popular choice. Adds multi-event handling (ceremony, reception, mehndi, sangeet, rehearsal dinner), and more configuration. -
Premium — £599
For larger or multi-day weddings. White-glove setup, priority handling, custom domain on Pages add-on.
Full plan details and what's included on each tier: see pricing.
Start your multilingual RSVPFrequently asked questions
- Which languages does AisleReply support?
- Fifty-plus, including all the major languages spoken at UK weddings: English, Hindi, Punjabi, Urdu, Polish, Arabic, Mandarin, Cantonese, Yoruba, Igbo, Bengali, Tamil, Gujarati, Spanish, French, Portuguese, Italian, German, Romanian, Russian, Turkish, Persian (Farsi), Hebrew, Vietnamese, Korean, Japanese, Thai, Swahili and many more. Every language is included on every plan at no extra cost.
- How does the assistant know which language to use for each guest?
- It auto-detects on the guest's first reply and stays in that language for the rest of the conversation. If you already know that a particular guest will reply in a particular language - your grandmother in Punjabi, say - you can pre-set the language for them on the dashboard so even the very first invitation arrives in the right tongue.
- Can guests mix languages in their reply?
- Yes. The assistant handles code-switching naturally - the kind of mixing you actually hear at weddings. Hinglish, Punjabi-with-English- numbers, Polish-with-the-children's-English-names, Arabic with scattered French. It's all understood, and the assistant tends to mirror the guest's style back to them so it never feels stiff or translated.
- Does AisleReply support right-to-left languages like Arabic and Hebrew?
- Yes. Arabic, Hebrew, Urdu and Persian (Farsi) are fully supported with proper right-to-left rendering inside WhatsApp and on your dashboard. Guests see correctly aligned messages in the right script, and the assistant replies in matching script and direction.
- Will I see the replies in English on my dashboard?
- Yes. Your dashboard shows the original message in the guest's language alongside an English translation. Names, dietary requirements, event attendance and headcounts are all normalised to English so you can review the list at a glance without having to read every language yourself.
- What about regional dialects like Punjabi from India vs Pakistan?
- The assistant handles regional variations sensibly. Punjabi guests writing in Gurmukhi script (more common in India) and those writing in Shahmukhi script (more common in Pakistan) are both recognised, and the assistant replies in the matching script and dialect. The same applies to differences like European versus Brazilian Portuguese, Mainland versus Taiwanese Mandarin, and Levantine versus Gulf Arabic.
- Can I get a caterer-ready export with everyone's dietary needs even if they replied in other languages?
- Yes. Dietary requirements are normalised to English on the dashboard and in the caterer export, regardless of which language the guest used. Wegetarianskie becomes vegetarian, حلال becomes halal, 素食 becomes vegetarian, and so on. Your caterer gets a single consistent English spreadsheet they can actually work from.
- How much does the multilingual feature cost extra?
- Nothing. All 50+ languages are included on every plan - Essential (£149), Standard (£349) and Premium (£599). There is no per-language fee and no upgrade gate. Multilingual is the default, not an add-on.
Ready when you are
If you're planning a wedding with guests across more than one language, AisleReply was built for *this* - not as a bolt-on, not as a setting, but as the way the service was designed from day one. Set up takes about a week, including done-for-you onboarding, and your guests start replying as soon as your invitations go out.
Start your multilingual RSVP