# Multilingual ticketing — confirmations and tickets in English — MijnEvent Multilingual # Your visitor from abroad shouldn’t get their ticket in Dutch Someone from Germany or the UK buys a ticket and then receives a confirmation full of words they will never read. Set your organisation to English and everything MijnEvent sends on your behalf — the confirmation email, the ticket, the page after payment — goes out in English. Below is exactly what comes along, and what does not yet. [How it works](#how-title) [About accessibility](https://mijnevent.nl/en/accessibility) How it works ## One language setting, and the rest follows The language sits with your organisation, not with the individual visitor. You set it once and nobody has to think about it again. 1 ### Your organisation gets a language Dutch or English — that is the language of your subdomain. New organisations start out in Dutch. Want English? We switch it over for you; it is not a toggle that can be nudged by accident on a busy day. 2 ### Everything we send comes along From that moment the platform reads its texts from the English set instead of the Dutch one. This is not machine translation landing slightly off — these are texts written line by line, well over two hundred of them for the emails alone. 3 ### Your visitor stays in one language From the confirmation in their inbox to the ticket they open at the gate, they get the same language throughout. No English email with a Dutch ticket underneath it, or the other way round. What comes along ## This follows your organisation’s language Concretely, without the marketing gloss: these are the places where your visitor actually sees the language. ### The confirmation email Subject line, greeting, the lines above the order, the explanation next to the ticket, the unsubscribe note at the bottom. The whole email set is fully translated — not a single Dutch sentence slips through. ### The ticket itself The labels on the ticket your visitor has in their inbox or their wallet: ticket type, date, venue, the instructions beside the QR code. So the ticket they hold up at the gate is in their language too. ### The page after payment The screen your visitor lands on coming back from iDEAL | Wero — whether the payment went through, was cancelled or got stuck. That is precisely the moment someone wants to be certain about what just happened. ### Error messages and validation text A mistyped email address, a discount code that has expired, a time slot that just filled up. These are exactly the messages you do not want to read in a foreign language — so that set is fully translated as well. Who it is for ## Where this genuinely matters Not every organiser needs this. These ones do. ### The event just across the border Around Enschede, Venlo or Terneuzen a solid share of your audience comes from Germany or Belgium. A Dutch confirmation email is not a detail there — it is a reason to email you asking whether the ticket actually worked. ### The international conference Your programme is English, your speakers are English, your delegates come from ten countries. You do not want the only Dutch thing about the entire event to be the confirmation everybody receives. ### The festival selling abroad You advertise outside the Netherlands on purpose, and you sell there too. Set your organisation to English and your whole overseas audience gets a ticket they can read without a translation app. Good to know ## What is not there yet The multilingual work is not finished everywhere. Better you hear it now than after you have moved across. ## Your admin screen is Dutch The screen where you build events, review orders and change settings exists in Dutch only for now. If you work with an English-speaking colleague, factor that in — it is on the list, but it is not here yet. ## So is the booking screen The flow where your visitor picks their tickets and pays currently runs in Dutch. The language setting therefore covers everything we record and send on your behalf, and not yet the buttons during the booking itself. ## Two languages, per organisation There is Dutch and English — not ten languages, and we will not pretend otherwise. The language belongs to your organisation rather than the individual visitor: they cannot click a flag themselves. The foundation underneath is i18n-ready, so a third language is a matter of translating, not rebuilding. Frequently asked questions ## Frequently asked questions ## Can my visitor pick a language themselves? No. The language belongs to your organisation, not the visitor — there is no language button or flag on your event page. Everyone buying from you gets the same language. That is deliberate: it means you always know which language your emails and tickets go out in. ## Which languages are available? Dutch and English. That is it, and we will not write “and more languages” as though ten were waiting in the wings. The architecture is ready for additional languages, so adding a third means translating rather than rebuilding. ## Is this machine translation? No. These are written texts, one by one. The email set runs to well over two hundred lines in both languages and the validation texts to nearly a hundred. So you will not get sentences that land slightly wrong because a translation engine missed the context. ## Can I switch between Dutch and English myself? Not yourself. You can see the language in your settings, but we do the switching — a quick message and it is set. It is a setting you make once and then leave alone. ## What if something has not been translated yet? Then it falls back gracefully rather than showing up empty. The emails, the tickets and the validation texts are complete; in the odd corner a Dutch line may still surface. Spot one and let us know — it will be translated the week after. # Selling across the border too? Mention at sign-up that you work in English and we will set your organisation up correctly right away. It costs nothing extra — it is part of every pricing model. [Start free](https://mijnevent.nl/registreer) [All features](https://mijnevent.nl/en/features)