The AI keyboard for Gmail replies on iPhone.

Most Gmail messages that arrive on an iPhone should not get a reply. They should get a label, a snooze, a forward, or a delete. I shipped Work mode anyway because the ones that do need a reply are the ones you rewrite for twelve minutes on a software keyboard and still send with a missing attachment line. This page is mobile-first drafts and the split between triage and reply. It is not Outlook’s client-stakeholder infinite workday — that is KOPY for Outlook — and it is not Slack status tone.

I wrote a shorter procedural post at how to reply to work emails faster on iPhone. That post is the seven-step app-switch tax. This article is the decision tax: when generating is malpractice because you have not decided whether the thread is yours.

Email is where the Grammarly numbers stop being abstract. The 2022 Grammarly / Harris estimate of about $1.2 trillion lost to poor communication, 7.47 hours per week of leader-estimated waste, and about $12,506 per employee per year is largely email-shaped even when the original sin happened in chat. People “confirm in writing” after a messy Slack thread and then the email is messy too. 2024 adds that writing already consumes about 19.08 hours per week and that 100% of surveyed knowledge workers hit weekly miscommunication. Up to $1.6 trillion in gen-AI communication productivity is the optimistic mirror. None of that pays you to auto-reply to newsletters.

Microsoft’s infinite workday special report is the volume argument: people average about 117 emails a day, 40% check email before 6 a.m., and 85% of emails are read in under 15 seconds. If you cite those three numbers, that is the source — not the annual WTI interruption study. The 15-second read is why I generate short. A Professional draft that opens with a paragraph of context will not be read. The reader already had the context. They opened Gmail on a phone to see the decision.

Triage before the keyboard

I keep a four-bucket triage that happens with my thumb on the list view, not in the compose field. Work mode is illegal in my own workflow until the message is in bucket four.

1. Not mine. Archive, unsubscribe, or filter. Generating a polite decline to a vendor newsletter is how you train yourself to fear the inbox.
2. FYI. Read in under 15 seconds, which the infinite-workday research says is the common fate anyway. Star if you need it for a meeting. Do not reply “thanks.”
3. Needs a forward or a task. The reply is not prose; it is routing. Forward with one sentence of owner. I will generate that one sentence. I will not generate a memoir.
4. Needs a decision in writing. Now you copy, switch to KOPY, Work mode. This is the only bucket where Professional / Question / Agree / Continue earn their keep.

If you skip triage, you will use AI to become more fluent at the wrong work. That is how you spend the 19.08 writing hours on messages that should have been a label.

What I copy out of Gmail

Gmail’s copy behavior on iOS is sloppy. You will grab quoted history, a legal footer, and a calendar invitation in ICS poetry. Trim to: the ask, the deadline if present, and one constraint (budget, audience, compliance). The model does not need the last four “per my last email” rounds. Those rounds are how drafts get sarcastic.

Custom keyboards need Full Access to read that trimmed pasteboard and to hit the API. If you refuse Full Access, you can still type. You cannot condition a draft on the message. There is no magic “Gmail integration” inside the keyboard extension. Copy is the integration. I am fine with that. It keeps KOPY from being a mail client with opinions about your labels.

Tone by email job, not by mood

Mood is how you get “Hope you’re well” on a thread about a missed SLA. Jobs:

• Professional for external-ish mail even when the person is a coworker: anything that might be forwarded. Include the decision in sentence one. Sentence two is the date. Sentence three is the ask of them, if any. Stop.
• Question when the thread is a pile of implied asks. Turn them into a numbered list of at most three questions. If you need more, you do not have an email, you have a meeting — and you should still ask whether the meeting is required, because Teams will happily spawn one.
• Agree for scheduling and receipts. “Thursday 10am PT works. Please send the invite to this address.” That is the whole email. Agree that restates the entire project is a status report in the wrong clothes.
• Continue when the thread went quiet with an unrecorded decision. Recap bullets: decided, owner, next artifact, date. This is the email people search for a month later.

I use Continue more in Gmail than in Slack. Slack threads are visible. Email decisions vanish into other people’s “unread.” Continue is how you make a searchable artifact without waiting until you are at a laptop to “write it properly.” The 15-second reader still needs those bullets.

KPI table: Gmail mobile, not inbox-zero cosplay

Inbox zero is a personality. These KPIs are operational. Track them for five workdays on the phone only. Desktop mail will flatter you.

KPI	Mobile definition	Bad pattern	Work mode’s lane
Time-to-send	Minutes from opening a bucket-four email to sending a decision-bearing reply	You read it at 7:40 a.m., rewrite in your head until 11, send a hedging paragraph	Professional first sentence = the decision; you add the real date
Clarification loops	Inbound replies that only exist because you omitted the date, owner, or attachment	“Can you send that as a PDF?” on a thread you thought was done	Question if you cannot attach on mobile; say when the artifact arrives
Meeting scheduled	Holds created from Gmail because the email could not close a yes/no	A 30-minute meeting to confirm a date that belonged in sentence one	Agree with two windows, or Continue recap that makes the meeting unnecessary
Deal follow-up lag	Hours a customer or vendor thread sits after you opened it on your phone and decided to “do it later”	You triaged it into your brain, not into a sent message	If it is commercial SLA, generate now or snooze to a time you will actually send — see sales

If 40% of people already check email before 6 a.m., the competitive move is not checking earlier. It is sending a closed-loop reply so you do not reopen the same thread at 9:12. I check because I am weak. I generate because I am not going to write a client-quality paragraph in bed. That is a boundary, not a hustle tip.

Gmail-specific failure modes

The CC forest. Eight people, no named owner. A Professional draft that says “we” will spawn eight interpretations. Name one owner. If you cannot, Question: “Who owns the revision by Wednesday?” Do not generate a pep talk.

The attachment lie. Drafts love “attached.” On a phone you often have not attached. I trained myself to search the draft for that word and delete it unless the paperclip is real.

The Reply vs Reply-all reflex. Generation does not choose recipients. You do. Work mode will not save you from answering all-staff with a side conversation. Look at the To line before you look at the draft.

The thread that is actually a document. If the reply needs a table, a quote, or a legal paragraph, stop generating in Gmail mobile. Notes or desktop. You can still use KOPY in those fields. You should not pretend a 900-word statement of work belongs in a thumb draft.

How this sits next to chat

People try to answer Slack pings via Gmail “so it’s documented.” Then they answer the same ping in Slack because the requester never saw the email. Pick a surface. The remote-work pillar is the routing guide. Slack for now-work and status; Gmail for anything that will be forwarded to a person who is not in the channel. LinkedIn recruiting stays in LinkedIn. Teams ad-hoc meetings stay in Teams. If you generate the same status in three tools, you have created a fourth job: reconciliation.

I use Gmail Work mode when the record matters and the reader will only give me 15 seconds. That constraint is in the research. It is also in your sent folder if you are honest. First sentence is the decision. Everything else is optional. The keyboard’s job is to get that sentence out of your hands before the train doors close, without the empty “circling back” that the 15-second reader has already learned to skip.

One more mobile habit that is not in the research and is still true: if you generate a draft and then keep the thread open while you “just tweak the tone,” you will spend the 7.47-hour tax on a message that was already sendable. I give myself one edit pass for facts and one for recipients. After that I send or I snooze. Work mode is a first draft, not a workshop. If the workshop is required, you are not in Gmail on a phone anymore — you are writing a document, and you should be honest about that before you burn the rest of the 19.08 writing hours on a compose window the other person will glance at for under 15 seconds.