Return From The Veil Online
Plumbing AI Receptionist

One front door for your agency and every active tenant.

This homepage is the explainer layer for the platform. It gives agency staff and clients a clear place to orient themselves before logging in, while Supabase continues to handle authentication, tenant access, dashboards, bookings, and reporting behind the scenes.

Use this page as the branded landing point on Cloudflare Pages. The application screens remain in the `.html` files, and the shortened URLs can still resolve cleanly when you want them to.
Before Login

Who this portal is for

This portal is for internal agency operators and onboarded plumbing clients. It is not a public customer booking page.

Agency Admin Client Admin Dispatcher Tenant Scoped
What's Live

Current platform capability

Tenant onboarding, Google Sheet copying, lead capture, call logging, dashboard access, and calendar-direct booking for full-service accounts are already active.

Supabase Auth RLS Google Sheets Calendar Booking

What users should expect

  • Agency admins can review tenants, onboarding progress, and operational status.
  • Client users can review leads, call activity, and dashboard information tied to their business.
  • Full-service tenants can run calendar-direct booking workflows.
  • Pilot tenants stay limited to the lighter request-only service model.

Access points

Standard Login

Use the main sign-in screen first when you need authenticated access into the platform.

Open login.html

Agency Console

Use the agency management console for internal operations, tenant oversight, and administrative control.

Open /admin_management

Client Dashboard

Use the client dashboard for tenant-facing lead visibility and account-level reporting.

Open client-dashboard.html

Clean Short URLs

You can still shorten the path in the browser. The `.html` files remain the source pages behind those routes.

Try /login

Operational note

This homepage should stay informational and stable. It should explain what the system is, who should log in, and where each user type belongs. The application logic should remain in the dedicated dashboard pages rather than being duplicated here.