Create a timely, human follow-up cadence that answers concerns and makes booking easier.
Use this resourceTo follow up with photography leads, respond to the original context, answer one likely concern, add useful proof or clarity, give one easy next step, and use a finite cadence with explicit stop conditions. Track the last contact and dated next action so follow-up is consistent without becoming pressure.
Adapt timing to the service’s decision cycle and stop immediately on reply, booking, decline, poor fit, or opt-out.
Review the requested service, date, location, client goal, prior messages, and what you asked them to do. Follow-up should continue the conversation rather than restart it.
Put it into practice: Write a one-sentence statement of the likely decision or unanswered question.
Useful evidence: The message could not plausibly have been sent to every lead in the database.
Useful follow-up can clarify availability, package fit, booking steps, delivery, planning, proof, deadline, or a direct answer. Repeated “checking in” gives no new reason to respond.
Put it into practice: Choose one relevant concern and answer it concisely.
Useful evidence: The lead can make progress even before replying.
Ask for the smallest decision that advances the process: answer a question, choose consultation time, review a relevant proposal, or complete defined booking.
Put it into practice: Remove competing links and vague requests.
Useful evidence: A prospect can state exactly what to do next.
Timing depends on urgency, event date, value, and decision cycle. Use a few purposeful contacts and a gracious close rather than indefinite automation.
Put it into practice: Define intervals, message purpose, owner, and final close for each service.
Useful evidence: Every sequence has a known end and no open lead lacks a dated action.
A reply should route to a person; booking stops sales follow-up; decline or opt-out closes it; changed availability updates the offer; an issue pauses promotion.
Put it into practice: Test each stop condition and channel reply path.
Useful evidence: No client receives a contradictory message after their status changes.
Record booked, unavailable date, price, timing, service mismatch, another choice, no response, or unknown without inventing a reason. Compare response and booking by service, source, and cadence.
Put it into practice: Review a sample of lost conversations for clarity and fit.
Useful evidence: Changes are based on repeated patterns rather than one rejection.
There is no universal number. Use a finite sequence where each message has a purpose, then close graciously.
Match timing to event urgency and decision cycle. High-demand near-term dates may require faster clarity than future portraits.
Reference the request, answer a likely concern, add relevant proof or clarity, and offer one simple next action.
Stop on booking, clear decline, opt-out, poor fit, or another condition defined by the workflow; route replies to a person.
Only when the client provided appropriate permission or expectation for that channel and local rules are followed.