How customers are created
There is no separate customer directory to maintain: a customer record is created when a person completes a booking through the public surface. The booking intake form collects the identity information the service requires — typically name, email, and phone — and that information becomes the customer's record within the tenant.
Linking a customer to a login
A customer can bind their record to an authenticated account. Once bound, the customer account surface shows their bookings directly: they can view their appointment context, and manage bookings through the token-based management link they received at booking time. Binding is per-tenant — a customer's identity on one business never grants visibility into another.
Data handling
Customer-identifying fields — email, name, phone, address — belong to a closed forbidden set in the platform's redaction policy. They are refused from release evidence artifacts, redacted from error contexts, and must never appear in public artifacts or screenshots. Staff see customer context only as far as their role allows, and only for bookings they are involved in.
Do not fabricate customer data
Testing and documentation must use seeded or obviously-fake customer data. Real customer identity is never used as illustration material. If you need test customers, seed them through the test harness with redacted placeholders.