Workflow purpose
This workflow helps a designer write a landing page. It is designed for a situation where the user has client expectations, creative ambiguity, and layout decisions and needs hero, proof points, objections, CTA and FAQ.
Flujo
- Define the real decision: what the Designer needs after using the output.
- Add the operating context for the project: audience, constraints, proof points and unavailable information.
- Run a context-builder prompt before asking for the final deliverable.
- Generate the first version for: write a landing page.
- Ask the AI to critique its own answer against clarity, specificity and risk.
- Edit the final output manually before publishing or sending it.
Customer Service Prompts Context Builder
Best for: Designers working on support replies, service recovery, help center articles and escalation notes in general work
Act as a senior customer service specialist. You are helping a Designer in general work write a landing page. First, restate the goal in one sentence. Use this context: [context]. Audience: [audience]. Constraints: [constraints]. Brand or communication tone: [tone]. Your task is to collect missing context before trying to write a landing page. Return hero, proof points, objections, CTA and FAQ. Include: 1) a ready-to-use draft, 2) a short rationale, 3) a review checklist, and 4) three missing-information questions if the context is incomplete. Do not invent facts, prices, policies or results that are not provided.
Example input: Goal: write a landing page; scenario: a service page for a local business; constraint: keep it specific and reviewable.
Expected output: hero, proof points, objections, CTA and FAQ
Customer Service Prompts First Draft
Best for: Designers working on support replies, service recovery, help center articles and escalation notes in general work
Act as a senior customer service specialist. You are helping a Designer in general work write a landing page. First, restate the goal in one sentence. Use this context: [context]. Audience: [audience]. Constraints: [constraints]. Brand or communication tone: [tone]. Your task is to produce a usable support reply for Designer. Return hero, proof points, objections, CTA and FAQ. Include: 1) a ready-to-use draft, 2) a short rationale, 3) a review checklist, and 4) three missing-information questions if the context is incomplete. Do not invent facts, prices, policies or results that are not provided.
Example input: Goal: write a landing page; scenario: a service page for a local business; constraint: keep it specific and reviewable.
Expected output: hero, proof points, objections, CTA and FAQ
Customer Service Prompts Critique and Improve
Best for: Designers working on support replies, service recovery, help center articles and escalation notes in general work
Act as a senior customer service specialist. You are helping a Designer in general work write a landing page. First, restate the goal in one sentence. Use this context: [context]. Audience: [audience]. Constraints: [constraints]. Brand or communication tone: [tone]. Your task is to audit the macro template against the real goal and constraints. Return hero, proof points, objections, CTA and FAQ. Include: 1) a ready-to-use draft, 2) a short rationale, 3) a review checklist, and 4) three missing-information questions if the context is incomplete. Do not invent facts, prices, policies or results that are not provided.
Example input: Goal: write a landing page; scenario: a service page for a local business; constraint: keep it specific and reviewable.
Expected output: hero, proof points, objections, CTA and FAQ
Customer Service Prompts Format Converter
Best for: Designers working on support replies, service recovery, help center articles and escalation notes in general work
Act as a senior customer service specialist. You are helping a Designer in general work write a landing page. First, restate the goal in one sentence. Use this context: [context]. Audience: [audience]. Constraints: [constraints]. Brand or communication tone: [tone]. Your task is to turn raw notes into a clear escalation summary for general work. Return hero, proof points, objections, CTA and FAQ. Include: 1) a ready-to-use draft, 2) a short rationale, 3) a review checklist, and 4) three missing-information questions if the context is incomplete. Do not invent facts, prices, policies or results that are not provided.
Example input: Goal: write a landing page; scenario: a service page for a local business; constraint: keep it specific and reviewable.
Expected output: hero, proof points, objections, CTA and FAQ
Lista de revisión
- The prompt states the user role and business context.
- The output format is explicit enough to review quickly.
- The prompt asks for missing-information questions instead of invented details.
- The answer includes a checklist or next step, not only a paragraph.
- Claims, numbers, policies and examples are checked before use.
- The output matches the task: hero, proof points, objections, CTA and FAQ.
Preguntas frecuentes
Why use a workflow instead of one prompt?
A workflow separates context, drafting, critique and final formatting so the result is easier to verify.
What should the designer prepare first?
Prepare the real goal, audience, constraints, examples and deadline before using the prompt chain.
How do I store the result?
Save the final prompt, example input and a note about what worked so the workflow can be reused.
Calidad editorial
Score: 74/100
Robots: noindex,follow
Esta página es útil para usuarios, pero no se incluye en el sitemap hasta superar revisión editorial.