The AI keyboard for Microsoft Teams messages.

Microsoft Teams is where I watch good operators accidentally schedule themselves into a hole. A two-line chat that needed an owner becomes “got 5 min?” becomes a calendar tile that collides with the work the chat was about. I shipped Work mode’s Continue and Question tones as an anti-meeting device as much as a writing device. This page is cross-team ad-hoc meetings and chat volume. It is not Slack’s public-channel status grammar, and it is not Outlook’s client email. If your tenant is Slack-first, read KOPY for Slack and only come back if you also live in Teams for the org next door.

Microsoft’s infinite workday special report is the volume baseline I use for this surface: about 117 emails and 153 Teams messages a day on average, 40% of people checking email before 6 a.m., meetings after 8 p.m. up 16% year over year, and 85% of emails read in under 15 seconds. The 153 is the number that should scare a Teams-heavy org. That is not 153 thoughtful notes. That is a firehose that trains you to answer in fragments, then book a meeting when the fragments collide.

The annual Work Trend Index 2025 is the interruption layer on top: about every 2 minutes during core hours, about 275 interruptions per day for the top 20% of ping volume across 24 hours, chats outside 9–5 up 15% year over year, about 58 messages before or after hours. Teams is both the chat and the meeting button. Slack can nag you. Teams can turn the nag into a third rectangle on your calendar before you have named the decision.

Writing quality still matters underneath the pings. Grammarly / Harris 2022 estimated about $1.2 trillion in U.S. losses from poor communication, about 7.47 hours per week leaders say they lose, about $12,506 per employee per year. 2024: about 19.08 hours per week writing, 100% of surveyed knowledge workers seeing weekly miscommunication. Gen AI’s up-to-$1.6 trillion communication-productivity figure is the optimistic twin. I do not put KOPY on that $1.6T. I put Work mode on the specific failure where a cross-team chat is cheaper than a meeting until someone writes a sentence that cannot be executed.

Ad-hoc meetings are usually a missing sentence

Cross-team Teams chats fail in a pattern I got tired of watching: engineering speaks in tickets, sales speaks in dates, finance speaks in freeze windows, and nobody posts the intersection. The huddle is scheduled to discover the intersection live. That is an expensive way to learn that the freeze started yesterday.

My rule: if the chat is missing owner, date, or artifact, I generate Question, not Professional. Professional will politely hallucinate alignment. Question will list the gaps. If the gaps are filled and people are still talking in circles, I generate Continue as a recap and I treat silence as assent for 30 minutes. If someone objects, they object to a written object, not to a vibe. Then I still do not book a meeting unless two of the three are true: a decision needs a voice vote, a screen must be shared, or there is a conflict that email/chat has already made worse.

The 16% rise in meetings after 8 p.m. is the aftershock of daytime chats that never closed. I would rather send a slightly stiff Continue at 5:40 p.m. than join a “quick sync” that exists because nobody wanted to look formal in a channel. Formal is cheaper than after-hours.

Channel vs chat vs meeting vs email

Teams users mix four containers. Work mode does not pick the container. You do. Wrong container is how you get 153 messages plus a meeting plus an email recap of the meeting.

• Channel thread: anything more than two people will need later. Status, decisions, “we’re slipping.” Professional or Continue.
• 1:1 or small chat: coordination, not record. Agree and Question. If a decision appears, paste a Continue into the channel. Do not leave the decision in a side chat that the next team cannot see.
• Meeting: last resort. If you book it from mobile, the invite body should be the Continue recap, not “sync.” I generate that body in the invite field with the same keyboard.
• Email: external, legal, or people who are not in the tenant. Leave Teams. Use Outlook or Gmail.

Tone map for a noisy tenant

1. Professional for leadership-visible channels and anything a customer success manager might screenshot into a ticket. Sentence one is state (on track / at risk / blocked). Sentence two is the cross-team dependency by name.
2. Question for “can we hop on” messages. I answer the implied problem, not the calendar. “I can meet if we need a voice vote. If the question is the freeze date, it’s Thursday 5pm PT — does that unblock you?” That sentence kills more huddles than any meeting-decline template.
3. Agree when you are unblocking someone and the work is actually yours. Agree names when the artifact appears. A bare thumbs-up on a @mention is how you get a second @mention an hour later.
4. Continue as the meeting replacement. Bullets: decision, owner, date, who was in the chat, who still needs to object. Post it in the thread that started the chaos, not in a new chat titled “recap.”

I avoid Funny in customer-adjacent Teams orgs. The transcript will outlive the joke. Neutral exists in the product; on Teams I reach for Professional instead because Neutral can read as disengaged to people who only know you as a profile photo.

KPI table: Teams volume vs closed work

If you only measure messages sent, Work mode looks like a way to send more. That is the wrong game. Measure closed loops against the 153-a-day weather.

KPI	Teams-specific count	Failure	Keyboard move
Time-to-send	Minutes from a @mention that required a decision to a message that contains owner or date	You reply “looking” and disappear into a meeting	Question if you cannot decide; Professional if you can
Clarification loops	Follow-up chats whose only content is decoding the last chat	Three “to confirm” messages after a “sounds good”	Continue recap; stop generating vibes
Meeting scheduled	Ad-hoc huddles/calendar holds whose invite body is empty or says “quick sync”	The 16% after-8pm meeting is born at 4pm as an unresolved chat	Answer the question in chat; if you must meet, generate the agenda in the invite
Deal follow-up lag	Hours a cross-team blocker sits because it lived in a private chat	Sales thinks eng agreed; eng never saw the chat	Promote the decision to a channel with Continue; commercial SLA belongs on sales

Deal follow-up lag on Teams is usually a handoff lag, not an SDR cadence. If quota is the clock, do not use this page as your playbook.

Mobile generate loop inside Teams

Copy the message that contains the ask, not the entire meeting transcript Teams sometimes dumps into the field. Trim @mentions that are not the ask. Switch to KOPY. Full Access still required for pasteboard and network — Apple’s keyboard extension rules, same as everywhere else. Details in how the iOS keyboard extension works.

Edit checklist I use on Teams drafts:

• Replace “we” with a name if a name exists.
• Replace “soon” with a clock time in a named timezone. Teams orgs span zones; “EOD” is how you get an evening meeting.
• If the draft offers to “jump on a call,” delete that sentence unless you already decided you need one.
• If the thread is a project channel, reply in thread. Main-channel Professional dumps are how you get 275 interruptions for other people.

For actual email records of the same decision, I do not dual-write from the sidewalk. I pick Teams or email. The remote-work pillar is the routing doc. Work email on iPhone is the compose tutorial once you have chosen email.

What I will not generate in Teams

• Performance notes in a project channel.
• Legal or security incident details in a draft that started from a copied alert I should not have put on a pasteboard.
• A meeting invite for a problem that is actually a missing RACI. Generate the RACI-shaped Continue first.
• Customer quotes invented by the model. If CS needs a sentence, they provide the sentence.

I built Work mode to make the 153-message day less stupid, not to help you win it. The winning move is a chat that prevents the 154th message and the 8 p.m. tile. That is a Continue recap with names and a time. Everything else is decoration on an interruption machine Microsoft already measured.

Guest accounts and external threads deserve a slower thumb. If the person on the other side is a vendor, a client, or a partner on a shared channel, I treat the chat as Outlook-adjacent: news first, no sarcasm, no “lol we will figure it out.” Work + Professional, then I decide whether the decision also needs an email. Usually it does not, if the shared channel is the system of record everyone already agreed to. Usually it does, if someone on their side is not in the tenant. That is a routing question for the hybrid pillar, but it shows up first as a Teams notification you will answer too fast.

I also watch for the “looping in” pile-on. Someone adds six people, none of them named as owner, and the mobile reflex is a Professional paragraph to the crowd. The crowd then produces six overlapping takes, which is how you get back to a huddle. My generate step in that moment is Question aimed at the adder: “Which decision do you need from which person by what time?” If they cannot answer, they were using @mentions as a nervous system, and a meeting will not fix their nervous system. A named owner might.