Use this page for pilot onboarding, import troubleshooting, diagnostics, and contact paths while the hosted backend is being configured.
Minimum items to verify before inviting a pilot contractor.
These are the first pilot walkthroughs to record or screen-share with a new user.
Show company name, workspace URL, domain, role selection, profile menu, and company switching.
Select Membership, upload the XLSX/CSV file, review mapped fields, and commit the import.
Select Inside sales, upload unsold estimate exports, and confirm value, last follow-up, and next step fields.
Use row selection, range selection, next action buttons, notes, closed outcomes, referrals, payout, and metrics.
Use these checks when a list does not parse, maps poorly, or creates unexpected duplicates.
Use `.xlsx` or `.csv`, confirm the browser can reach `node_modules/jszip/dist/jszip.min.js`, and retry from the package root or `/src/` path.
Check that the correct import profile is selected. Membership files should include expiration and package context; inside-sales files should include opportunity value and follow-up context.
Renewal Desk merges likely duplicates by stable customer identifiers, contact details, and import fingerprint while preserving existing action history and notes.
Open the profile menu, download diagnostics, and send that file with the import file type, browser, screenshot, and what you expected to happen.
The static app is local-first until Supabase is configured.
Create a Supabase project, run `docs/supabase-schema.sql`, then set the public project URL and browser-safe anon key in `config/runtime.js`.
Each rep should have their own login inside a shared company workspace. Do not share one team login, because it breaks audit trails and revocation.
Uploaded customer lists are contractor workspace data. They should not be sold, rented, brokered, or used for Renewal Desk marketing.
For pilot support, email the issue with diagnostics and the exact workspace context.