AI in customer service
M29
Ground answers (RAG), mask data, escalate to a human.
Training by function
A virtual agent speaks on behalf of the company. This path teaches how to ground its answers, mask sensitive data and plan escalation to a human.
Why this path
An ungrounded assistant invents policies, promises refunds or discloses another client's data. The defense: ground answers in a verified knowledge base (RAG), mask sensitive information and guarantee a handoff to a human. This path installs those guardrails.
M29
Ground answers (RAG), mask data, escalate to a human.
The baseline reflexes your whole team shares, whatever the job.
M01
Demystify the probabilistic engine and distinguish it from predictive AI.
A probabilistic engine predicts the most plausible word without understanding meaning: brilliant, but sometimes wrong. Never feed it confidential data in a public tool.
RegisterM02
Identify fabricated information and how to verify it at the source.
A hallucination is fabricated information presented confidently. The risk is real on expert tasks (figures, citations): every output must be verified at the source.
RegisterM03
Structure your prompts (Role + Context + Task + Format) and iterate.
Good results come from a structured prompt and an iterative approach. Providing examples of the desired output markedly improves quality.
RegisterM04
Sort your data and de-identify rigorously before every prompt.
Anything entered into a public AI can be retained and reused. Never client names, salaries or API keys; removing just the name is not enough.
RegisterM05
Recognize shadow AI and have tools approved by IT.
Shadow AI is the use of unapproved tools, often free and poorly protective. The reflex: check the IT allowlist and get the tool approved before using it.
RegisterM06
Apply "human-in-the-loop" and the "four eyes" method.
AI is a gifted junior assistant with no judgment: final responsibility stays human. Review and validate every deliverable as if you had written it yourself.
RegisterThe modules most relevant to the risks specific to your function.
M04
Sort your data and de-identify rigorously before every prompt.
Anything entered into a public AI can be retained and reused. Never client names, salaries or API keys; removing just the name is not enough.
RegisterM18
Know when disclosure is required and how to phrase it.
Inform people they are interacting with an AI and own its use while affirming human validation. For low-level assistance, disclosure remains optional.
RegisterM08
Distinguish reversible masking from legal, irreversible anonymization.
Masking a name is not enough: indirect clues (postal code, role, unique detail) allow re-identification. Legal anonymization is irreversible.
RegisterEnroll your teams in our AI-literacy and governance training paths, from the common core to function-specific use cases.
Immediate access · 100% online · at your own pace