How Photography CRM Automation Actually Works
Eight rules. Seven timings. Six recipes. No canvas, no connecting lines, no weekend spent configuring.
No credit card required
"Automation" in software marketing usually means a screen with boxes and arrows that you are expected to spend a weekend configuring. That is not what a photographer needs. A photographer needs the balance reminder to go out four days before the shoot whether or not they remembered, and to stop going out the moment the money arrives.
This page explains the mechanism precisely: what fires, what triggers it, and what you stop doing by hand.
The precondition: automation on the wrong channel is worth nothing
Before any of the mechanics matter, the channel has to be right. An automated email sequence to an Indian client is a sequence of unread messages. It will show as sent in the CRM, the dashboard will report activity, and the balance will still be unpaid.
Studio Ryzen's automations produce WhatsApp messages, composed and prefilled, opening on your own number. The last tap is yours. That is a deliberate limit rather than a shortcoming: a payment reminder that goes out entirely unattended, from a system, to a family in the middle of a wedding week, is how a studio damages a relationship it spent a year building.
What actually triggers a step
Every rule is tied to something that has happened or failed to happen. Nothing fires on a schedule alone.
| Trigger | What the automation does | What it stops doing |
|---|---|---|
| An inquiry arrives and nobody has replied | Prompts the follow-up, with the message already written | Once you reply, or the lead is marked lost |
| A quote has been sent and not accepted | Prompts a nudge after your chosen interval | The moment the quote is accepted |
| A booking is confirmed but the advance is unpaid | Prompts the advance reminder | When the advance is recorded |
| A shoot date is approaching with a balance outstanding | Prompts the balance reminder ahead of the date | When the balance is recorded |
| A booking reaches Booked | Drafts the pre-shoot questionnaire onto the booking | Once the questionnaire comes back |
| Delivery is complete | Prompts the review request | When the review is received |
The second column is the one that matters and the one most tools get wrong. A reminder that keeps arriving after the client has paid is worse than no reminder, because it tells the client that nobody at the studio is looking.
Eight rules and seven timings
The automations screen has eight rule toggles and seven timing values. That is the whole surface. You decide whether each rule is on, and how many days it waits. There is nothing else to configure and no second screen where the real settings hide.
Deliberately small. A studio that can see its entire automation configuration on one screen can reason about what will happen next week. A studio with forty conditional branches cannot, which is how duplicate reminders and contradictory messages get sent.
Recipes: the setup step, removed
Six named recipes preset those toggles and timings for a kind of work: wedding booking, pre-wedding, newborn, birthdays and events, corporate, and album and delivery. Pick the one that matches what you shoot and the rules are set.
A recipe is only a preset of the toggles and timings the automations screen already owns. It creates no rule of its own, no hidden trigger, no extra message. That is why applying one, or switching between them, cannot produce a duplicate reminder - there is no second set of rules for it to add.
Everything a recipe sets is still visible and still editable afterwards. The recipe is a starting point, not a mode you get locked into.
Where the messages come from
Six workflow messages ship with each of the twelve package blueprints. A blueprint carries its events, its payment split and its whole message set, so creating a booking from one means the conversation is already drafted: the confirmation, the advance request, the pre-shoot note, the balance reminder, the delivery message, the review request.
You can edit any of them. Most studios change two or three words and leave the rest.
What is not automated, and why
- Sending. The message is written for you; the last tap is yours, so nothing goes to a client that you have not seen.
- Deciding a lead is lost. Studio Ryzen prompts; it does not close leads on your behalf.
- Pricing. No rule changes a quote or applies a discount.
- Anything the client cannot act on. The portal never asks a client to do something only the studio can do.
The line is consistent: automation removes the remembering, not the judgement.
What this looks like across one booking
An inquiry arrives from the public booking page at midnight. It is in the pipeline before you wake up, with the follow-up drafted. You send it over WhatsApp at breakfast. The client accepts the quote; the invoice is created from it without you opening the invoice screen. The advance reminder is prompted, then stops the day the UPI payment is recorded. The pre-shoot questionnaire is drafted onto the booking when it reaches Booked. Four days before the ceremony the balance reminder is waiting. After delivery, the review request.
None of those steps required you to remember a date. That is the entire claim, and it is a smaller one than most automation pages make.
Related reading
For what this looks like from the studio's side rather than the mechanism's, see the automated photography CRM page. For the channel specifically, see the WhatsApp CRM page. For the category overview, start at the photography CRM India hub.
Frequently Asked Questions
- What does photography CRM automation actually do?
- It sends the follow-ups, reminders and requests that you would otherwise have to remember: the nudge on an unanswered inquiry, the advance reminder, the balance reminder before the shoot, the review request after delivery. Each is tied to a real event and each stops as soon as the thing it was chasing has happened.
- Can automated follow-ups go out on WhatsApp?
- Yes. Studio Ryzen composes the message and opens WhatsApp on your own number with it prefilled. The final tap is yours, so nothing reaches a client unseen, and because it sends from your number there is no per-message platform fee.
- Will automation send duplicate reminders?
- No. Each rule stops when its condition is resolved - a recorded payment ends the payment reminders. The six recipes only preset toggles and timings that already exist rather than creating rules of their own, so applying or switching a recipe cannot add a second copy of anything.
- Do I have to build a workflow?
- No, and you cannot. Studio Ryzen deliberately has no visual workflow builder. There are eight rule toggles and seven timing values on one screen, plus six recipes that preset them for a kind of work.
- How long does it take to set up automation?
- Applying a recipe sets every rule and timing at once. Most studios then adjust two or three timings to match how they work. There is no flowchart to design and no second configuration screen.
- Can I turn automation off?
- Every rule is an individual toggle, so you can run all of them, some of them, or none.
Ready to Grow Your Photography Business?
Start your free 14-day trial. No credit card required. See the difference in your first week.
No credit card required · Cancel anytime