Only the safety promises the product can actually support today
This page avoids inflated claims. It describes the trust layers the current ForRico product actually exposes: sitter profiles, booking records, messaging, payments, verification, and support.
Profiles
Sitter visibility
City, services, reviews, and core trust signals are publicly visible.
Bookings
Booking record
Booking, messaging, and follow-up actions stay connected in one flow.
Support
Escalation
If something goes wrong, the platform provides a clear support and reporting path.
Current trust layers
What ForRico actually provides today
These points are tied to existing product surfaces and backend modules, not hypothetical future features.
Verification signals
Sitter profiles expose approval and verification states so owners do not have to trust blindly.
In-platform messaging
Communication before and during care stays in one traceable thread.
Protected payments
Payments stay tied to booking state and follow-up actions rather than fragmenting outside the platform.
Service updates
Active care can remain visible through updates, timeline events, and booking-linked context.
Notifications
Users receive notifications for messages, bookings, and follow-up actions in one connected system.
Reporting and support
If a booking becomes problematic, the platform provides incident and support paths rather than informal escalation.
What this page intentionally does not claim
No inflated safety theatre
The platform should promise only what can be defended by code, data model, and actual support flow.
Trust comes from visible signals, not inflated claims
The right next step is to inspect profile quality, reviews, service fit, and communication inside the actual search flow.