Writing Styles
Pro Feature
TalkTone requires TalkWriter Pro or Enterprise. Upgrade to Pro →
Every TalkTone mode comes with a curated set of writing styles. A style defines the specific voice, structure, and personality of your transformed text. This page is the definitive reference for every style available in TalkWriter.
How Styles Work
- You pick a mode (Email, Chat, Creative, Document, Social, or Code)
- Each mode offers a set of styles to choose from
- The style determines the voice and structure of the output
- You can further adjust with formatting (Casual/Neutral/Formal) and intensity (Light/Medium/Full)
tip
Not sure which style to use? Start with the first style in each mode -- it is the default and works well for most situations.
💬 Chat Styles (6 styles)
For casual messaging, texts, DMs, Slack, and quick conversations.
| Style | Description | Example Output |
|---|---|---|
| Friendly | Warm, approachable, conversational. Like texting a good friend. | "Hey! Hope you're doing well. Just wanted to check in and see how things are going." |
| Professional | Polished but relaxed. Suitable for work chat without sounding stiff. | "Hi Sarah, quick update -- the project is on track for Friday delivery." |
| Witty | Clever, humorous, playful. Adds personality and charm to your messages. | "Plot twist: I actually finished the report early. I know, I'm shocked too." |
| Romantic | Warm, affectionate, heartfelt. For personal messages to loved ones. | "Thinking about you today. You make everything feel a little brighter." |
| Cold Outreach | Direct, value-driven introductions. For reaching out to people you don't know. | "Hi Alex, I noticed your work on the analytics platform -- would love to chat about a collaboration." |
| Support Reply | Helpful, empathetic, solution-focused. For customer service or helping someone. | "I totally understand the frustration. Here's what we can do to fix this right away." |
When to Use Each Chat Style
| Situation | Recommended Style |
|---|---|
| Messaging a friend | Friendly |
| Slack message to a coworker | Professional |
| Funny reply in a group chat | Witty |
| Text to your partner | Romantic |
| LinkedIn DM to a stranger | Cold Outreach |
| Replying to a customer question | Support Reply |
✉️ Email Styles (6 styles)
For professional and personal email correspondence.
| Style | Description | Example Output |
|---|---|---|
| Formal Business | Traditional corporate tone. Proper greetings, structured paragraphs, professional sign-off. | "Dear Mr. Johnson, I am writing to follow up on our previous discussion regarding the Q3 budget allocation..." |
| Friendly Professional | Warm yet competent. The sweet spot between corporate and casual. | "Hi David, thanks for the quick reply! I've attached the updated proposal -- let me know if anything needs tweaking." |
| Brief & Direct | No fluff, no filler. Gets straight to the point in as few words as possible. | "Hi -- the report is attached. Key finding: revenue up 15%. Let me know if you have questions." |
| Detailed Explanatory | Thorough and comprehensive. Explains context, reasoning, and next steps. | "Hi Team, I wanted to provide a detailed update on the migration project. Here's where we stand, what's changed, and what we need to decide next..." |
| Follow-Up | Polite nudge for unanswered emails. References previous context without being pushy. | "Hi Sarah, I wanted to circle back on the proposal I sent last Tuesday. I understand you've been busy -- just wanted to make sure it didn't slip through the cracks." |
| Apology | Sincere, accountable, solution-oriented. Takes responsibility and offers resolution. | "I sincerely apologize for the delay in delivering the final report. I take full responsibility for the oversight and have taken steps to ensure this doesn't happen again." |
When to Use Each Email Style
| Situation | Recommended Style |
|---|---|
| Email to CEO or board | Formal Business |
| Email to a team member | Friendly Professional |
| Quick status update | Brief & Direct |
| Project update with context | Detailed Explanatory |
| No response after 3 days | Follow-Up |
| You made a mistake | Apology |
✍️ Creative Styles (6 styles)
For blogs, stories, personal essays, poetry, journals, and creative projects.
| Style | Description | Example Output |
|---|---|---|
| Storyteller | Narrative voice with pacing, scene-setting, and character. Reads like a novel. | "The morning began like any other -- coffee brewing, emails piling up. But then the phone rang, and everything changed." |
| Poetic | Lyrical, evocative language. Rich imagery and emotional depth. | "The evening sky unraveled in ribbons of amber and rose, each hue bleeding softly into the next." |
| Humorous | Funny, self-aware, entertaining. Makes the reader smile or laugh. | "I tried to be productive today. Spoiler: I ended up reorganizing my sock drawer and calling it 'life optimization.'" |
| Inspirational | Uplifting, motivational, empowering. Makes the reader feel they can do anything. | "Every great achievement started with someone who refused to accept 'impossible' as an answer. Today, that someone is you." |
| Descriptive | Vivid, sensory-rich writing. Paints a picture with words. | "The old bookshop smelled of aged paper and cedar, its shelves sagging under the weight of a thousand forgotten stories." |
| Minimalist | Sparse, deliberate, powerful. Every word earns its place. | "Rain. A quiet street. Two cups of coffee getting cold." |
When to Use Each Creative Style
| Situation | Recommended Style |
|---|---|
| Blog post or article | Storyteller |
| Personal reflection or journal | Poetic |
| Casual blog or newsletter | Humorous |
| Motivational content | Inspirational |
| Travel writing or reviews | Descriptive |
| Twitter thread or micro-fiction | Minimalist |
📄 Document Styles (5 styles)
For reports, articles, meeting notes, academic writing, and formal documentation.
| Style | Description | Example Output |
|---|---|---|
| Analytical | Data-driven, logical, evidence-based. Breaks down complex topics with clear reasoning. | "This quarter's 15% revenue growth can be attributed to two primary factors: (1) enterprise client acquisition and (2) reduced churn." |
| Executive Summary | Concise, high-level, decision-focused. Gives leaders exactly what they need in minimal words. | "Q4 revenue: +15% QoQ. Key drivers: 3 new enterprise clients, churn down 22%. Recommendation: increase sales headcount by 2." |
| Technical | Precise, detailed, specification-grade. For technical audiences who need accuracy. | "The API endpoint accepts a JSON payload with a required userId field (string, UUID v4) and returns a 200 response with the user profile object." |
| Instructional | Step-by-step, clear, actionable. Guides the reader through a process. | "Step 1: Open the Settings panel. Step 2: Navigate to Integrations. Step 3: Click 'Add New' and select the Slack connector." |
| Narrative | Story-driven but professional. Adds context and flow to dry topics. | "When we first noticed the drop in conversion rates, the team was puzzled. A deeper analysis revealed an unexpected pattern..." |
When to Use Each Document Style
| Situation | Recommended Style |
|---|---|
| Quarterly business review | Analytical |
| Board presentation | Executive Summary |
| API documentation | Technical |
| User guide or SOP | Instructional |
| Case study or white paper | Narrative |
📱 Social Styles (5 styles)
For Twitter/X, LinkedIn, Instagram, YouTube, Reddit, and other social platforms.
| Style | Description | Example Output |
|---|---|---|
| Announcement | Punchy, exciting, news-worthy. Built for launches, releases, and big updates. | "We just shipped multilingual dictation -- 30+ languages, real-time. Try it today." |
| Thought Leadership | Insightful, authoritative, discussion-starting. Positions you as an expert. | "The future of voice-to-text isn't monolingual. Global teams deserve tools that speak their language." |
| Engagement Bait | Question-driven, opinion-seeking, community-building. Designed to drive comments. | "Hot take: voice dictation will replace typing for 80% of knowledge workers within 5 years. Agree or disagree?" |
| Behind-the-Scenes | Authentic, personal, transparent. Shows the real story behind the product or brand. | "Here's what nobody tells you about building a startup: the 'overnight success' took 847 days of debugging." |
| Educational | Informative, value-packed, shareable. Teaches the audience something useful. | "Most people waste 2 hours/day typing emails. Here's how voice dictation can cut that to 30 minutes (thread)." |
When to Use Each Social Style
| Situation | Recommended Style |
|---|---|
| Product launch | Announcement |
| Industry opinion piece | Thought Leadership |
| Increasing engagement | Engagement Bait |
| Building brand authenticity | Behind-the-Scenes |
| How-to or tutorial content | Educational |
💻 Code Styles (5 styles)
For developer documentation, code comments, commit messages, and pull requests.
| Style | Description | Example Output |
|---|---|---|
| Code Comment | Concise inline comments following standard conventions. Clear and scannable. | // Retrieves user profile by ID. Throws UserNotFoundError if no match. |
| API Docs | JSDoc/Javadoc style documentation with params, returns, and throws. | /** @param {string} userId - Unique user identifier @returns {UserProfile} */ |
| README | Project documentation style. Clear sections, setup instructions, feature lists. | "## Installation\n\nRun npm install talkwriter-sdk to add the package to your project." |
| Commit Message | Conventional commit format. Type, scope, and concise description. | feat(auth): add OAuth2 PKCE flow for mobile clients |
| PR Description | Structured pull request template. Summary, changes, testing, and notes. | "## Summary\nAdds rate limiting to the /api/transcribe endpoint.\n\n## Changes\n- Added Redis-based rate limiter..." |
When to Use Each Code Style
| Situation | Recommended Style |
|---|---|
| Explaining code logic | Code Comment |
| Documenting functions/methods | API Docs |
| Writing project documentation | README |
| Committing code changes | Commit Message |
| Opening a pull request | PR Description |
Complete Style Reference Table
Here is every style in one place for quick lookup:
| Mode | Style | One-Line Summary |
|---|---|---|
| 💬 Chat | Friendly | Warm, conversational, like texting a friend |
| 💬 Chat | Professional | Polished work chat without being stiff |
| 💬 Chat | Witty | Clever, humorous, personality-driven |
| 💬 Chat | Romantic | Affectionate, heartfelt messages |
| 💬 Chat | Cold Outreach | Direct value-driven introductions |
| 💬 Chat | Support Reply | Empathetic, solution-focused help |
| ✉️ Email | Formal Business | Traditional corporate correspondence |
| ✉️ Email | Friendly Professional | Warm yet competent work emails |
| ✉️ Email | Brief & Direct | Minimal, straight to the point |
| ✉️ Email | Detailed Explanatory | Thorough context and reasoning |
| ✉️ Email | Follow-Up | Polite nudge for unanswered emails |
| ✉️ Email | Apology | Sincere, accountable, solution-oriented |
| ✍️ Creative | Storyteller | Narrative voice with pacing and scene |
| ✍️ Creative | Poetic | Lyrical, evocative, emotionally rich |
| ✍️ Creative | Humorous | Funny, self-aware, entertaining |
| ✍️ Creative | Inspirational | Uplifting, motivational, empowering |
| ✍️ Creative | Descriptive | Vivid, sensory-rich, paints pictures |
| ✍️ Creative | Minimalist | Sparse, deliberate, every word counts |
| 📄 Document | Analytical | Data-driven, logical, evidence-based |
| 📄 Document | Executive Summary | Concise, high-level, decision-focused |
| 📄 Document | Technical | Precise, specification-grade detail |
| 📄 Document | Instructional | Step-by-step, clear, actionable |
| 📄 Document | Narrative | Story-driven professional prose |
| 📱 Social | Announcement | Punchy, news-worthy launches |
| 📱 Social | Thought Leadership | Authoritative, discussion-starting |
| 📱 Social | Engagement Bait | Question-driven, comment-generating |
| 📱 Social | Behind-the-Scenes | Authentic, personal, transparent |
| 📱 Social | Educational | Informative, value-packed, shareable |
| 💻 Code | Code Comment | Concise inline code comments |
| 💻 Code | API Docs | JSDoc/Javadoc style documentation |
| 💻 Code | README | Project documentation and setup |
| 💻 Code | Commit Message | Conventional commit format |
| 💻 Code | PR Description | Structured pull request template |
Combining Styles with Other Settings
Styles work together with other TalkTone settings to give you fine-grained control:
| Setting | What It Adds |
|---|---|
| Style (this page) | The voice and personality |
| Formatting | Formality level (Casual, Neutral, Formal) |
| Intensity | How much your words change (Light, Medium, Full) |
| Custom Instructions | Your personal rules and preferences |
Power User Combo
Try pairing Email mode + Brief & Direct style + Formal formatting + Light intensity for emails that stay close to your original words but sound polished and professional.
Next Steps
- Formatting Options -- Adjust formality level
- Intensity Slider -- Control how much TalkTone rewrites
- Custom Instructions -- Add your own rules