The AI keyboard for Slack replies on iPhone.

I shipped KOPY Work mode because Slack on a phone is where I personally sounded like a different person than I am at a desk. Same intent. Worse sentences. Shorter, punchier, accidentally sharp. A thread that needed a two-line status became a tap-out that read as dismissal. That is not a personality problem. It is a surface problem: you are typing with one thumb while the channel already has five people watching the timestamp.

This page is about async thread tone, status updates you can stand behind later, and not sending the first sentence your fingers produce. It is not a generic “AI for work” essay, and it is not a substitute for Microsoft Teams chat volume, Gmail triage, or the hybrid routing system. Slack has its own failure mode: replies look informal, so people under-write them, then spend the next hour mopping up what the under-write implied.

Grammarly and The Harris Poll (2022) estimated that poor communication costs U.S. businesses about $1.2 trillion a year. Leaders in that research put lost time at about 7.47 hours per week, or roughly $12,506 per employee per year. Slack is not the only channel in that pile, but it is the one that trains you to answer in fragments. Fragments are cheap to send and expensive to interpret.

The 2024 follow-up is worse in a quieter way. Grammarly’s 2024 State of Business Communication found that surveyed knowledge workers spend about 19.08 hours per week writing, and that 100% of them experience miscommunication in a typical week. The same research program estimated generative AI could save up to $1.6 trillion in U.S. communication productivity. I do not treat that as a KOPY revenue claim. I treat it as a ceiling on how much writing work is currently wasted on re-keying the same status in six slightly different tones.

Microsoft’s Work Trend Index 2025 is the Slack-specific weather report: during core hours people are interrupted about every 2 minutes. The top 20% of ping volume see about 275 interruptions per day across 24 hours. Chats outside 9–5 are up 15% year over year, with about 58 messages landing before or after hours. That is why I built generation inside the keyboard instead of another compose tab. You are already in the thread. Leaving Slack to prompt a chatbot is a second interruption you cannot afford.

What “abrupt” actually is in Slack

Abrupt is not “short.” Short is often correct. Abrupt is missing one of four pieces the reader needs to close the loop without pinging you again: owner, date, decision, or next artifact. “Looks good” is abrupt if the thread was asking who ships Friday. “No” is abrupt if the thread was asking whether the API change is in or out of this sprint. The reader then has to guess, and guessing is how you get a huddle you did not want.

On desktop I compensate with extra clauses. On iPhone I drop the clause that carried the date. Work mode’s job is to restore that clause without restoring the essay. I copy the incoming message — usually the last thread line plus one earlier constraint — switch to KOPY, pick Work + Professional or Work + Question, generate, then I edit the one fact the model cannot know: the real date, the real owner, the real blocker. The draft exists so I do not start from a blank field while walking into a store.

Apple’s custom keyboard documentation is why this flow has a setup tax. A third-party keyboard is an app extension. Network calls and clipboard reads need Full Access. I explain the privacy gate in how iOS keyboard extensions work. If Full Access is off, the keyboard cannot see what you copied, and Work mode has nothing to condition on. That is not a bug in Slack. That is iOS doing what it advertised.

Status updates that survive a screenshot

Assume every status you post in a public channel will be screenshotted into a leadership thread you are not in. Write the version that still makes sense when the emoji reactions are stripped. I use a four-part skeleton and let Professional fill the connective tissue:

• State: on track, at risk, or blocked — one of those three, not a vibe.
• Evidence: the smallest fact that would change someone’s plan (PR merged, vendor silent, QA failed on iOS 18).
• Owner: a name, including yours if it is you.
• Next visible artifact: a doc, a diff, a decision by a clock time.

If I only have three of the four, I switch to Question and let the draft ask for the missing piece instead of inventing it. Invented dates are worse than silence. Continue is for when the thread already has the facts and just died of politeness: someone said “sgtm” and nobody posted the recap.

Tone map I actually use in Slack

Work mode exposes several tones. In Slack I almost never open Funny. The four I rotate are Professional, Question, Agree, and Continue. They are not personality skins. They are different jobs.

1. Professional when I owe a record: launch status, incident update, anything a manager might quote. The draft should be copy-pasteable into a standup without rewriting.
2. Question when the incoming message is a demand wearing a question mark, or when I am missing a constraint. “Can we ship Thursday?” is not a yes/no until I know what “ship” means.
3. Agree when the decision is already made and delay is the only remaining risk. Agree still names the next artifact. A bare “yes” creates a second thread asking “yes to what.”
4. Continue when the thread has a buried decision and I need to surface it: “To close this: Maya owns the copy freeze, I own the build, we cut at 4pm PT.”

Disagree exists in the product. I use it in Slack only when I am explicitly rejecting a proposed path and I have a replacement. A mobile Disagree without a replacement reads as combat. If I am not ready to propose, I use Question.

Three Slack shapes that eat evenings

The @channel that is actually a staff meeting. Someone pastes a problem and five people answer with overlapping takes. My reply is not another take. It is a Continue draft that lists owners and a single decision time. If I cannot name owners, I Question who is on the hook instead of adding a sixth opinion.

The DM that should have been a thread. A stakeholder DMs “quick thought.” If I answer in the DM, the rest of the team cannot see the constraint. I still reply — ignoring it is worse — but the Professional draft includes “I’ll recap this in #proj so design has the same constraint.” That sentence is the whole point of generating instead of thumb-typing “ok.”

The emoji-only acknowledgement. A eyes emoji is not a status. If I am the owner, I generate a Professional two-liner that restates state + next artifact. If I am not the owner, I do not generate at all. Work mode is not a fidget toy.

KPI table: Slack thread hygiene

I do not have a fake panel of “users saved N hours.” I do have the metrics I watch on my own team when Slack is the primary async surface. Measure these for a week with a paper tally. The numbers will embarrass you faster than any product demo.

KPI	How I count it	What a bad week looks like	What Work mode is for
Time-to-send	Minutes from the ping that required a human sentence to the first message that contains owner or date	You badge-count until you are at a keyboard, then write a paragraph that still lacks a date	Professional draft in the thread, then you inject the real date
Clarification loops	Follow-ups that exist only because the first reply omitted owner, date, decision, or artifact	Three “wait, who?” messages after a “looks good”	Question tone when a piece is missing; do not hallucinate it
Meeting scheduled	Huddles or calendar holds created because chat could not close a decision	A 15-minute huddle to confirm a status that fit in four lines	Continue recap in-thread so the huddle has nothing to do
Deal follow-up lag	Hours a vendor or partner DM sits because it “isn’t a real email”	Partner waits overnight; you thought a thumbs-up was enough	Treat partner DMs as status records; Professional, then log the artifact

Deal follow-up lag on Slack is not the sales motion on KOPY for sales. It is the partner/vendor thread you treat as chat because the logo lives in Slack. Those people still have a clock. If the commercial follow-up lives in email, switch surfaces — see Outlook on the infinite workday — and do not keep two conflicting statuses.

A copy → generate → edit loop that does not leak secrets

KOPY generates from the text you put on the pasteboard. That is a feature and a footgun. Do not copy a thread that contains customer PII, credentials, or a paste of a legal document you would not put in a third-party processor. Copy the question and the constraint, not the whole incident channel. I designed the keyboard this way because Slack threads are long and models get worse when you dump 40 messages of sarcasm into context.

Practical loop:

1. Long-press the message that contains the ask. Copy. If Slack’s copy grabs too much, paste into Notes, cut to the ask plus one constraint, copy again.
2. Switch to KOPY. Work mode. Professional if you are asserting a status; Question if you cannot assert yet.
3. Read the draft out loud in your head as if your skip-level will see it. Cut any clause you cannot defend. Insert the real name and the real time.
4. Send. If the channel is noisy, reply in thread. Do not drop a status in the main channel unless the original ping was in the main channel.

If you need a longer written record — something that will be forwarded outside Slack — stop. That is email. I wrote a separate walkthrough for work email drafts on iPhone. Using Slack as a stealth email client is how you get decisions that nobody can find in a week.

What I refuse to generate in Slack

• Performance feedback. A mobile Professional draft is the wrong container for “you missed the standard.” Walk or schedule it.
• Headcount or compensation. If it belongs in HRIS or a 1:1, it does not belong in a generated channel reply.
• Incident comedy. Funny tone during an outage is how you get quoted in the postmortem.
• Fake certainty. If QA has not signed off, Question. Do not let Professional launder a guess into a ship date.

Those refusals are why I do not sell Work mode as “never think again.” The thinking is the date and the owner. The keyboard is the sentence that carries them without the accidental coldness of a two-word mobile reply.

Slack vs the rest of the work stack

If your pain is recruiter InMail, you are on the wrong page — use KOPY for LinkedIn. If your pain is a 12-message email that must survive legal and a client, use Gmail or Outlook. If your org lives in Teams and calendar pop-ups, read Teams. If you are trying to pick a default surface for a hybrid team, start at remote work and come back here for the Slack-specific tone rules.

I still use Slack more than I like. The WTI interruption numbers are not abstract when you can feel the 2-minute cadence in your wrist. Work mode does not slow that cadence down. It makes the one sentence you send inside that cadence contain the four pieces that prevent the next three messages. That is the only Slack outcome I was willing to ship a paid mode for.