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.
Telemedicine blocks include AI summaries; homework, questionnaires, and agreements follow your practice language for clients; agreements pre-fill the therapist name; AINuma Meet context attaches to intake; hero banner and recording copy fixes; notes on every intake.
When a session is held in Spanish, French, or another language, the transcript and AI-generated summary can now follow that same language.
Session notes now follow your preferred structure more closely, with better headings and easier edits before you save.