Looking after customer details in software support chats
This checklist helps software publishers protect licence keys, account emails, logs and screenshots in customer chats. It sets simple rules for what an AI agent may ask for, repeat or keep.
Runs in your browser. Nothing you enter is sent anywhere or saved.
Before you start
Software support chats are full of things people should not share freely: licence keys, account emails, error logs with file paths and screenshots showing names or documents. A careless habit in chat can leak a customer's licence or reveal their private files to someone else.
Use this list to set simple rules for your team and your agent. Tick each item, and note any you cannot yet meet. None of this is legal advice. For privacy law questions in your region, ask a qualified person who knows your product.
Tick each one as you go. 0 of 10 done.
[ ] Ask for the account email, and look up the licence yourself. [ ] Never repeat a full licence key back in the chat. [ ] Check who is writing before sharing account details. [ ] Ask people to hide private details in screenshots. [ ] Do not ask for passwords, under any circumstances. [ ] Request logs only when needed, and say what they contain. [ ] Send privacy requests straight to a named person. [ ] Keep customer chats out of public places and shared screens. [ ] Decide how long you keep chats and logs, then write it down. [ ] Review who on your team can open customer chats.
What the agent should and should not do
The agent can confirm which edition an email holds, tell a customer how many seats are used and explain how to move a licence. It should not read out a full key, share another person's details or change who owns a licence without a person checking.
If a customer pastes something sensitive by accident, such as a password or a full key, the agent should say so kindly, suggest changing it and pass the chat to a person.
Habits that keep trust
Small rules, repeated every day, protect customers better than a long policy.
- Say what you will do with any file the customer sends.
- Delete test accounts and test chats you no longer need.
- Remind new staff of the rules in their first week.
- Tell customers promptly if you find a mistake on your side.
FAQ
Can customers send licence keys in chat?
It is better to avoid it. Ask for the account email instead, because your system can find the licence from that. If a key is pasted, suggest the customer keep it private in future.
What should the agent do if someone asks to delete their data?
Confirm that you received the request, collect the account email and hand the chat to the person who handles privacy. The agent should not promise deletion or timing on its own.
Are screenshots safe to ask for?
They can be, if you ask people to hide private details first. Tell them exactly what you need to see, such as the error box, so they crop the rest out.
More free tools for software publishers and app makers
- First-reply checklist for software publishers and app makers
- Hand-over rules checklist for software publishers and app makers
- First-week checklist for software publishers and app makers
- Weekly chat review checklist for software publishers and app makers
- Busy-season checklist for software publishers and app makers
- Do and don't guide for your agent: software publishers and app makers
- Greeting messages for software publishers and app makers
- After-hours replies for software publishers and app makers
- Booking and order confirmations for software publishers and app makers
- Reminder messages for software publishers and app makers
- Apology and complaint replies for software publishers and app makers
- "Let me check" replies for software publishers and app makers
- Follow-up messages for software publishers and app makers
- Review request messages for software publishers and app makers
- Price and quote replies for software publishers and app makers
- Delay and stock notices for software publishers and app makers
- Thank-you messages for software publishers and app makers
- Hand-over notes for software publishers and app makers
- Ready answers for software publishers and app makers
- Holiday and closure notices for software publishers and app makers
- Missed enquiries calculator for software publishers and app makers
- AI agent instructions builder for software publishers and app makers
- Auto-reply message writer for software publishers and app makers
- FAQ answer sheet for software publishers and app makers
- Reply speed scorecard for software publishers and app makers
- Is your business ready for an AI agent? Quiz for software publishers and app makers
- Message workload planner for software publishers and app makers
- Hours saved calculator for software publishers and app makers
- Enquiry-to-customer value estimator for software publishers and app makers
Read the guide: Answer software customer messages before they become tickets.