Event Photographers: The DM That Is a Rights Question

You post four frames from Saturday's wedding. By Tuesday, three messages have arrived from that one event and none of them is a booking enquiry.

The decorator wants the mandap shots for their own feed. An aunt wants the link to "the full album". A rental company that supplied the chairs has already reposted one and is asking, retrospectively, whether that was okay.

Somewhere behind those is an actual enquiry from someone getting married in November. The automation has to find it without doing damage to the other three, and the other three are the interesting part.

The easy half: "send me your work"

Start with what genuinely automates well, because it is a real chunk of the inbox and it is free to answer.

People ask to see more. Full weddings rather than four frames, a specific kind of event, a particular venue. A comment automation on your best-performing reel, triggered on a word your caption asks for, sending a link to your public portfolio, costs nothing and answers at 2am. Templated replies are free and unlimited.

That is the whole of the safe list, more or less: where your portfolio lives, which cities you shoot in, whether you travel, how somebody enquires properly. Fixed facts about you, not facts about anybody's photographs.

The gallery trap

Now the same words in a different mouth.

album, photos, gallery, link, pics, full set — these are the words a stranger types when they want to see your work, and they are also the words a past client's family types when they want the private gallery from their own function. One keyword list, two completely different requests, and an automation cannot tell them apart.

Never let a template send a client gallery link. Ever, under any trigger. Those galleries contain somebody's wedding, somebody's child's first birthday, somebody's family at a funeral, and the fact that a person knows the right word to type is not authorisation to receive them. The consequence of getting this wrong is not a lost booking. It is handing a stranger a private event.

The related one: "when are my photos coming?" from an existing client, six weeks after the shoot, politely. A template that answers with a timeframe is committing your editing queue on your behalf, to somebody who will hold you to it and screenshot it. Put delivery vocabulary in the negative list and let a person answer with a date they can actually meet.

The rights question, which is most of the rest

"Can we use this photo?"

It arrives from the venue, the decorator, the caterer, the makeup artist, the outfit designer, the couple themselves, the couple's relatives, and occasionally a brand that has already posted it. On Instagram this is a whole economy — vendors trade in each other's images and everyone assumes a tag settles it.

It does not settle it, and an automated reply must not pretend otherwise, in either direction.

A yes gives away a licence. Whether you are even in a position to grant one depends on what you signed with whoever commissioned the shoot, what releases exist for the people in the frame, whether the couple has approval rights over their own wedding images, and what your contract says about commercial versus editorial use. None of that is knowable from a keyword.

An automated no is nearly as bad, because these are the vendors who refer you work, and a curt template refusal from an account that never explains itself costs you the relationship.

Practically, that means use, usage, repost, rights, licence, license, credit, share kar sakte, permission, commercial, print, hoarding and brochure all belong in the negative keyword list. They stop the automated reply entirely and put the message in front of a person.

The takedown

The smallest category and the one to design for anyway: somebody in a photograph asking you to remove it.

A guest who did not know they were being shot. A person whose relationship has since ended. Somebody who simply does not want their face on a commercial account. These messages are often short, sometimes angry, and always urgent to the person sending them.

Nothing automated goes near this. Not an acknowledgement, not a friendly holding line, and certainly not a cheerful reply about booking. It is worth adding remove, delete, take down, hata do and mat post to the block list purely so that no automation is even in the room.

Takeover, and the group thread

The moment you reply by hand, automation is out of that thread permanently. In this business you are usually in the thread within a few hours anyway, because the enquiries are few and each one is a whole event.

One habit worth building alongside it: when a message turns out to be about rights, move it off Instagram in your first reply. Not because the platform is unsafe, but because a licence agreed in a DM is a licence you will be reconstructing from screenshots two years later when a hotel puts the shot on a billboard.

What it will not do

There is no gallery hosting, no delivery portal, no watermarking, no contract or e-signature, no payment links, no calendar to hold a date. Leads leave as CSV. No WhatsApp. 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, and that DM clock restarts only when they message you again.

Templated replies are free and unlimited; a credit is spent only when the AI writes a new reply. Free tier is 100 credits, no card, and packs start at ₹499. A photographer's honest build — a portfolio link, a coverage-area answer, and a long block list — barely spends anything, because everything expensive is a question you decided not to answer automatically.

If you also plan the events, the date problem is a different beast. Designers face the same usage-rights inbox, and what stops a send explains the checks that sit under all of it.