Faster Replies Book 9 More Weddings for Wedding Photographer Callum

Most of these case studies come from emails my readers send me. With their permission, I share them with the names changed. I do this so that others can learn from what worked and what didn't. Have a story of your own? Share it with me.

38%of inquiries booked, up from 14%
1.7 hrsaverage reply time, down from 19
9weddings booked in 10 weeks

The inquiry landed just before midnight on a Tuesday. A couple in Bath, a September date, a barn Callum had shot twice.

He saw it over breakfast and wrote back by 9.15.

Too late. “So sorry, we went with the first photographer who wrote back.”

That one email changed how Callum, a solo photographer in Bristol, England, answers every couple. You can copy his new wedding inquiry reply further down.

It takes five minutes to send. In ten weeks it booked six more weddings than his old one.

The problem

Callum shoots about 25 weddings a year. He gets most leads from his website form and a venue list.

He was proud of his reply. It was long, warm and full of detail.

It was also slow. He answered in batches, usually the next morning or the one after.

Here is what two months of inquiries looked like.

Measure	Before
Inquiries in 8 weeks	22
Average time to reply	19 hours
Length of his reply	about 310 words
Replies from couples	9
Weddings booked	3

His reply opened with a paragraph about himself. Prices hid in an attached PDF.

There was no question at the end. So a busy couple had nothing to answer, and most simply did not.

Callum is not careless. He works alone, and the inbox always sat behind the real work, shooting and editing.

He also guessed that rivals answered in a day. So he ran a small test.

Two friends sent a pretend inquiry to five local photographers. Three answered within three hours.

He also noticed two of his replies went to spam. That can happen when a message has a big attachment.

Heavy attachments from new senders often trip spam filters, and Gmail’s email sender guidelines show how much gets checked before a message lands.

The solution

Callum did not need a fancier template. He needed a faster, shorter one that asked something back.

He wrote a four-part reply he could send in five minutes. It is easy to copy.

Hi [Names], congratulations on [date] at [venue]!
I’d love to photograph it. [One line about that venue or a detail they shared.]
My wedding collections start at [price] and most couples choose [middle option].
Can I ask, what matters most to you about the photos?
I’m free for a quick call on [two options], or just reply here.
[Your name]

The first part says he read their note. The second shows he knows the place.

The third shares a starting price in plain text, with no attachment. The last part asks one easy question.

That question did the heavy lifting. A couple can answer it in one line from their phone.

Those four parts are the backbone of what to say in a first reply to any couple.

The process that worked

How fast is fast enough?

His first rule was a two-hour window from 8 a.m. to 9 p.m.

He turned on phone alerts for the website form. He also saved the reply as a snippet on his phone.

A late-night inquiry got an answer at 8 a.m. sharp. He felt that was fair, and so did couples.

What goes in a wedding inquiry reply?

He kept it near 90 words. That is about what fits on one phone screen without scrolling.

He moved his “about me” story to the bottom of his website, where curious couples could find it.

He gave a starting price, because a hidden price made couples guess. Guessing often ends in silence.

What about the venue line?

This took two minutes per inquiry. He searched the venue name and found one real detail.

Examples were the walled garden, the long staircase and the barn’s west-facing doors.

Couples noticed. Three of them wrote back, “You actually know the place!”

It also gave him something easy to talk about on the call.

What happens after the reply?

If nobody answered in three days, he sent one short nudge.

Hi [Names], just checking my note found you. Still happy to chat about [date]. No rush at all.

He sent only one nudge. Two felt pushy to him, and he trusted that.

Ten weeks later

He tracked the next ten weeks in a simple notes app.

Each week he wrote down how many inquiries came in and how long each reply took. It took about five minutes on a Sunday.

Measure	Before	After
Inquiries	22	24
Average time to reply	19 hours	1.7 hours
Length of his reply	310 words	92 words
Replies from couples	9	19
Calls booked	4	12
Weddings booked	3	9

The number of inquiries barely moved. What changed was how many couples answered.

The share who booked went from 14% to 38%. At his average package, that is about $15,000 more booked over the same stretch.

What we learned from here

Callum did not write better. He wrote shorter and sooner.

Speed and one easy question beat a perfect letter. That is the whole secret of a good wedding inquiry reply.

Here is what he kept and what he dropped.

What worked	What did not
Replying within two hours	Batching replies to the next morning
One real detail about the venue	A paragraph about himself
A starting price in the email	A PDF attachment
One easy question at the end	Ending with “Let me know!”
One nudge after three days	Three nudges in a week

A price in the first email did cost him two couples. They said it felt “quick” and politely passed.

He sees that as fine. They would have passed later, after more of his time.

His phone snippet also needed a small fix. It once went out with the wrong venue name.

So he now reads the second line out loud before he sends.

Couples who booked often said the same thing. “You were the first to answer, and you made it easy.”

Time is the hidden cost. Fast replies took him about ten minutes a day, and he felt that was a fair trade.

Want to copy this? Start small. Write the four-part reply once, save it, and turn on alerts. That is about 30 minutes of work.

He has since added a clear PDF of his prices, built like a wedding photographer pricing guide, so the number in the email never surprises anyone.