Tenant boundary
A dedicated customer workspace is provisioned only after an agreed SOW.
Defined in SOW Security & governance
Control the handoff before automating the outcome.
RelayCX starts with the authority model: which systems an Agent may use, which actions it may take, when it must pause, and what evidence must remain.
04
SignalAgentHuman approvalAction
Production boundary
Clear claim boundary
This page describes RelayCX’s proposed delivery and control model. It does not claim that RelayCX currently holds any particular third-party certification.
Six control surfaces
Make authority visible at every stage.
Specific obligations become contractual only after diligence and written agreement.
Least privilege
Connections and actions are limited to what the selected workflow requires.
Defined in SOWApproval ownership
Risk thresholds route sensitive decisions to named customer owners.
Defined in SOWDecision trace
Context, proposed action, approval, execution, and outcome stay reviewable.
Defined in SOWAdmin-led access
Customer administrators invite approved employees; no public signup exists.
Defined in SOWContract-defined obligations
Retention, residency, deletion, audit, and compliance requirements are confirmed in diligence.
Defined in SOWDiligence agenda
Questions to resolve before the pilot.
01
Which records can the Agent read?
02
Which fields or systems can it change?
03
Which actions are reversible?
04
What confidence requires review?
05
Who owns each approval threshold?
06
What evidence must be retained?
07
What location and retention rules apply?
08
How will exceptions and incidents be handled?
The next relay
Put security into the first discovery call.
Bring your access, privacy, residency, approval, and audit requirements so they can shape the workflow from the beginning.
Book a diagnostic