Even Apple Uses AI for Customer Service

Last Wednesday at 10 PM, I was still replying to customer messages one by one on WeChat, my fingers numb from typing.

Those of us running small businesses know — customer questions are the same ones over and over, but every time I have to type it all out again. Then I saw this news: inside Apple's Apple Support app, developers found files called "Claude.md".

What Apple Leaked + Who's Using It

Last week, developer Aaron Perratore was at home unpacking Apple's Apple Support app (the one for checking warranties and booking repairs) and found leftover "Claude.md" files. .md is Markdown — think of it as "a notepad with formatting." These files contained Apple's "work manual" for Claude: who you are, how to answer, what you can and can't say.

Put simply, Apple is using AI for front-line customer service, and even they need to write manuals to manage AI. I've made this mistake before: just throwing AI on there and letting it answer on its own, and the customer got a generic "As an AI language model, I cannot..." response. Embarrassing.

Apple's approach reminds us: the key to using AI for customer service is writing a solid instruction file — telling it who you are, what your business rules are, what the tone should be. This isn't deep tech — it's just writing the rules clearly in text.

Your Replication Cost Today

  • Money: Claude ~$20/month (Pro), free tier works too — a dozen chats a day is enough for daily use
  • Time: 1–2 hours to write a "work manual," then ~10 min/week to maintain
  • Technical barrier: If you can use a chat app, you're good — no code needed
  • First step: Open claude.ai, start a new conversation, write "You are my customer service assistant, my business does XX, answer in a friendly tone, don't mention you're AI"

Advice by Stage

If you're just starting, no customers asking yet: Don't rush to set this up — get your product working first. Come back to write the manual after you've been asked the same question three times in a day.

If you have 1–2 customers, occasional questions: I'd suggest manually putting together an FAQ doc first, then paste it into Claude and let it draft replies. No need for automation — manual copy-paste is fine.

If you're scaling, 10+ customer messages a day: Put your "work manual" into Claude's Projects feature, so every new conversation remembers your rules. If you have the technical chops, consider connecting the API for auto-replies — but that's a next step, don't overcomplicate things all at once.