To run a wedding guest directory without sharing numbers, show each guest a name, photo and short profile, let guests send a chat request instead of dialling, open a conversation only when the other person accepts, exchange contact details by QR when both agree and set which groups can see which profiles. Guests meet each other, and nobody’s number leaks.
Why a directory is worth having
At a wedding, guests from two families, from school, from work and from the neighbourhood meet for the first time. A directory helps them find the cousin they were told to look for, discover who else is travelling from the same city and arrange to share a ride. It makes a large, unfamiliar crowd feel smaller.
It also solves a practical problem. Guests ask the family for each other’s numbers, and the family becomes a switchboard. A directory lets guests help themselves.
The concern is privacy. Many guests would be unhappy to find their mobile number on a list that hundreds of strangers can see. Spam, unwanted messages and awkward calls are real risks. The question is how to give the benefit without the cost.
The principle: connect first, share later
The safest design starts with a simple rule. Guests can see each other’s name, photograph and a short line, but not contact details. To talk, a guest sends a request. The other person decides. Only after acceptance can they message. Contact details travel only when the guest chooses to share them, for example by showing a personal QR code.
In this model, nobody is cold-messaged, and a guest who does not want to be contacted can ignore requests.
Step 1: decide who appears
Not every guest needs to be in the directory. Options:
| Option | Who appears | Fit |
|---|---|---|
| Everyone | All invited guests | Small weddings where all know the family |
| Opt-in | Guests who choose to appear | Large weddings, mixed ages |
| By group | Only guests in the same group or subgroup | Weddings with separate sides or circles |
Opt-in is gentlest. Ask guests when they first open the app: “Would you like to be visible to other guests?” and make the answer easy to change.
Step 2: choose what a profile shows
Keep profiles light. A name, a photograph, a city and a line such as “cousin of the groom” or “college friend of the bride” is enough. Avoid showing phone numbers, email addresses, workplaces or anything that could be misused. Let guests edit their own profile, and tell them what others see. Preview the profile before saving.
Step 3: use chat requests
A chat request is a polite introduction. The sender writes a short message, and the recipient sees it with a clear accept or decline. A conversation opens only after acceptance. Allow guests to block or report another guest. Provide a short guide on etiquette: say who you are and why you are writing.
Where a family wants more control, limit chat to certain groups, such as only within the same side, or turn chat off for some guests, such as children.
Step 4: add a QR for in-person exchange
When two people meet at the wedding, a personal QR code allows a quick exchange of contact details by consent. Each guest has their own code. One scans the other, and the contact is added. This is useful for friends from different cities who want to stay in touch. The guest decides when to show the code, so the family never publishes a list of numbers.
Step 5: set visibility with groups
Use groups to limit who sees whom. For example, the bride’s side may see only the bride’s side in the directory, with an option to open it to everyone later. Elders may be hidden from the directory to avoid unwanted requests. Where a family wants a wider mix, open the directory to all after the main function. Test the settings with sample guests from different groups.
Step 6: moderate and respond
Name a person to handle reports. Give them clear rules and the authority to remove a guest from the directory. Review reports during the wedding days. Keep records of reports and actions. Remind guests of the rules in the welcome message.
Step 7: communicate the privacy promise
A short note in the app builds trust: “Your phone number is not shown. Others can send you a chat request, and you decide whether to accept.” Place it where guests make their choices. India’s Digital Personal Data Protection Act, 2023 is being commenced in phases through May 2027 (Wikipedia summary, 2025); this is not legal advice, so ask your counsel to review how you collect and show guest data.
Step 8: close the directory
After the wedding, decide what happens. Options: close the directory and keep only photographs and wishes, keep it open for a few weeks so guests can follow up or archive it. Tell guests the date, and delete profile data according to the rule you stated.
A worked example for a large family wedding
A family expects guests from many cities and wants out-of-town relatives to find each other. The directory is opt-in. At first login, each guest is asked if they want to appear, with a short explanation. Guests who opt in fill a photograph and a line. The bride’s side and the groom’s side see their own side first, and the family opens the directory to all on the second day. A cousin who wants to arrange a shared ride sends a request, which the other accepts. At the sangeet, two old friends exchange details by QR. At the end of the week, the family closes the directory and keeps the albums. The example is illustrative and not a record of a wedding.
What to say in the invitation and welcome message
The directory will succeed if guests understand it. In the invitation or the first app message, explain three things in short sentences. First, what it is: a way to find and meet other guests. Second, what it shows: a name, photograph and a line, with no phone numbers. Third, how to control it: guests can choose whether to appear and can decline requests. Add a line for elders, who may be wary of apps: a family member can set up their profile on their phone, with their consent.
For overseas guests, mention time zones and invite them to introduce themselves early, so that relatives meet before travel. A short note in the family’s own voice has more warmth than a technical notice.
Edge cases to plan for
A guest without a smartphone. Their family member can act on their behalf for chat requests, with the guest’s agreement, or the family can introduce them in person.
Two guests with the same name. Use a photograph and a short line to tell them apart, and add the city or the side.
Unwanted attention. A guest who receives repeated requests from the same person can block them. The moderator may remove a persistent offender from the directory.
Guests who change their mind. Allow them to hide their profile at any time and tell them how.
Vendors and staff. Do not list them in the guest directory. If they need a contact route, give them a separate group.
Measuring whether it helped
After the wedding, look at the numbers: how many guests opted in, how many chat requests were sent and accepted, how many QR exchanges happened. Ask a few guests what they thought. If few opted in, the introduction may have been unclear. If many requests were declined, the profile lines may have been too vague. These small observations improve the next family occasion, and they help the planner decide whether a directory belongs in the next wedding app.
How Sociana handles this
Sociana’s delegates directory and QR contact exchange show attendees with search and tabs; a member taps a person to read their profile and send a chat request, and the conversation opens only after the request is accepted, so no one is cold-messaged. Each member has a personal QR, called My QR Code in one app and a Networking Card in another, and scanning it adds the contact. Members edit their own profile fields. Organisers can limit chat to ticket holders, moderate through reports and blocks, and use groups and cohorts to scope who sees what. Sociana gives you a directory with group rules and chat requests; there is no AI matchmaking.
The Tanvi & Rutwik wedding app (a three-day Pune wedding; not yet run) includes a guest directory, wishes, a countdown and bride’s side and groom’s side groups. Related: weddings, personal QR and group.
Frequently asked questions
Can guests see each other’s phone numbers?
Not by default. Guests connect through chat requests, and details are shared only when a guest chooses, for example by QR.
Can we hide some guests from the directory?
Yes. Use opt-in visibility or groups to limit who appears and who sees them.
What if a guest receives unwanted requests?
They can decline, and a block and report route exists. Name someone on the family team to handle reports.
Can the directory be switched off after the wedding?
Yes. The organiser decides when to close it. State the date to guests and delete profile data according to your rule.