Communication - Thread Docs

Write to the client: first replies, expectation-setting, chasers, closing notes, and the awkward messages nobody enjoys drafting.

Apology With Remedy

Draft the message when the desk genuinely failed — specific acknowledgment, concrete remedy, and one prevention step, without groveling or overreach.

Approval Request Email

Draft an email to an approver requesting authorization for a password reset, install, purchase, or access change — what/why/risk/expiry in one read.

Bad Review Response Prep

After a poor CSAT score or negative review, prepare internal talking points plus an external response draft — facts only, zero defensiveness.

Client RCA Summary

Draft a client-safe root-cause summary for a resolved issue — what happened, impact, cause, and prevention — written defensively for one ticket.

Client Reply

Draft an external client reply in your house voice and format — resolution updates, status notes, closing messages, or any client-facing email on a ticket.

De-escalation Reply

Draft the response to an angry client message — acknowledge, own what's ours, commit to a concrete next step with a time, without matching their tone.

Delay Apology

Draft an honest acknowledgment that a ticket has taken too long or a commitment slipped — apology without excuses, new commitment only if confirmed.

Difficult News Delivery

Draft the message no one wants to send — data loss, unrecoverable state, security exposure — factual, empathetic, and pointed at the path forward.

Email Baseline Standard

The base client-email standard other communication skills build on — structure, tone rules, and placeholder discipline for every outbound message.

EOL Product Notice

Draft the client notice that a product or OS is reaching end-of-life — verified EOL date, honest risk framing, upgrade paths, decision deadline.

ESL Drafting Assistant

Grammar and idiom cleanup for technicians writing in non-native English — "fix my English" or "mejorar ingles," technical content untouched.

Expectation-Setting Acknowledgment

Draft the first-touch acknowledgment on a new ticket — what we understood, how seriously we're treating it, next steps, and when the client hears back.

Follow-up Chaser

Draft a polite, escalating follow-up when a client hasn't replied on a ticket — first nudge, second nudge, or final pre-closure attempt with tone.

Maintenance Window Notice

Draft a planned-work client notice — what's happening, when, expected impact, duration, and rollback promise — for patching, upgrades, or migrations.

Multilingual Reply

Draft the client reply in the client's own language — detect it from their messages, write natively, and provide an English back-translation to verify.

Outage Notification

Draft a major-incident or mass-outage client notice — known impact, what we're doing, when the next update comes — without speculating on cause.

Price Increase Letter

Draft the client notice for an agreement price change — value-first framing, effective date, honest rationale — gated behind account-manager approval.

Resolution Closing Email

Draft the closure email for a resolved ticket — what was wrong, what we did, how to reopen — built from the ticket's actual evidence, not memory.

Scope Pushback

Draft the reply when a client requests something outside their agreement — a helpful no showing the path to yes (quote or agreement change) with AM loop.

Screenshot OCR Translate

Extract the text from a pasted screenshot — an error dialog, email, or app screen — translate it to English if needed, and summarize what it actually says.

Security Advisory Broadcast

Draft a security advisory going to many clients — new threat, vendor breach, or vulnerability — from verified facts with per-client relevance check.

Status Update Messenger

One command sets the ticket status and posts the matching templated client message from a per-status map, so status and note change together.

Technical to Plain English

Translate a technical resolution, diagnosis, or explanation into language a non-technical stakeholder can understand — "make this client-friendly."

Three Strikes Final Email

Draft the final "we're closing this ticket" email after three documented contact attempts with no client response — only when evidence exists.

Tone Polish Rewrite

Rewrite rough technician text into a polished, client-ready version — "write this nicely," "clean this up" — preserving every fact exactly.