The AI keyboard for sales outreach and follow-ups.

Sales email is not stakeholder-care email with a dollar sign. The clock is the deal, not the relationship newsletter. I shipped Work mode’s Continue and Question tones for pipeline follow-ups I was tired of watching die in “just bumping this” while the rep was on a train. This page is response-time SLA and follow-up lag. It is not an HR tone guide, not a recruiter-InMail guide — that is LinkedIn — and not a lesson in writing kinder internal mail. If you came here from a customer-success culture doc, you are in the wrong building.

I will not invent win rates, ramp times, or “customers saved.” I will use the communication research as weather, then talk about the sentence that either advances a next step or admits the deal is idle. Grammarly / Harris 2022: about $1.2 trillion lost to poor communication in the U.S., about 7.47 hours per week in leaders’ estimates, about $12,506 per employee per year. In a sales org that tax shows up as extra discovery loops, not as a warmer culture. 2024: about 19.08 hours per week writing, 100% of surveyed knowledge workers reporting weekly miscommunication. Up to $1.6 trillion in gen-AI communication productivity is the macro ceiling. Sequence tools already tried to collect it with templates. Templates trained buyers to skim. Work mode only helps if you copy their last message and answer the actual objection.

Speed of context-switching is the other tax. WTI 2025: about every 2 minutes in core hours, about 275 interruptions per day for the noisiest fifth over 24 hours, after-hours chats up 15%, about 58 messages outside 9–5. Infinite workday: about 117 emails and 153 Teams messages a day, 40% on email before 6 a.m., after-8 p.m. meetings up 16%, 85% of emails read in under 15 seconds. Buyers live in that weather too. Your follow-up gets 15 seconds. If sentence one is not the next step or the answer to their last constraint, you burned the SLA even if you hit the SLA on the clock.

SLA is a sentence design problem

A response-time SLA — 15 minutes during business hours, an hour, same day — is usually measured as “time to first outbound byte.” That metric is how you get empty “got it, will follow up.” I care about time to next-step sentence: a time, a yes/no on the constraint they named, or a Question that unblocks a calendar hold. Generating a Professional paragraph that restates their website is not hitting the SLA. It is hitting send.

On a phone, the empty “got it” is the default because the real sentence needs a CRM field you do not have in the subway. Work mode does not fetch Salesforce. You still copy their email, generate Continue or Question, and type the one CRM fact you remember (the seat count, the close month, the competitor they named). If you remember nothing, do not generate a fake recap. Question: “Before I send times, is the blocker still legal review of DPA, or has that moved?” Specificity is the product. Warmth is optional and often suspicious.

Follow-up types that are not “checking in”

1. Same-thread objection. They named price, security, timing, or a missing feature. Professional answers that noun in sentence one. Do not bury it under a compliment.
2. Multi-thread no-reply. They went quiet. Continue adds one new fact (a customer-shaped proof you can actually defend, a date your calendar still has, a doc you will attach when you are not on a phone). One fact. Not a guilt stack.
3. Internal blocker posing as a buyer delay. Your SE has not sent the architecture diagram. Do not generate a buyer-facing stall. Ping the SE on Slack or Teams with a Question that names the artifact. The SLA to the buyer starts when you have the artifact or when you tell them the time it lands.
4. Procurement / legal. This looks like Outlook stakeholder mail. Use news-first Professional from Outlook or Gmail. Do not use sales-urgency on a lawyer. They will slow-walk you for sport.

“Checking in” is not on the list because it is not a type. It is a failure to pick a type. If you cannot pick, you are not ready to send, and generating will only make the failure grammatical.

Tones for pipeline, not for belonging

• Professional: answers, quotes, and anything that might be forwarded to a buying committee. Sentence one is the answer. The 15-second read is the committee member on a phone before 6 a.m.
• Question: when you are missing the constraint that makes a meeting useful. Two questions max. A questionnaire is a form; send a form.
• Agree: they offered times or a process. Agree locks it: “Thursday 10am ET works. Invite sent to the three addresses below.” If you cannot send the invite from the phone, say when it will land. Do not Agree into a floating “perfect.”
• Continue: the stalled thread. Recap the last agreed next step, add one new fact, propose two new times or a yes/no. Continue is not a memoir of how much you enjoyed the call.

I do not use Agree to accept discounts you have not approved. I do not use Professional to threaten a close date you invented. The model will help you sound sure. Sure and wrong is how you get the miscommunication statistic to show up as a slipped forecast.

KPI table: pipeline lag on mobile

If your CRM already has these fields, use them. If it does not, a paper tally for one week will still show you where the keyboard matters.

KPI	Sales definition	Failure	Work mode
Time-to-send	Minutes from inbound buyer message during SLA hours to a next-step sentence (not “got it”)	You hit 15 minutes with an empty acknowledgement, then the real answer lands tomorrow	Copy their constraint, Professional or Question, inject the CRM fact you actually know
Clarification loops	Buyer replies that only exist because you did not answer the noun they used (price, DPA, seats, date)	Three-mail dance to learn you cannot discount	Put the noun in sentence one; stop generating atmosphere
Meeting scheduled	Holds that appear after a follow-up, with attendees who can decide	A 16% evening “quick call” with people who cannot sign	Question who must attend; Agree only when times and people are real
Deal follow-up lag	Hours or days between the promised next step and the next outbound that contains a new fact or a clear close	Sequence-mail “just bumping” with no new fact; buyer skims in under 15 seconds and bins it	Continue + one new fact, or a honest close-lost; do not generate hope

Deal follow-up lag is the headline KPI on this page. Time-to-send is necessary and insufficient. You can be fast and still be the 117th email of their day. The new fact is how you earn a second 15 seconds.

LinkedIn vs email for the same opportunity

If the buyer wrote in LinkedIn, answer in LinkedIn unless they asked for email. Jumping surfaces looks like a sequence tool having a stroke. LinkedIn skin is still more personal than email; keep it shorter. The recruiter page will teach you the wrong warmth if you steal from it — hiring replies optimize for reputation, sales replies optimize for a next step. If you need InMail manners for a hiring-adjacent dual role, split your brain: LinkedIn for recruiting, this page for quota.

Copy, Full Access, generate: same iOS keyboard rules as every other surface. Do not copy a full contract onto the pasteboard. Copy the clause they asked about. Details on the extension model: how keyboard extensions work. Longer non-sales email craft: work email on iPhone. Hybrid routing if you also live in chat: remote work.

What I refuse to generate for sales

• Fake social proof. If the draft names a customer I did not type, I delete the sentence.
• Urgency without a real constraint. “Rates go up Friday” when they do not is not Professional. It is a problem later.
• Internal blame. “My SE is behind” in a buyer-facing draft. Handle that on Slack/Teams.
• HR-shaped empathy paragraphs on a pricing thread. Empathy is a phone call or a precise concession, not a generated hug.

I built Work mode so a rep could answer the noun in the buyer’s last message before the next 2-minute interruption stole the thread from working memory. That is the whole sales case. Not a new personality. Not a sequence replacement. A first draft that assumes the buyer will give you 15 seconds, that your SLA is real, and that “just circling back” is how follow-up lag becomes a slipped quarter you will later describe as a communication problem — which, per the $1.2T research, it was.

A note on after-hours: the 58 messages and the 15% after-hours chat rise will tempt you to treat SLA as 24/7. I do not. If the buyer wrote at 9:40 p.m., a Professional draft can wait until your published hours unless they named a same-night incident. Sending at 10:12 p.m. trains them to expect you in the 16% evening-meeting bucket. Schedule-send exists in Gmail and Outlook; use it. LinkedIn is worse; there the timestamp is part of the theater. I still wait unless the thread is a live negotiation with a close in hours, not days.

If you sell with a partner or a SE on the thread, say who sends next in the generated Continue. “I’ll send the security answers by 2pm ET; Priya will send the architecture one-pager by 5pm ET.” Unowned dual-send is a clarification loop wearing a friendly face. The buyer’s 15-second read cannot parse “we.” Name the artifact and the person. Then go hit the SE on Teams or Slack with a Question that is allowed to sound internal and blunt. Mixing those two voices in the buyer thread is how you get HR-shaped sales email, which is the thing this page exists to prevent.