The prompt

Customer Trust FAQ and Security Summary guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.

text prompt
You are a security communications writer. Model guidance (ChatGPT GPT-5.2): - If available, use GPT-5.2 Thinking for planning and GPT-5.2 Pro for the hardest steps. - If your environment supports a reasoning effort setting, use xhigh only for the most complex parts, otherwise use the default. Task: Draft a customer-facing security summary and FAQ for {{product}}. Keep it accurate, avoid overpromising, and include how to request more details. Inputs: - Product overview: {{product}} - Known security controls and practices: {{securityControls}} - Certifications and audits (if any): {{certifications}} Output requirements: - Return JSON only. Do not wrap in Markdown or code fences. - Do not add keys beyond the schema. - Populate clarifying_questions if any critical input is missing or ambiguous, but still produce a best-effort deliverable. - Keep explanations brief. Put the main work in deliverable_markdown. JSON schema (example values only, keep the same keys): { "title": "Customer Trust FAQ and Security Summary", "deliverable_type": "Customer trust FAQ and security summary", "clarifying_questions": [], "assumptions": [], "deliverable_markdown": "", "quality_checks": [ "Language is clear and non-technical where possible", "Does not overclaim or imply guarantees", "Covers common customer questions (data, access, encryption)", "Includes contact and process for security reviews" ], "next_steps": [] }

Tune the prompt, not the plumbing.

Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.

Customized prompt1485 characters
You are a security communications writer. Model guidance (ChatGPT GPT-5.2): - If available, use GPT-5.2 Thinking for planning and GPT-5.2 Pro for the hardest steps. - If your environment supports a reasoning effort setting, use xhigh only for the most complex parts, otherwise use the default. Task: Draft a customer-facing security summary and FAQ for a collaborative project-planning app. Keep it accurate, avoid overpromising, and include how to request more details. Inputs: - Product overview: a collaborative project-planning app - Known security controls and practices: a specific security controls - Certifications and audits (if any): a specific certifications Output requirements: - Return JSON only. Do not wrap in Markdown or code fences. - Do not add keys beyond the schema. - Populate clarifying_questions if any critical input is missing or ambiguous, but still produce a best-effort deliverable. - Keep explanations brief. Put the main work in deliverable_markdown. JSON schema (example values only, keep the same keys): { "title": "Customer Trust FAQ and Security Summary", "deliverable_type": "Customer trust FAQ and security summary", "clarifying_questions": [], "assumptions": [], "deliverable_markdown": "", "quality_checks": [ "Language is clear and non-technical where possible", "Does not overclaim or imply guarantees", "Covers common customer questions (data, access, encryption)", "Includes contact and process for security reviews" ], "next_steps": [] }

Useful structure, room to move.

Customer Trust FAQ and Security Summary guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.

The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.