Every shop app should start here — most start at the calendar

What actually lives on a client record

Contact channels, past and upcoming appointments, deposit states — pending, paid, applied, forfeited, refunded — signed consents, and creative references tied to work already done or currently being quoted. When someone books again, the artist sees real history instead of starting from a blank slate.

Multi-tenant boundaries mean these records belong strictly to your shop — not a shared industry-wide client graph, even though Inkdesk runs many shops on the same platform.

Good records shorten consults dramatically. Prior piece photos, an allergy flagged at consent, and which artist a client already trusts is the actual difference between a twenty-minute rebuild of context and a five-minute confirmation before getting straight to work.

When someone's forfeited a deposit or canceled repeatedly inside your window, that pattern should be visible before you hand them another premium Saturday slot on trust alone. Policy stays fair and firm precisely because the record remembers what happened last time.

It also helps with the awkward version of this conversation nobody enjoys: a client who wants to dispute a forfeited deposit or argue about a policy they claim they never saw. Having a record that shows exactly when they booked, what they were told at the time, and whether they signed consent acknowledging the same policy turns a heated argument into a quick, factual conversation — which is a better outcome for everyone involved, including the client, who at least gets a straight answer instead of a shrug.

Keeping online, phone, and walk-in clients as one person

Public booking matches or creates a client by phone number inside the shop tenant. Walk-ins created straight from the day board hit the same table. Waitlist joins store intent until a cancellation or no-show opens a slot, and `waitlist.filled` can fire for anything else you've connected.

That's what stops you paying the tax of 'the Instagram name' versus 'the name on the card' versus 'whatever they told the front desk' all being separate mental records for the same actual human being.

Phone-led identity means one person doesn't turn into three separate records because they booked once online and once as a walk-in. Train the front desk to search before creating a new client — duplicates are the single fastest way to lose the value of all this history.

How this actually supports money and policy decisions

Deposits through Stripe Connect are per booking, but readable in the client's full context when a pattern matters — 'three forfeits in the last year' is a real operational signal, not a coincidence to ignore. Cancel windows, commonly around 48 hours, and card minimums around $20 stay consistent because the rules are shop-level, not reinvented per artist in whatever their personal text thread happens to say.

Artist payout tracking still concerns compensation models — commission, booth rent, hybrid — not client CRM fields directly, but completed work sitting on the client's file is exactly what gets reconciled against later.

Privacy and who on staff sees what

Staff access the cabinet with Google login and role permissions. Not every artist needs every settings panel, and client medical or consent detail should follow least-privilege access as you assign roles across a growing team.

Station and iPad check-in shows arrival flows without ever handing a client the full CRM. Portfolio and the booking widget only surface what you've chosen to publish — the underlying client record stays internal.

This matters more as a shop grows past its founding owner-operator stage. A two-chair shop where the owner personally remembers every client can get away with loose access habits; a six-chair shop with rotating staff and guest artists cannot, and the cost of getting it wrong — a client's medical detail or contact info seen by someone who had no reason to need it — is exactly the kind of thing role-based access is built to prevent.

How client data closes the loop across the whole shop

Online booking and the widget create or update the client; a deposit through Stripe Connect attaches money state to their appointment; reminders use their contact channels; a consent PDF lands on the file; check-in confirms arrival; completed work informs the next booking and feeds artist payout reconciliation.

Waitlist joins keep a high-intent client attached to a specific artist even while the calendar looks fully booked. The moment `waitlist.filled` fires for any connected integration, the CRM already knows exactly who converted.

Google staff login plus roles keeps that history available to whoever actually needs it — front desk, managers, artists — without a single shared password living on a sticky note by the register.

For a shop that's grown past the point where one person can hold every client's history in their head, this is less a convenience and more a requirement — the alternative is a front desk that has to ask every returning client to re-explain themselves from scratch, which reads as impersonal at best and unprofessional at worst for a business built on repeat trust.