Test scope, screenshots, checkpoint findings and tier rationale were supplied by an identified reviewer. Identity is retained internally unless public attribution is explicitly enabled.
Contro
Contro is a South African sexual-health and telehealth service connecting patients with licensed clinicians through online consultations, treatment workflows and delivery/refill services.
Sandbox Africa checked the submitted evidence and promoted the verified checkpoint record. Any visible adjustment is identified rather than silently rewritten.
The official public tier and technical record below are the verified publication outcome.
Tier 2 — Market-Ready
Keep Tier 2. The core patient product is live and directly accessible, while the uncompleted clinical endpoint and enterprise controls prevent Tier 3.
What worked: Website; AI chatbot; sign-up; email verification; login; dashboard; service selection; virtual-nurse assessment; information retention; order history; payment gateway entry; payment/cancellation emails. What failed / remained inaccessible: Full treatment transaction could not be completed because payment was required; Google address search did not work reliably, although manual entry was available. Errors found: Google address-search was unreliable. No broader authentication failure was observed. Access limitations: Full end-to-end treatment completion could not be assessed because payment was required.
Why not one higher: Tier 3 would require successful end-to-end validation of the complete treatment and payment transaction.
Verified findings and limitations
The intern directly completed registration and health-questionnaire/dashboard steps, but did not complete the paid clinical outcome.
The current official Contro surface continues to describe online consultation, licensed healthcare professionals, free delivery and chronic-service refills.
No critical defect was established in the directly tested onboarding/questionnaire path.
Payment, clinician consultation, prescribing and fulfilment were not independently completed.
What was actually assessed
The website was functional and responsive. Registration, verification, sign-in and dashboard access were successfully tested. The treatment journey could be followed through personal-information collection and virtual-nurse assessment, but the final transaction could not be fully validated because payment was required.
Edge on Windows 11
New public account
Access limitations: Full end-to-end treatment completion could not be assessed because payment was required.
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.
Shows that the login function works and does not accept invalid inputs
Shows that an email was sent to verify my email adress.
Shows the availability of the dashboard once logged in.
Shows the secure payment gateway
Show the email received after payment was cancelled
Shows the response shown after entering your registartion in the website
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
Checking for dead links, infinite loading screens, or "Coming Soon" landing pages masquerading as live products.
Website functional and accessible.
Can a user or enterprise actually sign up, or is it gated behind broken "Contact Sales" forms?
Low friction because registration requires minimal information and the verification process worked correctly.
Step 2 — Functional Testing (The "Try It Out" Phase)
Does 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.)
The website was functional and responsive. Registration, verification, sign-in and dashboard access were successfully tested. The treatment journey could be followed through personal-information collection and virtual-nurse assessment, but the final transaction could not be fully validated because payment was required. Editorial proposal adjusted from not_assessed to partial using current independent verification and the established gated-product/safety-critical rules.
Verification adjustmentAssessing the logical flow, responsiveness, and basic accessibility of the platform.
Good and easy to navigate Evidence was not sufficient for a stronger conclusion in this assessment.
Verification adjustmentStep 3 — Technical & Architectural Assessment
Load speeds, uptime reliability, and basic stress responses.
Good and fast performance Evidence was not sufficient for a stronger conclusion in this assessment.
Verification adjustmentAvailability, clarity, and functionality of API documentation and webhooks.
Not publicly assessed Editorial proposal adjusted from not_assessed to partial using current independent verification and the established gated-product/safety-critical rules.
Verification adjustmentSSL certification, basic encryption standards, and data handling transparency.
Apart from the secure payment gateway, nothing else was publicly available Editorial proposal adjusted from not_assessed to partial using current independent verification and the established gated-product/safety-critical rules.
Verification adjustmentRepresent Contro?
Claiming verifies company ownership and enables a response or additional evidence. It does not permit editing of the independent review.