Owner
Growth operator or founder responsible for daily public reply practice.
Standard operating procedure
Mobile web share/copy daily SOP
A mobile web share/copy daily SOP should prove that users can provide visible context, generate three drafts, choose one, copy it back to X, Reddit, or Facebook, edit it, and manually post. This is the first SOP TypeToSell should run because it validates mobile demand before Android ReplyPilot Keyboard, iOS keyboard plus Share Extension, or mobile browser extension complexity.
Cadence
Run daily for two weeks before judging native mobile demand.
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
Collect mobile candidate posts
Save 5 to 10 public posts from X, Reddit, or Facebook that can be answered from a phone without private context.
Open mobile web generator
Paste or share the visible source context into TypeToSell and choose the platform before drafting.
Generate three angles
Create trust, conversation, and natural next-step drafts so the user chooses from distinct reply intents.
Copy one selected draft
Record whether the user copied a selected draft, edited it, and returned to the source app manually.
Tag the blocker
If the reply is not posted, tag the reason as weak draft, copy-back friction, missing context, CTA concern, or manual approval confusion.
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
Quick answers
SOP questions
Why should mobile web SOP come first?
It validates demand, selected copy, return-to-app behavior, and manual posting before native platform complexity.
What is the main success signal?
Selected copied drafts plus repeat mobile sessions are stronger signals than generation starts alone.
Does this SOP replace Android keyboard?
No. It decides whether Android keyboard deserves to be the next surface.