1. Availability scope
Availability commitments apply only where an executed contract or order expressly provides a service-level agreement. The current prototype has no production uptime guarantee; target percentages must be backed by monitoring and operational capacity.
2. Scheduled maintenance
Ravensford should publish planned maintenance and use commercially reasonable efforts to minimise customer disruption, particularly for reception and messaging functions.
3. Incidents and support
Support channels and response objectives should vary transparently by plan. High-impact incidents such as security breaches, major outages and failed message delivery require triage, status updates and incident records.
4. Third-party dependencies
Telephony carriers, AI model providers, internet access, external calendars and CRMs can be outside Ravensford’s control. The service should use durable queues, retries, deduplication and reconciliation where feasible and distinguish upstream outages from platform incidents.
5. Credits and remedies
Any service-credit formula, claim period, exclusions and maximum remedy should be explicitly defined in the signed SLA and must not override mandatory legal rights.
6. Business continuity
Critical workflows should include fallbacks, human escalation and documented recovery processes. Customers should validate backup contact numbers and contingency arrangements before relying on AI Receptionist for essential calls.
Questions about this policy?
Use the Ravensford contact page to submit an enquiry. Production legal, privacy and security contact addresses must be confirmed before launch.
