cx-ai-disclosurelisted

Use to design and audit how customers are told they are interacting with AI, or that AI was involved in a decision about them, and to evidence that it happened. Trigger for "do we tell customers it's a bot", "AI disclosure requirements", "should the bot say it's not human", "customer asked if they were talking to a person", AI transparency obligations, or evidencing that an AI-assisted decision was explained.
rulebase-co/rulebase-skills · ★ 1 · AI & Automation · score 72

Install: claude install-skill rulebase-co/rulebase-skills

# Telling customers about AI Three distinct obligations get collapsed into one conversation, and they have different triggers, different audiences and different evidence: 1. **You are talking to a machine.** Transparency about the interaction itself. 2. **AI was involved in a decision about you.** Transparency about a process, which may carry a right to an explanation or to human review. 3. **Your conversation was processed by AI.** A data-processing question — QA scoring, sentiment analysis, summarisation — that the customer may never see any output from. The third is the one most often missed, because nothing about it is visible to the customer. A support operation running AI QA over every conversation is processing personal data with AI, whether or not a bot ever replied. **What is legally required varies by jurisdiction, sector and use, and it is changing. Nothing here states an obligation.** This gives you the design and the evidence; the determination is legal's. ## Design the interaction disclosure **Up front, not on request.** A bot that identifies itself only when asked has left every customer who did not think to ask uninformed. Disclose at the start of the interaction. **In the conversation, not only in a policy.** A line in the privacy notice is not a disclosure to someone in a chat window. **Answer the direct question honestly, always.** "Am I talking to a human?" must get a straight answer. A bot deflecting that question is the single worst failure