Procurement Readiness
Meridian is designed to survive buyer questions and support the technical diligence of high-value service firms.
Buyer Readiness
Before any deployment, Meridian provides an Architecture Blueprint and Procurement Packet. We expect firms to review these with their internal IT, compliance, or partner leadership.
Client Approvals
Meridian does not "set and forget." Every script, escalation contact, and routing rule requires explicit client sign-off before go-live. We provide a Launch Checklist for final acceptance.
Subprocessor Disclosure
Our core stack utilizes established cloud providers with SOC 2 Type II or equivalent posture, including Supabase (Data), Twilio (Communications), and Cloudflare (Infrastructure).
Data Boundaries
We work with clients to define "do-not-collect" fields. By default, clinical data, case strategy, and sensitive PII are filtered at the responder layer.
Acceptance Criteria
- Successful Architecture Blueprint review
- Script and boundary language approval
- Verified routing to CRM/Staff Inbox
- Rollback and escalation owner confirmation
- Transcript QA review schedule set