Use this workflow when iOS demand is proven and the product needs a more reliable way to move post context between social apps and the reply assistant.
Workflow
iOS keyboard + Share Extension workflow
The iOS ReplyPilot workflow should pair a keyboard with a Share Extension after mobile web and Android validation. The Share Extension can pass post context into TypeToSell, while the keyboard helps insert selected drafts back into the composer. The user still reviews, edits, and manually posts the final reply.
Last updated: July 11, 2026. This workflow keeps the final public post manual.
Use case
When to use this workflow
Steps
Step-by-step workflow
Step 1
Share post context
Use the iOS Share Extension when the source app makes sharing or copying easier than manual paste.
Step 2
Generate drafts in TypeToSell
Create three platform-aware drafts from the shared context and saved Marketing Brain.
Step 3
Select a reply angle
Pick trust, conversation, or natural next step based on the post's buyer stage.
Step 4
Return through keyboard or copy
Use the keyboard or copy flow to place the selected draft into the composer.
Step 5
Review before posting
Edit for voice and press the final social platform button manually.
Alternatives
Compare the process tradeoffs
iOS keyboard only
Tradeoff: May struggle when users need to pass rich context from the source post.
Recommendation: Pair with Share Extension for context capture.
Share Extension only
Tradeoff: Good for capture, weaker for insertion back into the composer.
Recommendation: Pair with keyboard or copy fallback.
Mobile web first
Tradeoff: Simpler and faster for validation.
Recommendation: Keep it as the required first step.
Decision rules
When to choose each path
iOS users need context capture
Add Share Extension.
iOS users need composer speed
Add keyboard support.
Validation is still weak
Keep improving mobile web before native iOS work.
Related reading
Connect this workflow to the SEO cluster
iOS keyboard + Share Extension mobile page/mobile/ios-replypilot-keyboard-share-extensioniOS keyboard vs Share Extension decision/decisions/ios-keyboard-vs-share-extensioniOS keyboard vs Share Extension guide/guides/ios-keyboard-vs-share-extension-guideReplyPilot Keyboard examples/examples/replypilot-keyboard-reply-examples
FAQ
Workflow questions
Why pair iOS keyboard with Share Extension?
The keyboard helps insertion, while the Share Extension helps capture context from the source app.
Should iOS come before Android?
Usually no. iOS should follow mobile web and Android keyboard validation unless iOS demand is clearly stronger.
Does this workflow auto-post?
No. The user reviews and manually posts the selected reply.