What guests see

We think about guests as much as hosts, because a beautiful invitation is only useful if people actually reply. Here's what happens on the other side of your link.

A guest taps the link in a chat and the invitation opens in their browser. There's nothing to install and no account to create. If you added music, they first see an Open Invitation screen, and the song starts the moment they tap it, a small moment that feels like opening a card. Without music, the invitation opens directly.

Everything sits on a single page: the cover, the event name, the date and time, the place with a Get Directions button, your description and any details you added, like a registry link or dress code. Guests don't click through tabs or separate pages to find the address. They see the atmosphere and the facts together, then reply.

Replying takes a few seconds

Guests tap one of the two RSVP buttons, type their name and send. If you allowed plus-ones, they say how many people they're bringing. If you added questions, they answer them in the same form. They can also leave a short note for the guest wall. The whole thing is designed for a phone held in one hand, with large buttons and readable text, so it works just as well for a teenager as for a grandparent.

If you set a capacity or an RSVP deadline, the page handles it for you. Once the event is full or the deadline passes, guests see a clear message instead of a form.

In the guest's own language

rsvp.so speaks 34 languages, including English, Spanish, French, German, Portuguese, Turkish, Arabic, Hindi, Japanese, Korean and Chinese. The buttons, the RSVP form and the date format follow each guest's browser language. Your own words stay exactly as you wrote them; we never machine-translate your invitation. For Arabic, Persian and Urdu, the layout switches to right-to-left.

So when a cousin in Germany opens a wedding invitation written in English, the form asks for her reply in German, and the date reads the way she's used to.