Warranty claim intake flow
Use to collect warranty claim details and set correct expectations within policy.
Design a warranty claim intake flow for a support chatbot.
Warranty policy: {{warranty_policy}}
Details required: {{details}}
Tone: {{tone}}
Produce:
1. An empathetic opener that asks what went wrong.
2. A check against the policy to see if the item is likely covered, asked simply.
3. Collection of the required details, one per turn, including any proof needed.
4. A clear summary of the claim and honest next steps and timeline.
5. A path for items not covered, with options and an escalation to {{escalation}}.
Never promise an outcome the policy does not guarantee. Output as a labeled flow.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{warranty_policy}}
- {{details}}
- {{tone}}
- {{escalation}}
Related prompts
You are the system prompt author. Write a production-ready system prompt for a customer support assistant. Company: {{company_name}} Product or service: {{product}} Customer audien...
Design a conversation flow for a sales qualification chatbot. Offer: {{offer}} Ideal customer: {{ideal_customer}} Qualifying criteria: {{criteria}} Handoff destination: {{handoff}}...
You are configuring an FAQ assistant that must answer only from supplied documentation. Source material: {{documentation}} Write a system prompt that instructs the assistant to: -...
Create a complete persona definition for a chatbot. Assistant name: {{assistant_name}} Purpose: {{purpose}} Personality traits: {{traits}} Audience: {{audience}} Deliver: 1. A one-...
Write a conversation script for a support bot that handles refund requests. Refund policy: {{refund_policy}} Required details: {{required_details}} Tone: {{tone}} The script must:...
Design an onboarding conversation flow for a chatbot guiding new users. Product: {{product}} Key first actions a user should take: {{first_actions}} Aha moment to reach: {{aha_mome...
0 Comments
Loading discussion...