A groom once made one simple request to his mother before his wedding: Ma, please invite thirty guests. Just thirty. She said no problem. Then she invited a crowd. Everybody who hears that story laughs, because everybody recognises their own mummy in it.
Planners do not laugh. Planners have stood in that exact hall.
Three hundred seats, four hundred people
A hall that seats three hundred does not develop new chairs because the list grew to four hundred. What it develops is heat, blocked aisles, aso ebi ladies standing in their good shoes, ushers improvising benches, and a celebrant looking across the room thinking this place is choking, why did we pay for decoration nobody can walk past. The photos look crowded. The fire exits disappear behind rows of borrowed plastic chairs. And every person in that room concludes the same thing: the planner did not plan.
Here is the unfair part. You did plan. You saw the overflow coming weeks ago.
Planners always know. That is the tragedy.
The list never explodes in secret. You watch it happen in real time: mummy's side goes from forty names to seventy, the client keeps saying we will trim it, and three group chats keep leaking new names at 11pm. You know. You have always known.
What you lack is a lever. You cannot tell your client's mother to stop. You cannot freeze a list that lives in other people's phones. So you do the only thing a professional can do with a problem they can see but cannot stop: you quietly make provision. Extra chairs on standby, a word with the venue manager, a plan B for the overflow. You absorb the risk, you carry the stress, and if the hall still chokes, you carry the blame too.
Knowing about a flood is not the same as owning a tap.
What a tap looks like
Three things turn guest-list growth from a weather condition into a decision:
Additions get blocked at the source. On Comtev, every person contributing names works inside an allowance you set. Mummy has fifty seats. When she sends name fifty-one, the AI politely declines it. Nothing enters the list by pressure, by accident, or by 11pm voice note. For the first time, the list physically cannot grow behind your back.
"Ten more" becomes a formal request, not a leak. Of course your client will come back with we need ten more, they always do. That is fine. You issue an additional allowance, deliberately, with your eyes open. Overflow still happens when the client insists, but it happens as a signed decision by the person paying for the event, not as a slow silent creep that lands on your head.
The crowding is visible before it is physical. This is the part planners feel in their chest. The client's private link carries a live view of the event, and it can simulate how crowded the venue will be as the count grows against the capacity you set. Your client does not have to take your word that four hundred people in a three hundred seat hall will be unpleasant. They can watch the picture tighten as their own family adds names. The conversation changes from the planner is being difficult to ah, maybe we should trim mummy's list.
Why the visibility matters more than the blocking
The allowance is a wall, and walls are useful. But the simulation is persuasion, and persuasion is what planners have always lacked in the guest-list argument.
Until now the only evidence you could offer a client was your own experience: trust me, it will be too much. Against that, mummy's feelings win every time. A live picture of their own venue filling past its capacity is different. It is not your opinion. It is their event, their hall, their numbers, drawn in front of them while there is still time to act. You stop being the person saying no and become the person showing them the room.
The blame moves too, and this matters for your business. When overflow is a decision the client made in daylight, with the simulation in front of them, the crowded hall is no longer evidence that the planner did not plan. It is evidence that the client chose a bigger crowd over a comfortable room. You provisioned for exactly what was approved. It is on record.
What this looks like on a real wedding
The bride's side, the groom's side, both mothers and one aunty with a spreadsheet each get their own allowance, and the AI assistant collects names from all of them on WhatsApp, merging the duplicates, because the Ngozi the bride added and the Ngozi from church are one person, not two chairs.
The list grows to its limits and stops. The client watches the venue view fill on their private link. When they ask for more, you grant more, on purpose, and the simulation shows everyone what the extra fifty does to the room. Whatever the final number is, it is a number you approved, provisioned for, and can stand behind at the venue gate.
The 11pm messages still happen. They just stop being your problem.
Once the list is clean, the invitations are the next place planners lose a day (and sometimes a phone number): how to send wedding invitations on WhatsApp without getting your number blocked.
FAQs
How does AI guest collection stop a list from growing?
Every contributor works inside an allowance you set. Our AI assistant collects names from each person on WhatsApp and politely declines additions over their limit, so nothing joins the list without your say-so.
What happens when my client wants to add more guests?
They ask, and you issue an additional allowance if you agree. Overflow becomes a deliberate, recorded decision by the client instead of silent creep you discover at the venue.
Can my client see how full the venue will be?
Yes. Their private link carries a live view of the event, and it can simulate how crowded the venue will get as the guest count grows against the capacity you set, so trimming the list becomes their idea, not your argument.
What happens when two people add the same guest?
Comtev checks for duplicates across every contributor and merges them, so one guest cannot occupy two seats or collect two access passes.
Does this cost the planner anything?
Comtev is free to run. You pay wholesale for the messages you send and the guest-collection seats you hand out, and you charge your client your own price for the work. The worked example is on our pricing page.