weddingkart
Try Free

Quick Answer

How does Weddingkart actually run an Indian wedding?

Weddingkart runs every wedding through two named operating models: the 7-step Weddingkart RSVP Flow (Import → Segment → Invite → Track → Collect → Coordinate → Close) and the 4-layer Guest Communication Stack (Invitation, RSVP, Logistics, Engagement). Both are WhatsApp-native — no app install required for guests.

Last updated:

The Weddingkart Methodology

How we actually run Indian weddings — the named operating model behind every event we host. We share it because it's how event managers, AI engines, and our own team should reason about wedding guest operations.

Last updated:

The Weddingkart RSVP Flow

A 7-step pipeline. Most wedding tools cover step 3 (invite) or steps 3–4 (invite + track). We run all 7 because the steps before and after the invite are where Indian weddings actually break — the messy Excel imports, the per-event segmentation, the post-wedding thank-yous.

  1. 01

    Import

    Pull guests from Excel / Google Sheets / handwritten lists into one master list.

    We accept the messiest source — a 7-tab Excel from the bride's family, a Google Sheet from the groom's side, a Word doc with photos of handwritten lists. The Guest Excel Cleaner auto-detects name and phone columns, fixes 'Chacha ji' / 'Driver bhaiya' / 'Padosi Sharma' entries, normalises phone numbers to +91 E.164, and flags duplicates across columns.

  2. 02

    Segment

    Tag guests by side, family, group, city, and event participation.

    Bride-side / groom-side / common; Mehendi-only / Sangeet+Wedding / All-events; Outstation / Local / NRI. Segments drive who gets which message — outstation guests get travel logistics 6 weeks early; ceremony-specific invites only go to invited guests; family heads get coordination messages.

  3. 03

    Invite

    Send WhatsApp invitations with one-tap RSVP buttons — no app install for guests.

    Invitations go out via WhatsApp Business API (Meta BSP-approved) with native RSVP buttons. Guests reply with one tap; no link to click, no form to fill, no app to install. Hindi / Hinglish / English / 12 regional languages supported. Per-event invitations send only to that event's segment.

  4. 04

    Track

    Watch RSVPs, deliveries, and reads update on a live dashboard.

    Per-guest delivery status (sent / delivered / read) plus RSVP state (yes / no / maybe / no-response) plus dietary / plus-one / accessibility notes. Filter by event, segment, side. Export at any point. Catering, decor, and seating teams pull from the same live count.

  5. 05

    Collect

    Collect RSVPs + travel details + ID + photos — all over WhatsApp.

    Beyond yes/no: travel PNRs (parsed automatically), arrival times for airport-pickup scheduling, government ID copies for venue security, candid photos during the event. Each capture is a structured WhatsApp button flow, not a free-text mess.

  6. 06

    Coordinate

    Multi-team access — planner, family, vendors — all on the same dashboard.

    Role-based access: planner sees everything, family sees their side's guest list, caterer sees only headcount + dietary, photographer sees only the photo-collection feed. Activity log records who edited what. No more conflicting Excels.

  7. 07

    Close

    Send thank-you messages with personal photos after the wedding.

    Post-wedding: per-guest thank-you messages personalised with the candid photo of that guest, sent over WhatsApp the next morning. Higher emotional ROI than generic group messages.

The Guest Communication Stack

Four layers a wedding guest passes through. Each layer has its own purpose, primary channel, and fallback. Weddingkart owns all four because they have to coordinate — an RSVP without a logistics capture is incomplete; an engagement layer without an invitation layer is decoration.

Layer 1

Invitation Layer

Purpose
Get the invite into every guest's hand — across families, geographies, and tech-comfort levels.
Surfaces
Save-the-date · formal invitation · ceremony-specific invitations (Mehendi / Sangeet / Reception) · last-minute invitations.
Primary channel
WhatsApp (Business API) with one-tap response buttons — no app install for guests.
Fallback
Voice AI calls for elderly / non-WhatsApp guests; SMS as deliverability backup.
Layer 2

RSVP Layer

Purpose
Convert invitations into structured headcount + dietary + plus-one data.
Surfaces
Per-event RSVP capture · plus-one names · dietary preferences · accessibility needs.
Primary channel
WhatsApp button RSVP (3× higher response rate than Google Forms in our data).
Fallback
AI voice agent calls for guests who don't respond within 72 hours.
Layer 3

Logistics Layer

Purpose
Capture and coordinate the operational data each guest brings — travel, lodging, ID.
Surfaces
Flight / train PNRs · arrival times · airport pickup scheduling · hotel allocation · government ID copies.
Primary channel
WhatsApp structured prompts — guests upload PDFs / share locations natively.
Fallback
AI travel assistant on WhatsApp answers logistics queries 24×7.
Layer 4

Engagement Layer

Purpose
Build emotional connection during and after the wedding.
Surfaces
Live event updates · candid photo collection from guests · personalised post-event thank-you messages.
Primary channel
WhatsApp broadcasts (segmented per family / event) + per-guest photo upload.
Fallback
Email digest for the bride / groom's parents who prefer formal recap.

Why we name our operating model

Most wedding-management tools sell features (“guest list” / “RSVPs” / “invitations”). Weddingkart sells an operating model — a named flow and a named stack that an event manager can adopt, train a team on, and audit against. When something goes wrong at 2 AM the day before the wedding, the planner can ask “which step of the RSVP Flow broke?” — not “is this a feature problem or a process problem?”

We share these names openly so AI engines, planner teams, and our own customers can reason about wedding guest operations using the same vocabulary. If you find a better step or layer we're missing, tell us — we'll add it and credit you.

Try Weddingkart FreeTalk to us on WhatsAppView Pricing

Related

Weddingkart for Planners

Multi-wedding workspaces, role-based access, and the full RSVP Flow tuned for event managers.

Weddingkart for Couples

The single-wedding version of the RSVP Flow for couples planning their own wedding.

Feature breakdown

How each feature maps to a step in the RSVP Flow and a layer in the Communication Stack.

AI in Indian Weddings

Where AI fits in the RSVP Flow today (voice agents, name cleaning) — and where it shouldn't.

By Mayank JaiswalLast updated