The AI keyboard for Outlook email replies.

Outlook on iPhone is where client and stakeholder mail goes to become either a closed decision or a 10 p.m. rewrite. I shipped Work mode’s Professional tone for this surface more than for Slack. Slack forgives a missing article. A client thread forwarded to their legal team does not. This page is stakeholder and client email from a phone against the infinite workday. It is not Gmail’s triage-first consumer-adjacent workflow — that split lives on KOPY for Gmail — and it is not a sales cadence guide.

The numbers I will actually cite live in Microsoft’s infinite workday special report: about 117 emails a day, about 153 Teams messages a day, 40% of employees checking email before 6 a.m., meetings after 8 p.m. up 16% year over year, 85% of emails read in under 15 seconds. If you only remember one, remember the 15 seconds. Stakeholder mail that opens with a weather report about your week will not be read. The person checking before 6 a.m. is not looking for warmth. They are looking for whether the date moved.

Work Trend Index 2025 explains why you are writing this mail from a phone in the first place: interrupted about every 2 minutes in core hours, about 275 interruptions per day for the noisiest fifth of workers across 24 hours, after-hours chats up 15%, about 58 messages outside 9–5. Outlook is the place those interruptions go when someone needs a forwardable sentence. If you wait until a “real keyboard,” the stakeholder has already forwarded your silence.

Quality still has a price tag. Grammarly / Harris 2022: about $1.2 trillion U.S. cost of poor communication, about 7.47 hours per week lost in leaders’ estimates, about $12,506 per employee per year. 2024: about 19.08 hours per week spent writing, 100% of surveyed knowledge workers hitting weekly miscommunication. Up to $1.6 trillion in potential gen-AI communication productivity is not a KOPY claim. It is a reminder that the hours are already going to writing. Spend them on the date and the owner, not on retyping “please find attached” with a better adjective.

Stakeholder mail has a different reader

A stakeholder is someone who can change your plan without being in your daily chat: a client sponsor, a VP who only sees the thread when it explodes, a partner who will paste your paragraph into their board deck. They read like the 85% — under 15 seconds — but they remember like a lawyer. That combination is why I do not use Continue to be chatty. I use Continue to freeze a decision in a form that survives a forward.

First sentence is the news: approved, delayed, at risk, need a decision by a clock time. Second sentence is the one number or date they will quote. Third sentence is the ask of them, with a default if they do not answer. I generate Professional for sentence rhythm, then I overwrite the number. The model does not know your contract. If it invents a date, that date will become the stakeholder’s date. I have watched that happen without AI. AI just makes the wrong date more grammatical.

Phone-specific landmines in Outlook

• Wrong account. Outlook on iOS will happily send from the personal store you used to download a PDF. Look at the From line before you look at the draft.
• Sensitivity and encryption. A generated paragraph does not set RMS. If the thread is confidential, do not copy it onto a pasteboard you would not paste into a random web form. Generate from a redacted ask.
• Meeting invites vs mail. Replying to a meeting from the mail view can surprise attendees. If the job is scheduling, Agree in the invite response, not a novel in the thread.
• Attachments. Same lie as Gmail. Search the draft for “attached.” Delete unless the paperclip is real. Offer a time the file will land if you cannot attach from the sidewalk.

Full Access remains the iOS gate: custom keyboards do not get pasteboard and network without it. I am not going to euphemize that. If your security team forbids Full Access on managed phones, KOPY will not be your Outlook solution, and you should not fight that with a screenshot of a marketing page. Use a managed desktop client. I built a consumer keyboard, not a replacement for Intune policy.

Tones when the recipient has power

1. Professional default. News first. No “just circling back” unless you are actually circling back on a promised date, in which case name the promise.
2. Question when they sent a pile. Number the questions. Max three. If you need a fourth, you need a meeting or a doc, and you should say which, because the 16% after-hours meeting growth is how piles get “solved.”
3. Agree for access, dates, and receipts. “We can make Friday 2pm ET. If I do not hear otherwise by Thursday noon ET I will send the invite.” Defaults beat chasing.
4. Continue after a call you took on a phone in a hallway. The recap email is the product. If you skip it, the stakeholder’s notes win. Generate bullets immediately while the call is still in your head. Edit names. Send.

I do not use Agree to accept scope you have not priced. That is how phone email creates unpaid work. If the stakeholder added scope in a casual P.S., Question it. Professional can make the P.S. look like it was always in the SOW.

KPI table: infinite workday Outlook

Track phone-sent mail only. Desktop Outlook hides the problem you hired a keyboard to solve.

KPI	What I count	Infinite-workday failure	Work mode
Time-to-send	Minutes from reading a stakeholder ask on the phone to a reply whose first sentence is the news	You read it before 6 a.m., compose it after 8 p.m. in your head all day	Professional news-first draft before the next 2-minute interruption
Clarification loops	Their reply that only asks “so is it Friday or not”	A hedged paragraph the 15-second reader could not parse	Put the date in sentence one; Question if you do not have it
Meeting scheduled	Holds created because the email never stated a default	After-8pm “quick call” to confirm what a Continue recap would have held	Agree with a default time; do not offer a meeting as politeness
Deal follow-up lag	Hours a client thread sits after you opened it on mobile and decided it was “too important for phone”	Importance becomes delay; delay becomes their escalation	Generate the news-first reply; if it is quota-timed, use sales rules, not intern-email hedges

A worked example without pretending it is your client

Incoming: “Need confirmation the integration still makes the 18th. Our steering committee is Tuesday.” I copy those two sentences, not the six quoted forwards. Work + Professional. I overwrite the date with the real one. If the 18th is dead, sentence one is “We cannot make the 18th.” Sentence two is the new date or “I will send a new date by 3pm ET today.” Sentence three is what I need from them (a sample file, a contact, a freeze exception). I do not open with thanks. They have 15 seconds. Thanks can be the last four words if I have the energy.

If I do not know the date yet, I do not let Professional invent one. Question: “I can confirm by 3pm ET today. If the steering committee needs a binary this morning, treat it as at risk.” That is an unpleasant email. It is an honest one. The $12,506-per-employee communication tax is full of pleasant emails that created a second project.

Routing off Outlook

If the stakeholder actually messaged you in Teams, do not “upgrade” to Outlook unless they need to forward outside the tenant. Dual-writing is how you get two dates. See Teams and the hybrid routing pillar. Recruiter threads stay on LinkedIn. Internal now-work stays on Slack if that is your chat. The keyboard is the same. The skin is not. I will keep saying that until someone stops pasting Slack fragments into client Outlook and calling it a status.

For the mechanical generate loop — copy, switch keyboard, edit, send — the blog post AI work email on iPhone is enough. This page exists because Outlook is where the infinite workday becomes visible to people who can fire you or fire your contract. Write like they will screenshot sentence one. Then send it before 8 p.m. so you are not the 16%.

On the road, Outlook is also where people try to negotiate scope because a client texted a “small ask” into the thread. Work mode will make your yes sound expensive and considered. That is dangerous. If the ask is new work, I generate Question even when I feel socially required to Agree. “I can take this as a change request. I’ll send impact on date and cost by 4pm ET.” Then I actually send the impact, or I have used the keyboard to buy a lie. The 7.47-hour waste is full of polite yeses that created a second project nobody staffed.

If you share a mailbox or a client alias, say so in the draft when it matters: “Sending from the project alias; I own the reply.” Generated Professional often writes “I” when the From line is a team. Stakeholders who search their inbox for a person’s name will miss the alias. One clause prevents a clarification loop that looks like you ignored them. That loop is how before-6 a.m. checking turns into a story about your responsiveness instead of about the date.