A booking is rarely one person
A single wedding booking might need a lead photographer, a second shooter, a cinematographer and a drone operator - sometimes across two or three event days, sometimes with a different combination of people on each one. Tracking that over WhatsApp works until it doesn't: a crew member finds out they're double-booked from a client, not from the studio.
Assigning crew per event day
Studio CRM assigns team members to a booking at the event-day level, not just to the booking as a whole - so a two-day wedding can have a different crew on the mehendi than on the wedding day itself, all tracked against the same booking.
Conflict warnings before they become a Saturday morning crisis
Because every crew assignment is checked against that person's other bookings, Studio CRM flags a conflict the moment someone tries to assign an already-booked photographer to a second event on the same date - catching it while there's still time to reassign, not when two clients are both expecting the same person to show up.
What each crew member is actually owed
Freelance and in-house crew alike get paid per booking, and Studio CRM tracks exactly what's owed to each person for each job they're assigned to - so "how much do we owe the second shooter for the Sharma wedding" has an instant answer instead of requiring a search through old messages.
Marking payouts settled, not just remembered
Once a crew member is paid for a booking, marking that payout settled keeps the studio's own records honest - no relying on memory for who's already been paid and who's still owed, especially with freelancers who might work several bookings in the same month.
Where team management lives
Team assignment and payouts live inside each booking and roll up into their own Team tab, so a studio owner can see, across every active booking, who's assigned where and what's still outstanding - without opening each booking one at a time.