The AI keyboard for async remote work.

Hybrid work is not a location. It is a routing problem. The same human now keeps status in Slack, cross-org work in Teams, commitments in Gmail or Outlook, and a career inbox on LinkedIn. I shipped one Work mode because the spine of a good sentence is shared — owner, date, ask — and I shipped separate /for pages because the skin is not shared. This is the pillar. The children are Slack thread tone, Teams meetings and volume, Gmail triage vs reply, Outlook stakeholder mail, plus LinkedIn professionalism and sales SLAs when those inboxes are part of the job rather than the culture.

If you skip routing and only install a keyboard, you will generate fluent duplicates. Fluent duplicates are how hybrid teams lose the 7.47 hours. Grammarly / Harris 2022 estimated poor communication at about $1.2 trillion a year in the U.S., about 7.47 hours per week leaders say they lose, about $12,506 per employee per year. Hybrid did not create that bill. Hybrid made the bill harder to see because the same decision can exist in three tools with three timestamps.

Grammarly 2024 is the writing-load layer: about 19.08 hours per week writing, 100% of surveyed knowledge workers reporting weekly miscommunication. Generative AI’s up-to-$1.6 trillion communication productivity estimate is the “if we wrote less badly” ceiling. A keyboard does not automatically collect that. A keyboard plus a routing rule might collect a slice. The slice I care about is the mobile reply that used to wait for a laptop and then arrived too late to prevent a meeting.

Microsoft measured the weather. WTI 2025: interruptions about every 2 minutes in core hours, about 275 interruptions per day for the top 20% of ping volume over 24 hours, after-hours chats up 15%, about 58 messages outside 9–5. The infinite workday report: about 117 emails and 153 Teams messages daily, 40% checking email before 6 a.m., after-8 p.m. meetings up 16%, 85% of emails read in under 15 seconds. Those figures are why “we’ll just be more disciplined” fails. The system has to assume interruption and still close loops.

Routing table I actually use

Write this on a wiki if you have one. If you do not, write it in the channel everyone already ignores, then pin it. The keyboard cannot store your org chart.

Job	Default surface	KOPY page	Tone I reach for first
Now-work, status, incident-lite	Slack thread (or Teams channel if Slack is not the tenant)	/for/slack or /for/teams	Professional or Continue
Cross-company in a Microsoft tenant, ad-hoc huddle risk	Teams channel, not a new meeting	/for/teams	Question, then Continue recap
Forwardable commitment, client, legal-adjacent	Email	/for/gmail or /for/outlook	Professional news-first
Hiring, intros, InMail	LinkedIn	/for/linkedin	Professional or Question
Quota-timed follow-up	Email or LinkedIn per the account	/for/sales	Continue with a next step, not HR warmth

The rule that saves more time than any tone: one decision, one surface. If you decide in Slack, do not “confirm in Outlook” unless someone outside the channel needs the forward. If you decide in Outlook, post a one-line pointer in Slack, not a second decision. Dual-writing is how the 100% weekly miscommunication statistic gets its raw material.

Time zones, EOD, and the 58 after-hours messages

Hybrid teams abuse “EOD.” EOD in one zone is after-hours in another, which is how you get the 58 messages and the 16% evening-meeting bump. Work mode will happily say “end of day” if your copied text did. I delete that phrase on sight and put a clock time with a timezone. That is not a model skill. That is a human skill the draft makes easier because I am not also hunting for a professional synonym for “blocked.”

If you are about to send after 8 p.m., ask whether the message prevents a meeting tomorrow or merely proves you were online. Only the first is worth another interruption in someone else’s 275. I schedule-send email when the news is not a fire. Chat is harder to schedule; then I write the Continue recap and wait. Work mode drafts are valid in the morning. They are not more valid at 10:12 p.m.

One keyboard, four skins

Technically KOPY is one iOS keyboard extension. Apple’s custom keyboard model means Full Access if you want clipboard context and a network call. I explained the constraints in how iOS keyboard extensions work. The product mistake would have been four apps. The communication mistake is one voice. Slack-abrupt in Outlook is how clients think you are angry. Outlook-formal in Slack is how teammates think you are about to put them on a PIP. LinkedIn-warmth in a sales follow-up is how deals stall in “love to reconnect.” Sales-urgency in a recruiter decline is how you get a reputation.

Work mode tones I reuse across the system, with different jobs:

• Professional: the record. Slack status, Teams leadership channel, email sentence one, LinkedIn inbound when you are at least curious.
• Question: the missing constraint. Use it before you book the huddle Teams is offering you.
• Agree: the unblock, with a time. Never as a personality.
• Continue: the recap that prevents the 16% meeting and the clarification loop.

Email mechanics — copy, generate, edit on a phone — are in the work-email iPhone post. Recruiter-specific copy-paste lives in recruiter LinkedIn examples. Do not flatten those into this pillar. This page is the switchboard.

KPI table: system health, not app vanity

Measure across tools or you will “win” Slack while losing email. A week of honest tallies beats a dashboard I will not fake.

KPI	System definition	Hybrid failure	What to change
Time-to-send	Minutes from a decision-shaped ping (any tool) to a message on the correct surface that contains owner or date	You answer fast in Slack and late in Outlook, so the client sees only the late one	Route first, then generate; do not optimize the wrong inbox
Clarification loops	Follow-ups whose cause is two surfaces with two wordings of the same decision	Slack said Friday; email said “soon”; Teams booked a huddle	One decision, one surface; pointer elsewhere
Meeting scheduled	Ad-hoc holds whose agenda could have been a Continue recap	After-8pm tiles born from unrouted chats	Question the gap in chat; Continue; meet only for voice votes and screens
Deal follow-up lag	Hours a money or hiring thread sits because it was treated as “not the team Slack”	Culture inbox is fast; commercial/hiring inbox is a graveyard	Give those threads a SLA; use sales or LinkedIn playbooks

I care about clarification loops more than raw speed. Speed on the wrong surface is how you get the $1.2T number to show up as a small team’s week. The 19.08 writing hours are not inherently bad. They are bad when they are spent reconciling three copies of Friday.

Operating cadence for a distributed week

1. Morning, 20 minutes, one device. Triage email with the Gmail/Outlook rules. Do not generate FYI mail. Generate only bucket-four decisions. Remember 40% of people already peeked before 6 a.m.; you are not behind because you slept.
2. Core hours. Chat is for now-work. Every “hop on?” gets a Question that tries to die in text. If you are in the 2-minute interruption weather, your replies should close loops, not start huddles.
3. Hand-off to other time zones. Continue recaps in the channel, not DMs. Clock times with zones. No EOD.
4. End of your day. If a stakeholder email is still open in your head, generate the news-first draft or snooze it to a real send time. Do not join the 16% evening meetings to soothe anxiety that a paragraph would have soothed.

None of this requires a headcount I will not invent. It requires treating Work mode as a sentence factory attached to a routing policy. I built the factory. Your team still has to hang the policy on a wall. If you want the Slack-abrupt problem, the Teams-meeting problem, or the Outlook-forward problem in isolation, leave this page and read the child. If you bounce between all of them on one phone, stay here until the routing table is boring. Boring routing plus a 2-second draft is the whole trick.

Managers: your job in this system is not to generate more. It is to stop rewarding speed on the wrong surface. If you praise the person who answered Slack in 30 seconds and ignore the person who closed the client loop in Outlook, you will get 153 Teams messages and a quiet inbox full of land mines. Put the KPI table in a 1:1. Count clarification loops for a week. The $12,506-per-employee figure is an average from 2022 research, not your payroll, but it is a useful threat model: you are already paying for the loops. Work mode is a way to make the loops shorter once you have decided where the sentence belongs.

If your company is chat-only and proud of it, you still need an email rule for the first external forward. That is the moment hybrid becomes real: a customer, an auditor, a candidate. Until then, stay on Slack or Teams and use Continue like it is infrastructure. After that moment, use Gmail or Outlook and accept that the 85% 15-second reader is your audience, not your teammates who already know the backstory. The keyboard does not choose that audience. You do, every time you pick a surface before you pick a tone.