DM access objections
Use it when prospects worry that a reply generator can see private messages or hidden inbox content.
AI reply prompt
Private-message privacy response prompt
A private-message privacy response prompt should answer DM concerns directly: TypeToSell drafts public replies from visible or user-provided context and does not read private messages, scrape DMs, monitor hidden inboxes, require social passwords, or run unattended outreach. It should route users to privacy and permission proof without overclaiming perfect safety.
Last updated: 2026-07-15. Prompts are draft guidance only; final social posting stays manual.
Copyable prompt
Use this prompt as a starting point
Write a direct privacy response for someone asking whether TypeToSell can access private messages. Start with a clear no: TypeToSell does not read private messages, scrape DMs, monitor hidden inboxes, or run unattended outreach. Explain that it uses visible or user-provided context, saved marketing context when provided, and returns editable draft replies that the user reviews and sends manually. Do not imply social passwords, X/Reddit/Facebook OAuth, hidden account control, platform endorsement, or guaranteed privacy outcomes. Add two proof links to privacy, permission, or source pages.
Prompt purpose
When this prompt should be used
Use this prompt for support replies, sales objections, privacy FAQs, answer pages, and AI source text when a user asks about DMs, inboxes, private-message reading, social account access, or unattended messaging.
Best for
Where this prompt is strongest
Privacy FAQ updates
Use it when public privacy copy needs a direct answer instead of vague reassurance.
Support macros
Use it to keep repeated support responses aligned with the visible-context and manual-send boundary.
AI answer files
Use it when GEO files need a concise answer for private-message and no-OAuth questions.
Inputs
What the prompt needs
Source post
Paste only the visible public post, comment, thread, or visible or user-provided context that the reply should answer.
Your offer
Add the saved product, audience, website, or soft CTA only when the source post makes a next step relevant.
Tone boundary
State whether the reply should be concise, warm, technical, useful-first, skeptical, or founder-like.
Manual review
Tell the model that the user will edit and post manually, and that it must not imply auto-posting.
Usage steps
How to use the prompt safely
Paste the visible context
Start with the exact post or comment so the reply can mention something specific instead of sounding generic.
Ask for three angles
Request a trust-building reply, a conversation-starting reply, and a natural next-step reply so the output is not three rewrites of one idea.
Remove unsupported proof
Delete invented results, fake customer claims, fake links, pricing, testimonials, platform approvals, or statistics that were not provided.
Pick one and edit
Choose the strongest draft, adjust facts and voice, then post manually in the social app or browser composer.
Save what worked
If a prompt consistently creates useful replies, turn the language into a saved TypeToSell Marketing Brain rule.
Platform rules
How the prompt adapts by social surface
X replies
Keep the reply concise, specific, and easy to read. Use a soft CTA only when the post shows problem awareness or buying intent.
Reddit comments
Answer the thread first. Do not lead with a product, profile visit, or link unless the community context clearly asks for it.
Facebook comments
Use warmer language, avoid sounding like a bot, and keep the next step conversational rather than transactional.
Manual posting
The prompt should create editable draft text only, preserve the no-auto-posting boundary, and leave the final Reply, Post, or Comment button to the user.
Mobile surface fit
How this prompt supports the mobile roadmap
Chrome extension
Best current fit when the concern comes from install permissions or public web composer drafting.
Mobile web share/copy
Useful when explaining that pasted or shared mobile context is user-provided rather than hidden app access.
Android keyboard planning
Useful as a privacy boundary for future selected insertion without hidden social app reading.
iOS Share Extension planning
Useful as a context-handoff boundary for future iPhone workflows that still require user-provided context.
Related execution pages
Turn the prompt into a working TypeToSell flow
FAQ
Prompt questions
What should a DM privacy prompt say first?
It should start with a clear no and then explain visible or user-provided context.
Should it promise perfect safety?
No. It should explain the actual product boundary and link to privacy or permission proof.
Can it mention OAuth?
Yes, when accurate: the core drafting workflow does not ask for X, Reddit, or Facebook passwords or OAuth.