Account facts, not the account
The rule needed an agreement date and a balance. Send those, not the customer's call history or billing file.
Quebec Law 25
Automate account changes in Quebec and still explain each one
An agent that handles plan changes around the clock keeps customers from waiting on a call center. Law 25 means each customer it turns down can ask why and ask a person to look again. Answer from the record, and the agent keeps working while you do.
Three duties in section 12.1, and the record behind each
Section 12.1 applies to decisions based exclusively on automated processing of personal information. When it applies, the enterprise has three things to do.
Tell the person, at or before the decision
The notice has to reach the person no later than when the decision is communicated. VeriProof keeps the notice version and delivery reference your application reports, next to the decision.
Explain it on request
On request, the person is told what personal information was used, the reasons and principal factors behind the decision, and their right to have the information corrected. The record holds the facts the rule checked and the rule version that applied.
Let them be heard by a staff member
The person can submit observations to a staff member in a position to review the decision. That review goes to a person with authority, and their response and the outcome stay with the case.
A plan change the agent refused
A customer in Laval asks the carrier's support agent to move to a plan with a new phone included. The agent checks the account and refuses: the customer is still inside the minimum term of a device agreement signed eleven months earlier.
The customer asks why, and says they paid the device off last month.
The support lead opens the case and finds the facts the agent submitted, including the agreement start date and a device balance that hadn't updated yet, plus the rule version and the notice reference the application reported. The customer's observation goes to a retention specialist, who approves the change. The application reports the new plan, and the record closes with the full sequence in it.
The fix for the stale balance becomes a request to the developer who owns the integration. That handoff is built in, so the next customer gets the right answer the first time.
Keep the record to what the rule needs
Records your privacy assessment can use
Real decisions give your privacy impact assessment concrete examples of how the agent behaves. Your team weighs them against the wider processing.
VeriProof keeps the facts and reasons your application supplies. It doesn't reconstruct a model's internal reasoning, so the reasons you give customers come from the rule that applied.