The Signal · Lesson 6 of 6
Governance and evidence
Once a system can act on your behalf, the question stops being how smart it is and becomes what it is allowed to do.
Governance6 min read
Draw the permission line on purpose
Write down what the system may do without a human, what it may propose but not commit, and what it may never touch. Booking a standard maintenance hour and issuing a refund are not the same class of action.
If nobody has written that list, the boundary is whatever the vendor shipped by default.
Disclosure and recording
Rules on disclosure and call recording vary by state, and consent requirements differ between one party and all party states. Decide your policy with your own counsel, apply it consistently on every line, and keep the wording the same across languages.
A Spanish caller is entitled to the same disclosure as an English caller, in Spanish.
Evidence is the whole point
For every action the system takes, you want a record showing when it happened, what triggered it, what changed, and what the caller was told. Not a transcript. A record.
That trail is what lets you resolve a dispute, correct a bad instruction, and change the rules with confidence. Without it you are trusting a black box with your customer relationships, and there is no version of that which ends well.
What to take away
- Write the permission list yourself, or inherit the vendor default.
- Disclosure and recording rules vary by state and must be applied in both languages.
- Every automated action needs an auditable record, not just a transcript.