Availability audits
Use it when a page might imply TypeToSell is live on a browser or store surface without public proof.
AI reply prompt
Cross-browser availability proof prompt
A cross-browser availability proof prompt should require a verified public listing or official TypeToSell release page before describing Firefox, Safari, Google Play, App Store, or another distribution surface as live. Without proof, it should rewrite copy as planning, roadmap, validation, fallback, or unsupported language in every translated page.
Last updated: 2026-07-15. Prompts are draft guidance only; final social posting stays manual.
Copyable prompt
Use this prompt as a starting point
Audit this TypeToSell availability claim: [paste page, table, listing, answer, or translated copy]. For each browser, marketplace, app store, native mobile surface, or fallback workflow, classify the status as live, beta, private test, fallback, roadmap, validation, planned, or unsupported. Require a verified public listing or official TypeToSell release page for every live claim. If proof is missing, rewrite the claim as planning, roadmap, fallback, validation, or unsupported. Flag translation drift, competitor-table drift, stale evidence, Google Play claims, App Store claims, Firefox claims, and Safari claims without proof.
Prompt purpose
When this prompt should be used
Use this prompt before publishing comparison pages, alternative pages, app-store ASO pages, cross-browser answers, launch announcements, llms files, or localized pages that mention where TypeToSell is available.
Best for
Where this prompt is strongest
Comparison tables
Use it when competitor rows could make TypeToSell look like it supports the same distribution surfaces.
Localized SEO pages
Use it when translated pages need the same current status as the English source.
AI citation safety
Use it when llms or answer pages need a compact source for browser and marketplace availability.
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 proof surface when Chrome extension pages and public TypeToSell pages verify support.
Mobile web share/copy
Useful as a valid fallback workflow that should not be described as native app-store availability.
Android keyboard planning
Useful for keeping Google Play and keyboard language in roadmap status until public proof exists.
iOS Share Extension planning
Useful for keeping Safari, App Store, and Share Extension claims proof-based and dated.
Related execution pages
Turn the prompt into a working TypeToSell flow
FAQ
Prompt questions
What proof should the prompt require?
It should require a verified public listing or official TypeToSell release page for every live availability claim.
How should unproven surfaces be described?
Use planning, roadmap, validation, fallback, private test, or unsupported language until proof exists.
Why include translated copy?
Translated SEO pages can drift into stronger claims, so availability status must stay aligned in every language.