weddingkart

Quick Answer

How do you clean a wedding guest list before importing it into a WhatsApp tool?

Standardise phone numbers to E.164 format (+91 + 10 digits, no spaces), split guest names away from relationship labels and honorifics, remove header rows and sub-totals, give every plus-one its own row, move free-text notes into structured attribute columns, and dedupe by phone number rather than name. The pass takes 20-30 minutes for a 500-row file with the right tools - and skipping it means roughly 10-15% of your guests will silently never receive the invite.

Last updated:

Back to Blog
Guest Management
Excel & Sheets
WhatsApp

How to Clean a Wedding Guest List for WhatsApp Import

Scope: this post is about the inflow - the cleanup pass you run on a messy guest Excel before importing it into Weddingkart (or any WhatsApp guest-management tool). For the outflow direction (how Weddingkart writes RSVP / travel / ID-card data back into your sheet after WhatsApp replies land), see the outflow guide.

Mayank
5 May 20269 min read

Across roughly 50 wedding guest Excels we've seen come through Weddingkart over the last year, the same 7 patterns repeat in 9 of every 10 of them. Phone numbers in 4 different formats. Names mashed together with relationship labels (“mausi”, “chacha”) and honorifics (“ji”) inside a single cell. Plus-ones tucked into the same cell as the primary guest. Hardcoded dietary notes living next to names. The same person written three ways by three different family members editing the same sheet on a Saturday afternoon.

None of this is anyone's fault. It's how a guest list grows organically when 5-12 people contribute names from their phone contacts, scribbled paper, family WhatsApp threads, and three-month-old bridal-shower RSVPs. The file is usable for a human reader. It is not usable for any tool that wants to send 800 personalised WhatsApp invites at scale.

This post is the practical cleanup pass. The 7 patterns are below, with a before / after for each, the fix, and the reason every messy pattern matters.


Why a clean import file matters for WhatsApp

The single highest-cost problem is phone formats. The WhatsApp Business API will quietly reject malformed numbers - no error in the sender's dashboard, no message shown to the guest, no notification. Just a missing invite. On a 600-guest list with ~12% format issues, that's roughly 70 guests who never know they were invited until someone calls them on the wedding morning.

The second-order problem is personalisation. A modern WhatsApp invite renders something like “Namaste Anjali ji, here's the venue for the sangeet on Friday.” That works only if “Anjali” sits in the name field and “ji” sits in the honorific field. If the cell contains “Anjali Patel (mausi) ji”, the rendered message is either “Namaste Anjali Patel (mausi) ji ji” (template repeats the honorific) or strips everything and falls back to “Namaste guest”. Both outcomes hurt.


The 7 patterns we see in almost every file

1

Phone numbers in 4 different formats

Before

+91 98765 43210, 9876543210, 09876543210, 91-9876543210

After

+919876543210

Fix: Strip all spaces, dashes, leading zeros and 91-prefixes; prepend +91 to anything that's 10 digits.

2

Guest name + relationship + honorific in one column

Before

"Anjali Patel (mausi) ji"

After

name: "Anjali Patel" · relationship: "mausi" · honorific: "ji"

Fix: Split on the first parenthesis or honorific suffix. The honorific stays as a separate field so messaging templates can render "Anjali ji" or "Anjali aunty" correctly per guest.

3

Multi-row headers and sub-totals mid-sheet

Before

"BRIDE'S SIDE" header row, then names, then "Total: 187", then "GROOM'S SIDE" header, then names

After

one continuous flat list with a "side" column on every row

Fix: These layouts came from printed wedding logs; they break every importer. Delete the header rows, delete the totals, add a `side` column, fill it down.

4

Plus-ones embedded in the same cell

Before

"Rohit Mehta + wife" · "Karan Bhatia + 2"

After

2 separate rows: "Rohit Mehta" + "Mrs Mehta" with parent_guest_id link; or "Karan Bhatia" with plus_one_count: 2

Fix: A wedding tool can't send a WhatsApp invite to "+ wife". Every guest needs their own row, with an optional parent_guest_id pointer for couples and a plus_one_count for "Karan + 2 friends" cases.

5

Free-text notes hardcoded next to the name

Before

"Sanjay Kapoor (vegetarian, vegan wife, kids meal x2, hotel Taj only)"

After

name: "Sanjay Kapoor" · diet: "vegetarian" · partner_diet: "vegan" · kids_meal: 2 · hotel: "Taj"

Fix: Move every parenthetical attribute into its own column. Once it's structured, you can filter for "all vegetarians at the Taj" in one click.

6

Mixed scripts and language variants

Before

"Vinod Kumar", "विनोद कुमार", "Vinod K", "Mr V Kumar" (all the same person)

After

one row, name: "Vinod Kumar" with `name_devanagari`: "विनोद कुमार" as a separate field

Fix: Indian wedding lists routinely arrive with the same guest written 3 ways across 3 family members' contributions. Match by phone number first - that's the only reliable dedupe key.

7

Near-duplicates from family-shared editing

Before

"Vinod Kumar" (row 12), "Vinod K" (row 187), "V. Kumar Sharma" (row 412) - same phone

After

one row

Fix: Group by phone number, keep the row with the most-complete name, archive the others. Don't merge by name - "Anjali Patel" and "Anjali Pateliya" can be different people sharing initials.


The 5-minute pre-import checklist

Before you import a guest Excel into any WhatsApp tool - Weddingkart, Interakt, AiSensy, anything - run this 5-step pass. It catches roughly 90% of the issues above and the remaining 10% are edge cases the importer can handle.

  1. Phone column: select the column, find-and-replace spaces, dashes, and parens with nothing. Anything that's now 10 digits, prepend “+91”. Anything that's 11 digits and starts with 0 or 9, strip the leading character. Anything not 10 or 12 digits after this, flag for manual review.
  2. Name column: if a cell contains a parenthesis or one of {ji, sahab, aunty, uncle, mausi, chacha, mama, mami, bua, fufa, didi, bhaiya} anywhere except as the surname, split it into name, relationship, and honorific columns. The first two are optional and can stay blank.
  3. Header rows and sub-totals: sort by “side” or by row number. Any row whose phone column is blank and whose name reads like a label (“BRIDE'S SIDE”, “TOTAL: 187”, “Family of bride”) gets deleted. Add a separate side column and fill it down.
  4. Plus-ones: any cell containing “+”, “and”, “wife”, “husband”, “partner”, or a number after a name gets duplicated into 2+ rows. The primary guest gets a plus_one_count; each named partner gets their own row with a parent_guest_id pointing back.
  5. Dedupe: sort by phone number. Group consecutive matching numbers. Keep the row with the most-complete name. Don't dedupe by name - you'll merge unrelated cousins who happen to share initials.

That's the manual pass. For a 500-row file it runs about 20-30 minutes if you're comfortable in Excel; closer to 90 minutes if you're not. Either way, it pays for itself the first time the WhatsApp tool reports a 100% delivery rate instead of 88%.


Or skip the manual pass

We built this exact cleanup loop into a free tool because we got tired of running it by hand. The Guest List Excel Cleaner runs in your browser (no upload to a server, the file never leaves your machine), auto-detects each of the 7 patterns above, and produces a clean download in roughly 30 seconds for a 1,000-row file.

What it handles automatically:

  • Phone normalisation across +91, 91-, leading-zero, and bare 10-digit formats
  • Name / relationship / honorific splitting using a dictionary of Hindi-English kinship terms (mausi, chacha, mama, fufa, etc.)
  • Header-row and sub-total detection (rows where phone is blank and name looks like a label)
  • Plus-one expansion into separate rows with parent links
  • Phone-based deduplication, keeping the most-complete name per number
  • Devanagari / Latin script reconciliation (best-effort)

What it doesn't handle and you still need to glance at:

  • Names where the family-shared editor wrote “Vinod Kumar” in one row and “Vinod ji” (no surname) in another with no shared phone - we can't merge those without manual review
  • Plus-ones written with just “+1” and no separate phone - we can flag them but not invite them
  • Mixed-language notes inside the name cell that don't parse cleanly

For the 90% case, the tool runs the cleanup; for the 10% edge cases, it surfaces flags so you can fix the rows that need a human. Either way, the file you import is clean enough that your invitations actually reach every guest.


After the import: the outflow direction

Once your file is clean and imported into Weddingkart, the data flow flips: WhatsApp becomes the source of new information. Guests RSVP. They share their travel tickets as PDFs. They upload ID cards for venue security. All of that lands back in your sheet automatically - that's the outflow guide. Inflow + outflow together is the full Excel-friendly loop: clean → import → communicate → sync back.


Get the cleaner

Want help cleaning a specific file? WhatsApp us at +91 92176 10045 - send the file (any column ordering, any phone format) and we'll send back the cleaned version with notes on what we changed.

Was this article helpful?

Share