After sign-up, your tenant receives demo patients and confirmed appointments from the server—nothing is created in the browser. Your chosen app language is sent to the API for registration and intake transcript/summary. The dashboard calendar loads those appointments even when the scheduling resources list is still empty.
Patients and calendar: New accounts should see two demo patients on the Patients page and two confirmed demo appointments on the Dashboard for the current period. All of that data comes from your backend workspace, not from local seeding or mock data in the app.
Locale: Sign-up and API requests respect the language you are using in the app (including Accept-Language and localized intake content when you open session detail). Changing language refetches intake transcript and summary for the new locale.
Scheduling resources: If your branch does not yet return rows from the scheduling resources endpoint, the calendar can still infer resource context from existing appointments so you are not blocked by an empty resource list. For a fully consistent setup (slots, blocks, booking), your backend should still provision schedule resources that match those appointments.
Track post-session actions—homework, questionnaires, reminders, and therapist tasks—in one place on the patient record, with optional AI suggestions from reviewed session summaries.
Therapists can add an AINuma intake & booking widget to their own website: create a widget key in Settings, copy a direct link or ready-made HTML button, and optionally embed the full flow in an iframe.
New demo users get a persistent side-panel walkthrough across dashboard, calendar, patients, and clinical workflows—with highlights on the real UI. Demo trials now start on the server for every first-time entry (free-trial page or Login sign-up), so onboarding and entitlements stay in sync.