Chasing addresses by text is a slow way to start a wedding. People send half an address, a photo of an envelope or nothing at all. I would send one link and ask every guest once, in the same order.
What do guests tell me?
The names as they should appear on the envelope, then street, city, region, postcode and country. Email and phone are optional, for the day the post goes astray. Each answer matches a line on a label, so you can copy columns straight across.
What would a guest's AI ask?
"How should we write your names on the envelope?" Then "What is your street address?" Then "Which postcode and country?" The AI shows every answer, so the guest can fix a typo before anything is sent, and it submits only after a yes. Read about agent-fillable forms.
How do I look after this data?
Addresses are personal, so ask only for what you will post to. The form leaves out identity numbers on purpose. Download the CSV once, keep it private and delete it after the thank-you cards go out. Follow your local rules for personal data.
What else will I need?
Two small tick boxes help: one for guests who are moving, one for guests who want a printed invitation instead of an email. Once addresses are in, move on to a wedding RSVP form for replies and a song request form for the music. Afterwards, a wedding guest book collects notes. Browse forms for weddings.
Questions
How do I print envelope labels from the answers?
Download the CSV and open it in a spreadsheet. Use the envelope_names column and the address columns as the source for a mail merge in your label printer.
What should I do with the addresses afterwards?
Keep the CSV in one private place, use it for invitations and thank-you cards, and delete it once the cards are posted. Share the link only with people you invite.
What if a guest is moving before the wedding?
A tick box asks whether they are moving, and a date field asks when. Check those two columns before you print labels, so no card goes to an old address.