Wedding Day Contact List Template for Indian Weddings

The painful version of wedding-day coordination is not that someone asks, "Who has the decorator's number?" It is that the same question hits the bride, the groom's brother, the planner, the hotel desk, and three family WhatsApp groups while the actual decision-maker is standing ten meters away.

The outcome you want is calmer: every routine question has one guest-help channel, every family decision has one owner, every vendor issue has one escalation path, and the couple is protected from becoming the call center for their own wedding. This wedding day contact list template gives Indian weddings a practical command sheet for haldi, mehndi, sangeet, pheras, reception, destination weddings, and NRI guest movement.

What is a wedding day contact list?

A wedding day contact list is the private command sheet that tells the planning team who to call for each type of decision, update, or escalation during the wedding. It covers family captains, venue contacts, hospitality, transport, medical or safety escalation, planner support, and backup owners for every function.

Wedding day contact list means the operational phone tree used on the event day to route questions to the right person without disturbing the couple or exposing private vendor numbers to guests.

The fast decision rule: if a person can solve a live wedding-day problem, they belong on the private contact list. If a person only needs information, they belong in the guest FAQ, itinerary, or Mandap Chat instead.

| Contact type | Put on private list? | Share with guests? | | --- | --- | --- | | Lead planner | Yes | Usually no | | Planner assistant | Yes | Only if assigned as help desk | | Bride-side family captain | Yes | No | | Groom-side family captain | Yes | No | | Hospitality desk | Yes | Yes, if it is the official help number | | Transport captain | Yes | Usually no | | Hotel front desk | Yes | Sometimes | | Venue manager | Yes | No | | Vendor on-site leads | In vendor roster | No | | Emergency services | Yes | Only local official numbers when appropriate |

This page is not a replacement for the wedding vendor contact list. Think of the vendor roster as supplier control. Think of this list as wedding-day command control.

Who should be on the wedding day contact list?

The wedding day contact list should include the people who can make decisions or remove blockers quickly: planner, assistant planner, bride-side captain, groom-side captain, venue manager, hospitality desk, transport captain, hotel desk, security or access lead, emergency owner, and one final decision-maker from each family.

Use this structure:

| Role | Best person | What they own | | --- | --- | --- | | Lead planner | Senior planner or coordinator | Final production decisions | | Planner assistant | Operations assistant | Run sheet updates and task chasing | | Bride-side captain | Sister, cousin, or trusted family member | Bride-side family calls and ritual cues | | Groom-side captain | Brother, cousin, or trusted family member | Groom-side movement and baraat cues | | Venue manager | Banquet or event manager | Room access, power, housekeeping, security | | Hospitality lead | Desk captain or concierge lead | Guest questions, lost items, welcome desk | | Transport captain | Fleet owner or planner transport lead | Shuttles, drivers, airport or hotel pickups | | Hotel desk contact | Group booking or front-office lead | Room keys, luggage, breakfast, checkout | | Emergency owner | Planner or family-appointed adult | Medical, safety, police, ambulance escalation | | Finance owner | Family or planner finance contact | Approved payment releases only | | Ritual owner | Priest assistant or family elder | Pooja items, family seating, muhurat cues | | Photo gatherer | Cousin or planner assistant | Family photo calls and missing relatives |

One mistake to avoid: writing "bride family" or "groom family" as the owner. A group cannot answer a call. Put one name, one phone number, and one backup.

What is the best day-of wedding contact list template?

The best day-of wedding contact list template is short, filtered by function, and written for live use on a phone. It should show the role, owner, phone number, backup, escalation topic, availability window, and whether the contact is private or guest-facing.

Copy this template:

| Field | Example | | --- | --- | | Function | Sangeet | | Contact role | Hospitality desk lead | | Name | Riya Sharma | | Primary phone | +91 XXXXX XXXXX | | Backup phone | +91 XXXXX XXXXX | | WhatsApp group | Planner ops only | | Owns | Guest directions, lost-and-found, seating questions | | Escalates to | Planner assistant | | Available from | 5:00 PM | | Available until | 12:30 AM | | Guest-facing? | Yes | | Notes | Direct guests to ballroom entry B |

For multi-day Indian weddings, do not make one messy list for every event. Add a function column and filter it for haldi, mehndi, sangeet, wedding ceremony, reception, and checkout. That keeps the master version consistent while letting each team see the slice they need.

How do you split private contacts from guest-facing contacts?

Private contacts should include the people who solve operational problems. Guest-facing contacts should include only the channel guests are allowed to use for routine questions. Mixing the two creates chaos because guests start calling planners, vendors, or family captains for basic schedule questions.

Use two layers:

| Layer | Who sees it | What it includes | | --- | --- | --- | | Private command list | Planner, venue, family captains, hospitality lead | Family owners, venue, transport, emergency, escalation, vendor roster link | | Guest-help layer | Guests, hotel desk, welcome desk | Itinerary, venue pins, transport time, dress code, food notes, official help channel |

If guests need answers, send them to a single channel: a hospitality desk number, wedding website FAQ, or AI wedding concierge for destination weddings. Do not send the whole private phone tree into a 300-person WhatsApp group.

For hotel arrivals, the guest-facing layer should also match the wedding welcome desk checklist, because the desk is where guests first test whether the contact sheet, itinerary, and QR code are actually aligned.

WhatsApp can still be useful when used deliberately. WhatsApp's Help Center describes broadcast lists as a way to send messages to several contacts without recreating the list each time (WhatsApp broadcast lists guide). That can work for reminders, but critical changes still need owner acknowledgement from the private contact list.

When should you finalize the wedding day contact list?

Finalize the wedding day contact list 48 hours before the first event, after the run sheet, transport plan, rooming list, vendor roster, and emergency kit ownership are confirmed. For a multi-day wedding, recheck changed numbers each morning before the next function begins.

Use this timing:

| Timing | What to confirm | Output | | --- | --- | --- | | 14 days out | Family captains, planner team, venue lead | Draft command list | | 7 days out | Transport, hotel, hospitality, photo gatherers | Function-level contact list | | 48 hours out | Final phone numbers, backup contacts, guest-help channel | Locked contact sheet | | Morning of each function | Changed phones, room changes, shuttle captains | Live correction note | | After each function | Remove stale contacts, update next-function owner | Clean next-event list |

Pair this with the wedding day run sheet template. The run sheet says what happens and when. The contact list says who can fix it when the timeline slips.

What contacts matter most for destination and NRI weddings?

Destination and NRI weddings need a stronger contact list because guest movement, hotel rules, language comfort, airport pickups, and room changes create more questions than a local single-venue wedding. The most important contacts are hospitality, transport, hotel, luggage, airport pickup, and family decision owners.

Add these extra contacts:

| Situation | Contact to add | Why | | --- | --- | --- | | Airport arrivals | Airport pickup captain | Guests land at different times | | Hotel check-in | Front-office group booking lead | Room keys and early check-in questions spike | | Luggage movement | Bell desk or luggage captain | Bags get separated across rooms and venues | | Shuttle movement | Shuttle captain and backup driver lead | Baraat, reception exit, and brunch need timing control | | International guests | English-speaking hospitality lead | Reduces confusion for first-time Indian wedding guests | | Elderly guests | Accessibility owner | Wheelchairs, lifts, seating, and rest areas | | Kids or nanny support | Family-approved child-care owner | Prevents random guest messages |

If you already use a wedding hotel rooming list or NRI wedding guest travel form, copy the final hotel, transport, and arrival owners into this contact list. The documents should agree before guests start arriving.

What should the emergency section include?

The emergency section should be conservative and clear: local emergency number, venue security, hotel desk, nearest hospital or clinic if already approved by the family or venue, planner emergency owner, and one family decision-maker. Do not make random cousins responsible for medical or safety decisions.

Use a small emergency block:

| Emergency type | Primary owner | Backup | | --- | --- | --- | | Medical concern | Planner emergency owner | Family decision-maker | | Venue safety or security | Venue manager | Security desk | | Missing guest or child | Hospitality lead | Family captain | | Lost passport or ID | Hotel desk plus family owner | Planner assistant | | Weather change | Lead planner | Venue manager | | Transport breakdown | Transport captain | Planner assistant |

Keep this block inside the private list and inside the document pouch from the wedding emergency kit checklist. Guests can receive a simple instruction such as "for urgent help, contact the hospitality desk" without seeing private family and vendor escalation notes.

For India, the official emergency response number is 112, as listed by India's emergency response support system (ERSS 112). Venue and hotel teams may also have internal emergency procedures, so confirm the right local instruction with them before the event.

How should the contact list connect to WhatsApp groups?

Use WhatsApp groups for communication, not as the source of truth. The contact list should say which WhatsApp group each role watches, but the phone sheet should remain the master document because group chats bury details quickly.

Use this group structure:

| Group | Members | Purpose | | --- | --- | --- | | Planner ops | Planner team only | Internal task routing | | Venue and planner | Planner plus venue leads | Room, power, access, security | | Family captains | Planner plus named family owners | Ritual cues and family movement | | Hospitality desk | Hospitality, hotel, transport | Guest help and lost items | | Transport ops | Transport captain and planner assistant | Shuttle and driver movement | | Guest broadcast | Guests or segmented guest lists | Approved reminders only |

The rule: if a message changes the plan, update the contact list or run sheet after the chat. A buried WhatsApp reply is not an operating system.

How can Mandap Chat reduce contact-list pressure?

Mandap Chat reduces contact-list pressure by answering routine guest questions before they reach family captains or planner phones. The private contact sheet still handles decisions and exceptions, but the AI concierge can answer schedule, venue, dress code, transport, rooming, food, weather, and welcome-desk questions from the approved wedding information.

This matters because most wedding-day calls are not true emergencies. They sound like:

• "Where is the haldi?"
• "What time does the shuttle leave?"
• "Can I wear black to the sangeet?"
• "Where do I collect my room key?"
• "Is lunch before or after the ceremony?"
• "Who do I ask about a missing bag?"

Upload the public answers once. Give guests the Mandap Chat link or QR code. Keep the private contact list for real escalation.

The 20-minute setup checklist

If production week has already started, build the simple version now.

1. Name one bride-side captain and one groom-side captain.
2. Name one hospitality lead and one transport captain.
3. Add the venue manager, hotel desk, and security or access contact.
4. Add the planner assistant who will update the live sheet.
5. Add emergency owner, backup owner, and local emergency number.
6. Mark each contact as private or guest-facing.
7. Put the guest-facing help channel into the itinerary, welcome desk, and Mandap Chat.
8. Link the private contact list from the run sheet and emergency kit document pouch.
9. Reconfirm every phone number 48 hours before the first event.
10. Print one copy for the planner desk, hospitality desk, and venue captain.

The goal is not a beautiful phone tree. The goal is that nobody has to call the couple to find the person who was already supposed to own the answer.

FAQ

What is a wedding day contact list?

A wedding day contact list is the private command sheet that shows who owns each wedding-day decision, update, and escalation. It should include the lead planner, family captains, venue contacts, hospitality desk, transport captain, emergency contacts, and backup owners for each function.

Who should be on a wedding day contact list?

Include the lead planner, planner assistant, bride-side captain, groom-side captain, venue manager, hospitality desk lead, transport captain, hotel desk, security or access lead, medical or emergency local number, and one final decision-maker from each family.

Should guests receive the full wedding day contact list?

No. Guests should receive one simple help channel, such as a hospitality desk number, wedding FAQ, or Mandap Chat link. The private wedding day contact list should stay with planners, family captains, venue teams, and operational owners.

When should the wedding day contact list be finalized?

Finalize it 48 hours before the first event, after the run sheet, transport plan, rooming list, and vendor roster are confirmed. Recheck phone numbers the morning of each function if the wedding spans multiple days.

How is a wedding day contact list different from a vendor contact list?

A vendor contact list tracks suppliers and on-site vendor leads. A wedding day contact list tracks the whole escalation tree: family owners, venue, guest help, transport, hospitality, emergencies, and the planner team. Most weddings need both.