Fixed quote after a free call

Wedding RSVP reminders and guest communication, handled for you

Chasing RSVPs and meal choices is the job couples and planners dread most. We build a workflow with one RSVP form or website page, often with a QR code on the invitation, that collects attendance, meal choices, dietary needs and travel details, sends polite reminders to guests who have not replied, and keeps live counts and a dietary summary for the caterer and venue. A typical build costs $1,000 to $2,500 and takes about three to four weeks.

The problem

Why chasing wedding RSVPs falls to the planner

RSVPs arrive by card, text, email and word of mouth, and the couple forwards them to the planner in batches. Meal choices are missing, plus-ones are unclear, and the caterer needs final numbers on a fixed date.

Chasing late replies falls to the couple or the planner, often in the busiest weeks before the event. Dietary and access needs then have to reach the caterer and venue accurately, without sharing more personal detail than needed.

What we build

What our wedding RSVP automation includes

One RSVP form

A form or RSVP page with attendance, meal choice, dietary needs, plus-ones and optional travel details, linked from a QR code on the invitation.

Guest list sync

Responses matched to the couple's or client's guest list, with unknown names flagged.

Reminder schedule

Polite reminders by email, or text where the guest gave a mobile number and agreed, before the RSVP deadline.

Live counts

Attending, declined and awaiting counts, meal choice totals and a dietary summary.

Caterer and venue pack

Final numbers and dietary needs by table, shared with only the detail each needs.

Guest updates

Schedule, transport and weather updates to attending guests, approved by the planner.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Invitations out

    The guest list is loaded and the RSVP link or QR code goes on the invitation.

  2. 02 Automated

    Responses recorded

    RSVPs and meal choices update the guest list and counts.

  3. 03 Automated

    Reminders sent

    Guests who have not replied get reminders before the deadline.

  4. 04 Coordinator review

    Planner reviews

    The planner checks unknown names, plus-ones and unclear replies with the couple.

  5. 05 Lead planner decides

    Final numbers

    The couple or client approves final numbers before they go to the caterer.

How it behaves

How RSVP reminders and guest updates behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the guest sees

  • A QR code or link that opens a quick RSVP form
  • One or two friendly reminders if they have not replied
  • Clear updates on schedule and transport

What the planner sees

  • Live attending and meal counts
  • Unknown names and unclear replies flagged
  • A caterer pack ready to send

What the automation does

  • Matches responses to the guest list
  • Sends reminders before the deadline
  • Keeps counts and the dietary summary up to date

Edge cases and fallbacks

Guest not on the list
Flagged to the planner to check with the couple.
Guest changes their reply after the deadline
Recorded and flagged to the planner, who updates the caterer.
Two people reply for the same household
Merged with the planner confirming numbers.
Form or email outage
Reminders pause, guests can reply by email, and the planner is alerted.

Architecture

RSVPs and guest communication at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Guest list From the couple RSVP form QR or web page n8n workflow Match, remind Reminders Email or text Live counts Meals, dietary Planner Checks, approves Caterer pack Final numbers
  • Input
  • Logic and services
  • Output
  • Data
  • People

How it flows

  1. 1 The guest list is loaded and the RSVP form goes out on invitations.
  2. 2 n8n matches each response to the list and updates live counts.
  3. 3 Guests who have not replied get reminders before the deadline.
  4. 4 The planner checks gaps, the couple approves numbers and the caterer gets a clean pack.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

RSVPs, meal choices & guest communications project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Guest list format, RSVP tools in use, meal options, deadlines and caterer needs.

  2. 02

    Design

    2 to 3 days

    Form fields, reminder schedule, consent wording and pack formats.

  3. 03

    Build

    About 1 week

    Form, matching, reminders, counts and caterer pack.

  4. 04

    Test

    About 1 week

    Test guests run through every path, including plus-ones and late changes.

  5. 05

    Launch

    1 to 2 days

    Go live with the first event and walk the team through counts.

  6. 06

    Support

    Ongoing

    Reused for every new event with updated details.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n A custom RSVP page or Google Forms and Sheets Your planning platform via Zapier Gmail or Microsoft 365 Twilio SMS or WhatsApp Business Platform Guest lists exported from Zola, The Knot or Joy, confirmed per project

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Guest list, form fields, schedule and packs.

    $200 – $400

  • Build

    Form, matching, reminders, counts and packs.

    $500 – $1,300

  • Integrations

    Planning platform, sheets, email and messaging.

    $150 – $400

  • Testing and shadow run

    Every guest path tested before launch.

    $100 – $250

  • Launch and training

    First event launch and walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Built once and reused for every event. Form, messaging and n8n costs are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Forms and email: Google Workspace or your email provider on its own plan.
  • Twilio SMS (US): About $0.0083 per message segment plus carrier fees (Twilio's published US pricing), if texts are used.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: texts to guests

Reminder texts go only to guests who gave a mobile number on the form and agreed to texts; others get email. Autodialed texts are covered by the TCPA rules.

Source: www.law.cornell.edu

Dietary and access needs are health data

Data concerning health is special category data under Article 9 GDPR and UK GDPR, so the form asks for explicit consent and the caterer gets only what it needs.

Source: gdpr-info.eu

Processors under contract

Form, email and messaging providers that hold guest data work under processor terms (GDPR Article 28).

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Wedding RSVP reminder questions questions, answered.

Short, friendly and with the RSVP link, sent a couple of weeks before the deadline and again a few days before. Texts go only to guests who agreed to receive them; everyone else gets email.

A simple RSVP page or form is enough for most events. If the couple already uses Zola, The Knot or Joy, we work from their guest list export where available, confirmed per project.

Yes. A QR code on the invitation opens the RSVP form on the guest's phone, with their name looked up from the guest list.

Guests choose from your options and add needs in a short field, with consent wording. The caterer gets totals and table-level needs, not more personal detail than necessary.

Yes. The same flow handles registrations, session choices and access needs for corporate events, with your branding.

Response rate by deadline, reminders sent, late changes and how early final numbers reach the caterer.

Free 20-minute call

Want this for your event & wedding planner?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call