Owner
Founder, agency operator, creator, or sales lead approving public replies.
Standard operating procedure
Manual approval AI reply SOP
A manual approval AI reply SOP should make every public reply pass through visible context, three draft angles, human selection, edit review, and manual final posting. It protects TypeToSell from auto-posting confusion, unsupported proof, hidden account control claims, and spammy CTA pressure.
Cadence
Run before every copied, inserted, or posted AI-generated social reply.
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
Verify source context
Confirm the draft responds to the actual visible post and not a guessed topic.
Choose one draft angle
Pick trust, conversation, or natural next step; do not blend all three into one noisy reply.
Edit for platform
Shorten X replies, make Reddit useful-first, and keep Facebook warmer and more conversational.
Run claim review
Remove unsupported numbers, testimonials, pricing, product claims, and availability statements.
Post manually
The user presses the final Reply, Post, or Comment button after reviewing the editable text.
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
What does manual approval mean?
The user reviews, edits, and personally presses the final platform button after AI drafts text.
What should block approval?
Missing source context, invented proof, auto-posting language, hidden account control, or excessive CTA pressure should block approval.
Does TypeToSell click Reply or Comment?
No. TypeToSell drafts, copies, or inserts selected editable text only.