Voice is who's speaking: the perspective, expertise, and worldview behind the response. A support lead voice reasons differently than a legal voice, regardless of mood. Tone is how they're speaking in this particular moment: formal or casual, urgent or reassuring, direct or diplomatic. The same voice can shift tone; a support lead can sound calm on a Tuesday and urgent during an outage.
You control both independently. A curated set of each below: pick a name and drop it straight into a prompt ("respond in a [tone] tone" or "respond as a [voice]").
Tone
Direct
"Checkout is broken for all EU customers. Fix needed before 2pm."
Diplomatic
"I know the EU checkout bug is frustrating, let's find the quickest safe fix."
Reassuring
"The refund already went through on our end. It should show in your account within 3 days."
Urgent
"Payments are failing right now for new signups. This needs eyes immediately."
Casual
"Yeah that bug's annoying, I'll have a fix up after lunch."
Formal
"Please find attached the revised terms of service for your review at your earliest convenience."
Encouraging
"Good catch on that edge case, this is exactly the kind of testing that prevents outages."
Candid
"Honestly, we shipped this too fast and skipped the load test. Won't happen again."
Analytical
"Latency breaks down as 60ms database, 20ms auth check, 15ms rendering."
Empathetic
"I know losing your saved cart is frustrating right before a sale, let's get it restored."
Confident
"This caching change will cut page load time by roughly half."
Curious
"What happens to conversion if we move the discount code field above the total instead of below?"
Skeptical
"That fixes today's symptom, but I doubt it addresses why the queue backs up in the first place."
Playful
"Our staging environment has more bugs than a picnic, let's fumigate before the demo."
Neutral
"The A/B test shows a 2% lift in checkout completion for variant B."
Voice
Expert
"Given our traffic pattern, a read-through cache eliminates most of this database load."
Mentor
"I made this exact mistake on my first launch. Here's what I'd do differently now."
Coach
"You're close: tighten the subject line and this email converts a lot better."
Skeptic
"Everyone assumes we need a loyalty program, but do our repeat customers actually want one?"
Diplomat
"Support and engineering both have valid concerns here, let's find a fix that satisfies both."
Strategist
"If we nail onboarding this quarter, retention compounds for every quarter after."
Explorer
"What would happen if we let customers build their own bundle instead of picking from three tiers?"
Auditor
"This flow collects more customer data than the feature actually needs, worth trimming."
Beginner
"I'm still learning our refund system. Could someone walk me through partial refunds?"
Storyteller
"Our support queue used to double every holiday season, until the day we automated the first response."
Realist
"This migration will take six weeks, not two. Let's plan around that instead of hoping."
Advocate
"Self-serve refunds aren't just convenient: they're the difference between a lost customer and a returning one."
Investigator
"Signups spiked at 11pm exactly when the influencer post went live. That's our source."
Translator
"In plain terms, this outage cost us about $4,000 in abandoned carts."
Guide
"First, connect your bank account. Then, verify your business details. Once approved, you can send your first invoice."