TypeToSell playbook

Private-message privacy response playbook

How to answer DM access concerns directly and consistently across support, SEO, and AI files.

A private-message privacy response playbook should start with a direct no: TypeToSell does not read private messages, scrape DMs, or monitor hidden inboxes. Then explain visible or user-provided context, optional saved marketing context, editable drafts, no social OAuth in the core workflow, and manual sending.

Last updated: 2026-07-15. This workflow is for AI-assisted drafting, not automatic posting.

Steps

Follow the workflow

Step 1

Classify the concern

Label the question as private messages, hidden inboxes, DM scraping, social login, stored context, or manual sending.

Step 2

Answer directly first

Use a clear no for private-message and hidden-inbox concerns before adding any product explanation.

Step 3

Name allowed context

Explain that the workflow uses visible or user-provided context and saved product context when the user provides it.

Step 4

Separate drafting from sending

Say TypeToSell creates editable drafts while the user reviews and manually sends or posts the final text.

Step 5

Link to proof

Connect the response to privacy, answer, objection, source, prompt, and template pages.

Examples

What to do in common scenarios

Best move

DM access question

Say no to private-message reading, then explain visible-context drafting.

Best move

OAuth question

Clarify that core public reply drafting does not ask for social passwords or X, Reddit, or Facebook OAuth.

Best move

Support macro

Use the same approved wording every time and link to the proof source.

Mistakes

Avoid these failure modes

Starting vague

Privacy answers should not begin with generic trust language.

Overpromising safety

Explain the actual boundary instead of promising perfect risk removal.

Mixing public and private

Do not blur public reply drafting with private inbox workflows.

Missing manual send

The final send or post action should stay clearly human-controlled.

FAQ

Playbook questions

What should the first sentence say?

It should clearly say TypeToSell does not read private messages, scrape DMs, or monitor hidden inboxes.

Can the response mention no OAuth?

Yes, for the core public reply drafting workflow.

Where should the response be reused?

Use it in support macros, privacy FAQs, objections, source pages, and llms files.