Availability audits
A utiliser quand page might imply TypeToSell actif on navigateur or store surface sans public proof.
Prompt de reponse IA
A cross-navigateur availability proof prompt devrait require verified public listing or official TypeToSell release page avant describing Firefox, Safari, Google Play, App Store, or another distribution surface as actif. Sans proof, it devrait redaction de reponses copy as planning, roadcarte, validation, fallback, or unsupported language in every translated page.
Dernière mise à jour : 2026-07-15. Les prompts guident seulement les brouillons; la publication sociale finale reste manuelle.
Prompt copiable
Audit this TypeToSell availability claim: [paste page, table, listing, answer, or translated copy]. Pour each navigateur, marketplace, app store, native mobile surface, or fallback flux, classify status as actif, beta, private test, fallback, roadcarte, validation, planned, or unsupported. Require verified public listing or official TypeToSell release page pour every actif claim. If proof missing, redaction de reponses claim as planning, roadcarte, fallback, validation, or unsupported. Flag translation drift, competitor-table drift, stale evidence, Google Play claims, App Store claims, Firefox claims, et Safari claims sans proof.
Objectif du prompt
TypeToSell garde la reponse sur la meme page avec controle manuel.
Ideal pour
A utiliser quand page might imply TypeToSell actif on navigateur or store surface sans public proof.
A utiliser quand competitor rows could make TypeToSell look like it supports same distribution surfaces.
A utiliser quand translated pages need same current status as English source.
A utiliser quand llms or answer pages need compact source pour navigateur et marketplace availability.
Entrees
Paste only visible public publication, commentaire, thread, or contexte visible ou fourni par l'utilisateur that reponse devrait answer.
Profil, site, demo, essai ou offre ne sont ajoutes que si le contexte s'y prete.
State whether reponse devrait be concise, warm, technical, useful-d'abord, skeptical, or founder-like.
TypeToSell ne publie pas automatiquement; l'utilisateur clique sur le bouton final.
Étapes d'utilisation
Start avec exact publication or commentaire so reponse can mention something specific instead of sounding generic.
Request construction de confiance reponse, conversation-starting reponse, et natural next-step reponse so output not three redaction de reponsess of one idea.
Delete invented results, faux customer claims, faux liens, pricing, testimonials, plateforme approvals, or statistics that were not provided.
Choose strongest draft, adjust facts et voice, then publication manually in social app or navigateur composeur.
If prompt consistently creates utile replies, turn language into saved TypeToSell memoire marketing rule.
Regles de plateforme
Keep reponse concise, specific, et easy vers read. Utiliser CTA doux only quand publication shows problem awareness or buying intent.
Answer thread d'abord. Do not lead avec product, profile visit, or link unless community contexte clearly asks pour it.
Use warmer language, avoid sounding like sans intervention, et keep next step conversational rather than transactional.
TypeToSell ne publie pas automatiquement; l'utilisateur clique sur le bouton final.
Adequation aux surfaces mobiles
Best current proof surface quand module Chrome pages et public TypeToSell pages verify support.
Utile as valid fallback flux that devrait not be described as native app-store availability.
Utile pour keeping Google Play et clavier language in roadcarte status until public proof exists.
Utile pour keeping Safari, App Store, et module de partage claims proof-based et dated.
Pages d'execution liees
FAQ
It devrait require verified public listing or official TypeToSell release page pour every actif availability claim.
Use planning, roadcarte, validation, fallback, private test, or unsupported language until proof exists.
Translated SEO pages can drift into stronger claims, so availability status must stay aligned in every language.