Browse documentation

Business Operations

Client Management (CRM)

The single, organization-wide client record behind every booking, gallery, and invoice — and why a client is never treated as a stranger at your other branches.

In most tools, a client who books at your downtown studio and later books at your other location looks like two different people — two separate records, two separate histories, no memory of who they are. Peasier doesn't work that way.

One client, not one per branch

Every client is a single record shared across your whole business — not duplicated per branch. The first time someone shows up in a booking, an invoice, or a gallery, Peasier creates their record automatically by matching their email address. If that same email books again — at the same branch or a different one — it's recognized as the same person, not created as a new client.

In practice: say a bride books her engagement shoot at your Lekki branch, then books her wedding six months later at your Victoria Island branch. Staff at Victoria Island open her client profile and see the engagement shoot, the invoice she paid, and every gallery she's already received — before the wedding has even happened. She's never treated as a stranger just because she walked into a different door.

What's shared everywhere, and what isn't

A client's core identity — name, email, phone number, and whether they're flagged sensitive — is shared across every branch the moment it's set. What's scoped to a branch is which staff see that client in their day-to-day directory: a staff member only sees the clients who've actually had a booking, gallery, or invoice at their own branch, worked out automatically from that activity. Nobody has to manually decide which branches a client "belongs to."

Finding a client without creating a duplicate

When staff start a new booking or invoice, a fast, organization-wide search checks whether the client already exists — by name or email — before creating anything new. This is what actually prevents "Sarah Johnson" from ending up as three separate, disconnected client records because three different staff members typed her name in slightly differently at three different branches. The full client directory a staff member browses day to day, on the other hand, only shows clients tied to their own branch, so it stays relevant to what they're actually working on.

What a client's history tells you

Every client's profile carries their real history with your business: every gallery delivered to them, every invoice sent (and whether it was paid), and their total revenue — tracked separately for Naira and Dollar invoices, since currencies are never mixed together. A staff member preparing for a shoot, or a studio owner deciding who to prioritize for a discount, isn't starting from zero — they're looking at a client's entire relationship with the studio, not just today's booking.

What this makes possible

Because a client's full history already follows them to every branch, Peasier's client model is a real foundation for recognizing and rewarding repeat clients — a returning-client badge when they come back to book again, or a loyalty or referral program down the line. That isn't a feature Peasier ships today, but it's worth knowing the identity model underneath already supports it, rather than something that would need to be rebuilt from scratch later.

Protecting high-profile clients

A client can be flagged so that only owners, admins, and explicitly approved staff can see them at all — see Sensitive Clients for exactly how that works and what it hides.