Copyable template library
ReplyPilot Keyboard handoff templates separate source context, saved marketing context, selected draft insertion, and manual posting. They are planning templates for Android keyboard and iOS keyboard plus Share Extension workflows, not current app-store availability claims. Use them after mobile web share/copy proves demand.
Last updated: July 12, 2026. Templates are editable starting points, not auto-posted replies.
Template groups
Use when the workflow must pass visible post context into the reply assistant.
Source post: [visible text]. Platform: [X/Reddit/Facebook]. User intent: [trust/conversation/next step].
Context available: [what the user can see]. Context unavailable: [hidden data not accessible].
If source context is missing, ask the user to paste or share it instead of guessing.
Use when the keyboard inserts editable text but does not publish.
Insert selected draft only: [draft]. User reviews and manually presses the final platform button.
Before insertion, confirm the selected draft has no unsupported proof, store claim, or hidden data assumption.
If insertion is constrained, copy selected draft and return control to the user.
Use when source context and draft placement need separate surfaces.
Share Extension receives visible source context; keyboard or copy fallback places the selected draft.
Persist only what the reply workflow needs; avoid storing raw posts longer than necessary.
If keyboard placement fails, keep selected copy as a valid completion path.
Usage steps
Read the visible post, comment, or thread first. A template should shape the reply, not replace context.
Pick trust, conversation, soft CTA, or manual approval instead of blending every goal into one generic reply.
Swap placeholders for a specific observation, objection, audience, problem, example, or natural next step.
TypeToSell can draft, copy, or insert selected editable text, but the user still presses Reply, Post, or Comment manually.
Mobile fit
Use the template to shorten phone drafts and prove selected copy behavior before native keyboard work.
Use template slots as insertion patterns only after Android users already choose useful drafts and want less copy-back friction.
Use templates to separate source context handoff from selected draft placement, with copy fallback kept valid.
Use templates as browser-session fallback content; do not treat them as proof that native app composers are solved.
Related execution pages
Quick answers
It is a structured way to pass source context, selected draft text, and manual posting boundaries between surfaces.
No. These templates describe roadmap planning and should not be treated as current Google Play or App Store availability.
They should never imply hidden social app reading, social account control, or automatic posting.