For Customer Service Representative (In-House)s ·
What you'll accomplish
By the end of this guide, you'll have a Claude Project set up with your company's voice guidelines, return policy, and FAQ content uploaded as reference documents. Every conversation in this project will produce drafts that sound on-brand and cite correct policy — without you needing to explain company specifics each time.
What you'll need
What you should see: A "Projects" section in the navigation with a "+" or "New Project" option. Troubleshooting: Projects may take a moment to appear after upgrading — try refreshing the page.
Click on "Project Instructions" (or the gear/settings icon inside the project). This is where you tell Claude who it's helping and how to behave.
Copy and adapt this template:
You are helping a Customer Service Representative at a [retail/financial services/software] company.
Your role: Help draft customer-facing emails, CRM case notes, escalation summaries, and internal communications — all in our company's voice.
Our communication style:
- Professional but warm, never robotic
- Lead with empathy before explanation
- Keep emails concise (under 150 words)
- Never promise something uncertain — note when to verify
I will sometimes share customer case details with you. When drafting, use the company documents in this project for policy accuracy. If you're unsure about a specific policy detail, say so rather than guessing.
Inside the project, look for an "Add files" or attachment area (usually a paperclip or "+" in the project sidebar).
Documents to upload (use what you have access to):
How to prepare documents for upload:
What you should see: Uploaded documents appear listed in the project sidebar. Claude can now search them during conversations.
In the project conversation area, type: "What is our return policy for orders over 30 days old?"
Claude should reference your uploaded policy document and give you an accurate answer (or tell you it's not covered if the document doesn't address it).
What you should see: Claude cites or references your policy document in its response. If it hallucinates a policy that isn't in your document, the document may need to be more explicit — add more detail to the policy file.
Type: "A customer emailed asking for a return on a purchase they made 6 weeks ago. Our 30-day policy means we can't accept it. Draft a response email."
What you should see: A denial email that references the correct policy timeline, sounds empathetic, and offers any alternatives that are in your uploaded documents.
Policy check: "What does our policy say about [situation]? I need to respond to a customer."
On-brand draft: "Draft a [type of email] for a customer who [situation]. Keep it in our voice."
Response review: "Review this email I drafted. Does it match our voice and is the policy accurate? [paste email]"
KB gap: "I need to answer a question about [topic] but I'm not sure of the exact policy. Based on our documents, what's the best answer?"
Training material: "Based on our uploaded sample responses, write a new example response for a [case type] scenario."