Inquiry is operational work
The workflow starts before booking by capturing source, acknowledging receipt, assigning response, and defining outcomes.
Adapt it: Adjust response commitment and qualification for your service and working hours.
Follow an example client workflow from a new inquiry through booking, session, delivery, review, and referral.
Use this resourceThis portrait photography workflow example shows a complete 28-day client journey from inquiry through booking, preparation, session, gallery delivery, review, and referral. Exact timing should change by service, but every stage needs a trigger, owner, client communication, deadline, completion condition, and exception path.
Use the example to model one primary service, then test paid, overdue, replied, canceled, and rescheduled paths.
Trigger: Website form submitted.
Automatic: Create lead, record source, send acknowledgement, assign response due in four business hours.
Human: Review request, availability, and fit; send recommendation.
Complete when: Consultation booked, direct booking offered, or lead closed.
Trigger: Proposal or booking link sent.
Automatic: Follow-up due in two days; proposal expires in seven days.
Human: Answer questions and document changes.
Complete when: Agreement and $200 reservation payment received.
Automatic: Send confirmation, create session, questionnaire due in seven days, balance due seven days before session.
Human: Add personal welcome note and review questionnaire.
Complete when: Planning notes and client actions are resolved.
Seven days before: Review location, weather, payment, participants, access, and equipment.
Two days before: Send concise reminder.
Complete when: Final readiness check passes.
Session day: Photograph and back up files.
Next business day: Send thank-you and confirm three-week delivery range.
Production: Cull, edit, quality-check, export, and client-test gallery.
Send gallery access, download, rights, product, expiration, and support instructions.
Three days later: Confirm access.
After satisfaction: Request review; later request referral or relevant rebooking.
Complete when: Gallery, products, support, finance, and archive tasks close.
Use the example to model one primary service, then test paid, overdue, replied, canceled, and rescheduled paths.
The workflow starts before booking by capturing source, acknowledging receipt, assigning response, and defining outcomes.
Adapt it: Adjust response commitment and qualification for your service and working hours.
Proposal sent is not booked. The example requires agreement and payment before calendar and onboarding change.
Adapt it: Use the booking requirements from your actual reviewed process.
Reliable administrative tasks are automated while recommendations, answers, and questionnaire review remain human.
Adapt it: Keep sensitive, creative, and unusual decisions assigned to a person.
Preparation and balance dates move with the session instead of relying on manually entered calendar reminders.
Adapt it: Update every dependent action after a date change.
The production stage includes file protection and client expectation before editing.
Adapt it: Add service-specific proofing, commercial approval, album, or retouching steps.
The record does not close merely because a gallery link sent; products, support, finance, and archive remain visible.
Adapt it: Define every obligation that survives digital delivery.
Use enough to represent meaningful changes in responsibility or client state without creating labels that drive no action.
Automate predictable logistics and keep judgment, creative advice, and sensitive communication human.
It is observable evidence that a stage is finished, such as signed agreement and received payment.
It updates the appointment and every dependent deadline, message, payment, team, and preparation action.
After all contracted deliverables, support, financial, archive, and chosen follow-up obligations are complete.