Communication - Thread

25 skills in this category.

Apology With Remedy

Draft the message for when the desk genuinely failed — specific acknowledgment of what went wrong, a concrete remedy, and one prevention step — without groveling and without admissions beyond the established facts.

Approval Request Email

Draft an email to an approver requesting authorization — password reset, software install, purchase, access change — with what/why/risk/expiry stated so they can decide 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 from the ticket record only, zero defensiveness.

Client RCA Summary

Draft a client-safe root-cause summary for a resolved issue — what happened, impact, cause, and what prevents recurrence — written defensively. Use for a single-ticket RCA the client asks for, short of a full major-incident letter.

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 or frustrated client message — acknowledge, own what's ours, commit to a concrete next step with a time — without ever matching their tone.

Delay Apology

Draft an honest acknowledgment that a ticket has taken too long or a commitment slipped — apology without excuses, and a new commitment only if the technician confirms one.

Difficult News Delivery

Draft the message no one wants to send — data loss, an unrecoverable state, a security exposure — factual, empathetic, and pointed at the path forward, under strict defensive-writing rules.

Email Baseline Standard

The base client-email standard other communication skills build on — structure, tone rules, and placeholder discipline for every outbound message. Load when drafting any client email, or when another skill references it.

EOL Product Notice

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

ESL Drafting Assistant

Grammar and idiom cleanup for technicians writing in non-native English — "fix my English," "mejorar ingles," or any draft that needs natural-sounding English with the technical content untouched.

Expectation-Setting Acknowledgment

Draft the first-touch acknowledgment on a new ticket — what we understood, how seriously we're treating it, what happens next, and when the client will hear from us.

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, tone matched to the attempt number.

Maintenance Window Notice

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

Multilingual Reply

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

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, a clear effective date, and an honest one-line rationale — gated behind account-manager approval before anything leaves the desk.

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 asks for something outside their agreement — a helpful no that shows the path to yes (quote or agreement change) and loops in the account manager.

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 at once — new threat, vendor breach, critical vulnerability — built from verified facts only, with a per-client relevance check so no one gets an advisory about a product they don't run.

Status Update Messenger

One command sets the ticket status and posts the matching templated client message from a per-status map — so a status change and the client-facing note that should go with it happen together. Runs manually on demand.

Technical to Plain English

Translate a technical resolution, diagnosis, or explanation into language a non-technical stakeholder can understand — "explain this to the office manager," "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 the evidence of prior attempts actually exists.

Tone Polish Rewrite

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