Published conclusion
Tier 2 — Market-Ready
The main appointment journey is directly verifiable and market-facing, but multiple quality defects prevent a mature-platform assessment. Keep Tier 2: core consultation workflow verified; defects and untested clinical depth block Tier 3.
Reverified assessment
Verified findings and limitations
Direct review observationsThe reviewer completed registration, email verification, login, doctor selection and consultation-booking/payment surfaces. The AI chatbot booking path and report download failed, and invalid month values were accepted.
Independent verificationThe current official site remains active and presents telehealth, consultation and AI-assisted health features.
Observed issuesAI booking failure; report download failure; date/input validation defects.
Testing limitationsClinical-quality claims and all post-consultation workflows were not tested.
Independent verification sources. Source 1
Contributor screenshot evidence
What was observed
These images formed part of the evidence pack considered during verification. Full-standard records retain the contributor's factual caption for each screenshot.
Sandbox verification
Seven checkpoint assessment
The verified result is the official public checkpoint record. For earlier-standard reviews, these findings may have been reconstructed from preserved evidence during Sandbox Africa’s 2026 audit; they are not presented as if the contributor originally completed a structured worksheet. Contributor-submitted checkpoint wording is shown only where explicit public reviewer attribution has been enabled.
Step 1 — The Existence & Accessibility Check
Is it live?Checking for dead links, infinite loading screens, or "Coming Soon" landing pages masquerading as live products.
Sandbox verifiedpassThe reviewer accessed the live iScript.Health service.
Onboarding frictionCan a user or enterprise actually sign up, or is it gated behind broken "Contact Sales" forms?
Sandbox verifiedpassRegistration, email verification, login and doctor-selection flows were completed.
Step 2 — Functional Testing (The "Try It Out" Phase)
Core loop executionDoes the application actually do what it claims to do? (e.g. a payment gateway completing a test transaction, a logistics app's routing engine working.)
Sandbox verifiedpartialConsultation booking/payment surfaces worked, but the AI chatbot booking path and report download failed.
User experience (UX) & interface (UI)Assessing the logical flow, responsiveness, and basic accessibility of the platform.
Sandbox verifiedpartialInvalid month values were accepted and failed AI/report flows created visible usability defects.
Step 3 — Technical & Architectural Assessment
PerformanceLoad speeds, uptime reliability, and basic stress responses.
Sandbox verifiedpartialThe main service remained usable during review; no controlled uptime/load test was performed.
Integration readinessAvailability, clarity, and functionality of API documentation and webhooks.
Sandbox verifiedpartialNo API/webhook integration workflow was independently exercised.
Security basicsSSL certification, basic encryption standards, and data handling transparency.
Sandbox verifiedpartialEmail verification was present, but input-validation defects and the absence of a deeper security audit limit confidence.
Company right of replyRepresent iScript.Health?
Claiming verifies company ownership and enables a response or additional evidence. It does not permit editing of the independent review.
Claim company profile