Owner
iOS product owner responsible for Share Extension and keyboard handoff.
Standard operating procedure
iOS keyboard + Share Extension SOP
An iOS keyboard plus Share Extension SOP should separate source context handoff from selected draft placement. The Share Extension passes visible source context into TypeToSell; keyboard insertion or copy fallback places the selected editable draft. This SOP should follow mobile web and Android learning because paired iOS native surfaces are more complex than a mobile web share/copy MVP.
Cadence
Run after mobile web and Android evidence justify native iPhone investment.
Last updated: July 12, 2026. The final platform action stays manual.
Inputs
Required inputs before the SOP starts
Visible source context
Use the actual visible post, comment, thread, or pasted text that the user wants to answer.
Saved marketing context
Use only saved product, audience, offer, voice, website, and soft CTA rules; do not invent proof.
Manual posting boundary
The process ends with selected editable text. The user still presses Reply, Post, or Comment manually.
Mobile surface status
Label whether the process is current mobile web, roadmap Android keyboard, roadmap iOS native flow, or browser fallback.
Procedure
Run the steps in order
Split the two jobs
Document which surface captures source context and which surface places the selected draft.
Define storage limits
Decide what source text, generated drafts, and user selections can persist and for how long.
Test Share Extension context
Pass only visible source context into TypeToSell without implying private social account access.
Test draft placement
Use keyboard insertion when possible and selected copy fallback when iOS constraints block insertion.
Review manual approval
Confirm the user edits the selected draft and manually taps the final platform action.
QA gates
What must pass before handoff
Specificity gate
The draft must include one detail from the source post or a clear reason it is asking for more context.
CTA pressure gate
Cold replies should usually have no CTA. Problem-aware replies can include one optional next step.
Proof gate
Remove unsupported statistics, testimonials, pricing, customer outcomes, review scores, store availability, or platform approval claims.
Manual approval gate
The operator must be able to point to the final human edit and manual platform action before the reply is published.
Fail conditions
What blocks the SOP
Auto-posting implication
Fail the SOP if copy says or implies TypeToSell clicks the final Reply, Post, Comment, or Publish button.
Hidden context assumption
Fail the SOP if it assumes a keyboard or extension can read private or unavailable social app content.
Unsupported availability
Fail the SOP if roadmap surfaces sound currently available in Google Play or the App Store without dated proof.
Guaranteed outcome claim
Fail the SOP if it promises replies, followers, leads, revenue, rankings, or platform safety guarantees.
Related execution pages
Connect this SOP to the rest of the system
iOS keyboard + Share Extension workflow/workflows/ios-keyboard-share-extension-workflowiOS Share Extension fix/fixes/ios-share-extension-context-handoff-fixiOS validation plan/validation/ios-keyboard-share-extension-validation-planReplyPilot handoff templates/templates/replypilot-keyboard-handoff-templates
Quick answers
SOP questions
Why does iOS need a Share Extension SOP?
The Share Extension handles visible source context, while keyboard or copy fallback handles selected draft placement.
Should iOS come before Android?
Usually no. Android is a cleaner native insertion test after mobile web validation.
Is this an App Store availability claim?
No. This SOP is roadmap planning and should not be treated as current App Store availability.