zimi.chat help

Overview of the Zimi flow

This page gathers the most important app entry points and explains who uses what. Use the links here when testing onboarding, the provider dashboard, or the admin portal.

Quick links

Zimi onboardingSeller login for creating new providers in the field, QR links, and WhatsApp onboarding.Zimi dashboardThe provider's daily app for conversations, sharing, settings, and receptionist testing.Admin portalZimi's internal control panel for providers, sellers, WhatsApp numbers, modules, and operations.Endpoint overviewTechnical overview of pages, API endpoints, roles, and security model.

How the flow fits together

1
A seller signs in to Zimi onboarding with seller ID and PIN.
2
The seller creates a provider, selects or receives a Zimi-managed WhatsApp number, and shows the QR code.
3
The provider scans the QR code, tests the flow, and then uses the Zimi dashboard for daily operations.
4
Zimi admin follows onboarding, providers, sellers, and WhatsApp numbers in the admin portal.

Roles and access

Seller: signs in through onboarding with seller ID and PIN. Sellers can only create providers and see onboarding context.

Provider: signs in to the dashboard with the provider zimi-id and PIN. Providers can only see their own conversations, settings, and sharing links.

Admin: signs in with Google OAuth and must have the admin role in Supabase app metadata. Admins can manage providers, sellers, WhatsApp numbers, and modules.

Human escalation

The provider has full access to all customer conversations in the dashboard and can reply directly at any time. That human provider reply is the escalation path required by WhatsApp policy when Zimi cannot resolve something, when the customer asks for a person, or when a request is sensitive. If a customer cannot contact the provider, for example a salon, through Zimi, they can always message the provider directly on WhatsApp outside the Zimi platform.

WhatsApp and email consent

Zimi supports inbound replies and selected outbound messages on WhatsApp and email. Consent has two levels, and the provider owns that consent.

1. Inbound-only baseline: the customer starts the normal conversation. Zimi can reply in that thread, and the provider can continue from the dashboard.
2. Utility messages: booking reminders and no-show follow-ups can be sent on WhatsApp Templates or email when the customer gave consent at booking or first contact.
3. Marketing messages: Google review requests, dormant customer reactivation, and future promotional or engagement messages require a separate explicit marketing opt-in, distinct from utility consent. WhatsApp marketing uses approved Meta Templates, and marketing emails must include an unsubscribe link.
4. General rules: respect opt-outs immediately, keep proof of consent, and never message customers who have not opted in at the correct level.

Legal