Service status
Anxio is still being built, so this page reports what is working and what remains rather than pretending every service is production-ready. If something is broken for you and this page says nothing about it, tell us — we would rather hear twice than not at all.
Code reviewed 17 Sept 2026. Expand each area for what is built, what remains and current limitations. Production uptime, account email delivery and booking have not been verified by this review.
64%
estimated implementation work remains, averaged equally across the 9 areas below. Percentages are rough code-review estimates, not measured uptime, launch readiness or time remaining. The detailed breakdown is the basis for this report.
36% implemented (estimate)
Website
The main site, expert directory and expert profiles are implemented.
Building
85% built · 15% remaining (est.)
View breakdown
Built so far
- Homepage, guided intake flow, shared navigation, footer and responsive page layouts are implemented.
- Contact links, an immediate-help page, page metadata and a sitemap are present.
- The expert directory has a five-column desktop grid, search, full profiles and real published expert records.
- Expert portraits are uploaded to the public Supabase Storage bucket and displayed on cards and profiles.
Still to do
- Complete the FAQ and expert application form.
- Finish content review and verify accessibility, mobile layouts and navigation across the site.
Current limitation: A page being present does not mean the service it describes is available.
Sign in and accounts
Dedicated signup, login, password recovery and logout flows are implemented.
Building
85% built · 15% remaining (est.)
View breakdown
Built so far
- Separate signup and login pages connect to authentication, with server-side validation and rate limiting.
- Password recovery, password reset, authentication callbacks and logout handlers are implemented.
- Staff login and server-side permission checks have unit test coverage.
Still to do
- Connect the homepage name, email and password steps to real account creation.
- Configure account email delivery in the final setup phase and verify signup, recovery and staff access in the deployed environment.
Current limitation: The homepage Create account step currently only advances the interface; it does not create an account.
Finding a therapist
Guided intake now generates an AI reply and ranks real published experts against the concern.
Building
85% built · 15% remaining (est.)
View breakdown
Built so far
- The homepage collects a concern and requests a short AI reply in the background while account details are collected.
- The separate intake form has a server pipeline for crisis checks, concern extraction, therapist matching and fallback handling.
- Each session loads every published expert profile from Supabase, sends the saved matching fields to AI, validates the ranking and reveals the top results one by one.
- Sessions receive a long UUID URL and currently use a JSON-backed server session seam for later persistence.
- Unit tests cover extraction failures and the intake pipeline, including crisis routing.
Still to do
- Connect the homepage password step to real account creation and persist intake sessions durably.
- Complete booking and verify matching, availability and expert ranking in the deployed environment.
- Complete review of intake wording and verify immediate-help routing throughout both intake experiences.
Current limitation: Booking is not open yet, and the temporary session store is process-local until it is replaced with durable persistence.
Account dashboard
The signed-in dashboard is designed, but its care and payment information is sample data.
Building
30% built · 70% remaining (est.)
View breakdown
Built so far
- The account page requires sign-in and displays the signed-in email.
- Layouts exist for profile information, a matched expert, upcoming and past sessions, and payment history.
Still to do
- Replace sample profile, expert, session and payment information with records belonging to the signed-in person.
- Connect account controls and session actions to working services, and verify access restrictions.
Current limitation: Displayed sessions, receipts and profile details are demonstrations, not actual bookings or transactions.
Staff workspace
Protected staff access and team screens exist; operational workflows are unfinished.
Building
35% built · 65% remaining (est.)
View breakdown
Built so far
- Staff access is checked on the server and workspace views depend on assigned permissions.
- Team lists, employee entry and task editing interfaces are implemented.
Still to do
- Save employee and task changes to persistent records; current changes only update the page state.
- Connect the remaining workspace panels to real workflows and verify permissions for each action.
Current limitation: The team workspace uses sample records. Editing a team does not provision a staff login.
Booking and payments
Slot reservation and payment processing are not implemented.
Building
0% built · 100% remaining (est.)
View breakdown
Built so far
No working service implementation yet.
Still to do
- Build availability selection, slot reservation and booking confirmation.
- Integrate checkout, payment verification, receipts and refund handling.
- Verify cancellations, failed payments and protection against duplicate bookings or charges.
Current limitation: Sample prices and payment history do not represent a working checkout.
Sessions
Joining a therapy session by video, voice or chat is not implemented.
Building
0% built · 100% remaining (est.)
View breakdown
Built so far
No working service implementation yet.
Still to do
- Integrate a session provider and build the joining experience.
- Connect session access to confirmed bookings and the correct participants.
- Verify device permissions, connection failures and session completion.
Current limitation: Session cards in the account dashboard are previews; they do not provide a live session.
Email delivery
Account email setup is planned for the final phase; newsletter delivery is not connected.
Building
0% built · 100% remaining (est.)
View breakdown
Built so far
- Account actions request signup and recovery emails through the authentication service.
- The newsletter form validates submitted email addresses.
Still to do
- Finish frontend and backend work, connect the domain, then configure the email sender and verify delivery.
- Connect newsletter storage and delivery, with consent, confirmation and unsubscribe handling.
Current limitation: Delivery has not been verified by this review. Newsletter submissions currently neither store an address nor send mail.
Service monitoring
This is a manual development report; automated health reporting is not connected.
Building
0% built · 100% remaining (est.)
View breakdown
Built so far
No working service implementation yet.
Still to do
- Connect automated uptime and dependency checks, with timestamps and last-known results.
- Add incident reporting and verify alerts and outage handling before claiming services are operational.
Current limitation: This page cannot confirm a live outage, provider availability or production uptime.
Email setup is planned for the end of development, after frontend and backend work is complete and the domain is connected. Account email delivery will be configured and tested then.
Automated uptime checks are not running yet, so nothing here is being measured. Once they are, the areas that have shipped will report real results instead of progress.
If something is not working
Tell us what happened — the page you were on and what you expected is enough. Please do not include anything you would not want stored in an email.
Support does not depend on this site being up. If you need someone now, Tele-MANAS is free, 24/7 and answers across India on 14416, and other lines are listed here.