Provider eligibility
A provider should only appear eligible for work when the relevant organisation, role, credentials, service, geography, and operational permissions support it.
Trust & safety
Trust should come from what the system can prove.
CareBow operates in a high-trust category. The website, product, provider network, and operational workflows should tell the same story—without invented scale, fake badges, or unsupported safety promises.
Verification means a workflow
CareBow should not use “verified” as decoration. Verification must map to evidence and approval states in the underlying system.
Private health context
Family health information should stay scoped to the intended person and authenticated users, with data collection and monitoring minimized where possible.
Truthful availability
Services, response times, support levels, certifications, ratings, coverage, and traction should only be claimed when CareBow can prove them.
What families should see clearly
- Who is delivering the service and through which organisation.
- What service is actually available in the requested location.
- What CareBow is charging for software versus the underlying care service.
- What happens if a booking changes, fails, is cancelled, or needs follow-up.
- When AI guidance is insufficient and professional or emergency care is appropriate.
What CareBow should never imply without evidence
- Guaranteed response times or staffed 24/7 support.
- Universal provider availability or same-day coverage.
- Formal compliance certifications that have not been independently completed.
- App-store ratings, download counts, family counts, or provider counts that cannot be documented.
- Clinician review or medical validation that is not tied to documented review evidence.