Lead generation · 5 min read
Wedding Planners: Most of Your Inbox Is Not a Client
Read a wedding planner's Instagram inbox for a week and the uncomfortable fact is not the volume. It is the ratio.
Most of the people writing are not going to hire a planner. They are getting married, they are excited, they saw a haldi setup they liked, and they want to know what it costs. Some of them will do the whole wedding themselves with an uncle coordinating. Some are vendors. Some are students doing a project. A few are planners in another city.
That ratio is the design problem, and the obvious fix — make the bot ask about budget — is the one worth arguing against before you build it.
The date problem, which is the other half of this trade, already has its own post and this one will not repeat it. There is no calendar here and nothing can confirm the twenty-seventh.
Why an automated budget question backfires
It looks like the perfect first filter. One field, sorts the inbox, costs nothing.
Three things go wrong.
A number typed into a DM is not a budget. It is a guess made by somebody who has never planned a wedding, before the venue is booked, before the guest list has been fought over, often before the parents have been consulted. Half the figures you collect will be low by a wide margin and the other half will be invented on the spot to sound serious.
The people who can afford you find it insulting. A family that will spend properly does not want the first thing your business says to them to be a means test, delivered by software, four seconds after they said hello. In a referral trade, the first thirty seconds is the product demo.
It is a number you then have to store. A financial figure attached to a named account, sitting in a lead record, exportable as CSV by anyone with access. It buys you very little and it is one of the few genuinely sensitive things a marketing tool can hold.
Budget is the question you most want answered and the one a stranger is least able to answer honestly at the moment they first write to you.
Filter on the things that are actually fixed
Three fields separate a viable enquiry from a non-viable one without ever mentioning money, and all three are things the person genuinely knows.
- The date, or the month. If they do not have one, the wedding is not real yet. That is not a rejection, it is a callback in six weeks.
- The city, and where the function is. Whether it is inside your operating radius decides everything, and it is a fact rather than an aspiration.
- What they want planned. Full wedding, one function, day-of coordination, decor only. The scope word tells you more about the size of the job than any figure they will type.
Stop there. Guest count, theme, venue shortlist and budget are all conversations for a human, and they are better conversations once somebody has heard your voice.
Let the filtering happen before the DM
The better place to solve a bad ratio is upstream of the inbox entirely.
You cannot publish a price for a wedding, because there isn't one. You can publish the shape: whether you work on a planning fee or a percentage, whether there is a minimum event size you take on, whether you do single functions or only full weddings, whether decor is in-house or contracted. Put that on a highlight, in the bio link, in the caption of the post that generates the most enquiries.
People self-select on structure. A family that reads "we take full weddings from three functions upward" and writes anyway has told you something a budget field never would.
The non-viable enquiry still deserves a real reply
This is the part most lead-qualification writing gets wrong, and in this trade it is expensive to get wrong.
The person who cannot afford a planner this year has friends, siblings and colleagues who are also getting married, and they will remember which account replied like a human and which one ignored them. A short, warm, genuinely useful automated reply — where the good vendor directories are, what a day-of coordinator does differently, the one thing you would tell anyone doing it themselves — costs nothing, because templated replies are free and unlimited.
Refusing gracefully at scale is one of the few things automation is unambiguously good at.
The person messaging is usually not the person paying
In most Indian weddings the money and the decision sit with parents, and the Instagram account belongs to the couple or to a friend. Anything your automation asks is being answered by a proxy.
This is the second argument against automated qualification and it is the stronger one. A cousin cannot tell you the budget. She can tell you the date and the city, which is exactly the list above.
Cost, and what it will not do
Templated replies are free and unlimited. A credit is spent only when the AI writes a new reply — which, on a planner's inbox, should mostly be the enquiries that genuinely do not look like the others. Free tier is 100 credits, no card; packs start at ₹499.
No calendar, so nothing can hold a date. No quotes, no contracts, no payments, no advances. No CRM sync — leads leave as CSV. No WhatsApp, no sequences, no broadcast. It cannot message anyone who has not written to you first.
Official Graph API only: seven days to reply to a comment, twenty-four hours inside a DM thread, restarted only by their message. Against a booking cycle measured in seasons, put the useful link in the first reply and do not design anything that assumes a second one.
Build the three-field capture first, then read the date refusal, then what the checks stop. The wedding industry overview explains why this whole category behaves the way it does.
