Creating Customer Support Prompts

This tutorial explains how to design effective prompts for customer support scenarios, helping you generate consistent, helpful responses to customer inquiries, troubleshoot issues, and handle various support situations.

Prerequisites

• A Cognipeer account with access to the Prompts feature
• Basic understanding of customer support principles
• Familiarity with prompt creation and parameters

Tutorial Steps

Step 1: Understand Customer Support Prompts

Customer support prompts have specific characteristics that make them effective:

• Clear problem identification
• Appropriate tone and empathy
• Structured troubleshooting steps
• Policy references when needed
• Escalation paths
• Follow-up procedures

Step 2: Plan Your Customer Support Prompt

For this tutorial, we'll create a versatile customer support response prompt:

1. Core elements:

   • Customer information
   • Issue description
   • Product/service details
   • Response tone and style
   • Troubleshooting steps
   • Policy references
   • Escalation options

2. Parameters to include:

   • Text parameters for customer details, issue description, product information
   • Checkbox parameters for optional response elements
   • Date parameters for follow-up scheduling

Step 3: Create a New Prompt

1. Navigate to the Prompts section in the sidebar
2. Click the Create Prompt button
3. Enter the following details:
   • Title: "Comprehensive Customer Support Response"
   • Description: "Creates professional, helpful responses to customer inquiries with appropriate troubleshooting and follow-up"
   • Tags: "customer support, response, troubleshooting" (optional)

Step 4: Write the Prompt Text

1. In the Prompt Text field, enter the following:

Create a customer support response for { {customer_name:text} } who has contacted us about an issue with { {product_name:text} }.

CUSTOMER INFORMATION:
- Customer since: { {customer_since:text} }
- Subscription/Plan: { {subscription_type:text} }
- Previous interactions: { {previous_interactions:text} }

ISSUE DETAILS:
{ {issue_description:text} }

RESPONSE GUIDELINES:
- Tone: { {tone:text} } (e.g., professional, friendly, empathetic)
- Priority level: { {priority_level:text} } (e.g., low, medium, high, urgent)

RESPONSE STRUCTURE:

1. GREETING
Start with a personalized greeting acknowledging the customer.

2. ACKNOWLEDGMENT
Acknowledge the issue and express understanding/empathy.

3. SOLUTION/TROUBLESHOOTING
{ {include_troubleshooting:checkbox} } Include the following troubleshooting steps:
- { {troubleshooting_step_1:text} }
- { {troubleshooting_step_2:text} }
- { {troubleshooting_step_3:text} }

{ {include_solution:checkbox} } Provide this specific solution:
{ {solution_details:text} }

4. POLICY INFORMATION
{ {include_policy:checkbox} } Include the following policy information:
{ {policy_details:text} }

5. ESCALATION
{ {include_escalation:checkbox} } Include escalation information:
This issue has been escalated to our { {escalation_team:text} } team. A specialist will contact you within { {response_time:number} } business hours.

6. FOLLOW-UP
{ {include_follow_up:checkbox} } Include follow-up information:
I've scheduled a follow-up on { {follow_up_date:date} } to ensure your issue has been resolved.

7. CLOSING
End with an appropriate closing, offering additional assistance if needed.

ADDITIONAL NOTES:
{ {additional_instructions:text} }

2. This prompt includes multiple parameter types to create a flexible customer support template:
   • Text parameters for customer and issue details
   • Checkbox parameters for optional response sections
   • Date parameters for follow-up scheduling

Step 5: Preview and Save Your Prompt

1. Click the Preview button to see how your prompt will appear to users
2. Test filling in the parameters to ensure they work as expected
3. Set the appropriate Visibility Settings
4. Click Save to create your prompt

Step 6: Create Specialized Support Prompts

Now that you understand the structure of customer support prompts, create additional prompts for different support scenarios:

Technical Troubleshooting Prompt

1. Create a new prompt titled "Technical Troubleshooting Response"
2. Use the following prompt text:

Create a technical troubleshooting response for a customer experiencing issues with { {product_name:text} }, specifically related to { {issue_type:text} }.

CUSTOMER INFORMATION:
- Customer name: { {customer_name:text} }
- Product version: { {product_version:text} }
- Operating system/environment: { {environment:text} }
- Error message/code (if any): { {error_message:text} }

ISSUE DETAILS:
{ {issue_description:text} }

TROUBLESHOOTING APPROACH:
- Diagnostic level: { {diagnostic_level:text} } (e.g., basic, advanced, expert)
- Estimated resolution time: { {estimated_time:text} }

RESPONSE STRUCTURE:

1. GREETING AND ACKNOWLEDGMENT
Start with a professional greeting and acknowledge the technical issue.

2. ISSUE IDENTIFICATION
Confirm understanding of the issue and its impact.

3. DIAGNOSTIC QUESTIONS
{ {include_diagnostic_questions:checkbox} } Include these diagnostic questions to gather more information:
- { {diagnostic_question_1:text} }
- { {diagnostic_question_2:text} }
- { {diagnostic_question_3:text} }

4. TROUBLESHOOTING STEPS
Provide a step-by-step troubleshooting process:

Step 1: { {troubleshooting_step_1:text} }
Expected outcome: { {expected_outcome_1:text} }

Step 2: { {troubleshooting_step_2:text} }
Expected outcome: { {expected_outcome_2:text} }

Step 3: { {troubleshooting_step_3:text} }
Expected outcome: { {expected_outcome_3:text} }

{ {include_advanced_troubleshooting:checkbox} } Include these advanced troubleshooting steps if the basic steps don't resolve the issue:
- { {advanced_step_1:text} }
- { {advanced_step_2:text} }

5. EXPLANATION
{ {include_technical_explanation:checkbox} } Include a brief technical explanation of what might be causing the issue:
{ {technical_explanation:text} }

6. PREVENTION
{ {include_prevention_tips:checkbox} } Include tips to prevent this issue in the future:
{ {prevention_tips:text} }

7. ESCALATION PATH
{ {include_escalation:checkbox} } If these steps don't resolve the issue, provide escalation information:
Please contact our { {escalation_team:text} } team at { {contact_method:text} } with reference number { {reference_number:text} }.

8. CLOSING
End with an appropriate technical support closing.

ADDITIONAL NOTES:
{ {additional_instructions:text} }

Refund Request Prompt

1. Create a new prompt titled "Refund Request Response"
2. Use the following prompt text:

Create a response to a refund request from { {customer_name:text} } for { {product_or_service:text} } purchased on { {purchase_date:date} } for ${ {purchase_amount:number} }.

REFUND REQUEST DETAILS:
- Reason for refund: { {refund_reason:text} }
- Order/Transaction ID: { {order_id:text} }
- Request date: { {request_date:date} }
- Days since purchase: { {days_since_purchase:number} }

REFUND POLICY INFORMATION:
- Standard refund period: { {refund_period:number} } days
- Special circumstances: { {special_circumstances:text} }
- Documentation required: { {documentation_required:text} }

REFUND DECISION:
{ {refund_approved:checkbox} } The refund request is approved.

RESPONSE STRUCTURE:

1. GREETING
Start with a professional, empathetic greeting.

2. ACKNOWLEDGMENT
Acknowledge the refund request and summarize understanding of the situation.

3. POLICY REFERENCE
Briefly reference the relevant refund policy.

4. DECISION AND EXPLANATION
{ {if_approved:checkbox} } If approved:
- Confirm the refund approval
- Provide details on refund amount: ${ {refund_amount:number} }
- Explain refund method: { {refund_method:text} }
- Indicate processing time: { {processing_time:text} }

{ {if_denied:checkbox} } If denied:
- Respectfully explain why the refund cannot be approved
- Reference specific policy points: { {denial_reason:text} }
- Offer alternative solutions: { {alternative_solution:text} }

5. NEXT STEPS
Clearly outline any actions the customer needs to take.

6. ADDITIONAL INFORMATION
{ {include_additional_info:checkbox} } Include this additional information:
{ {additional_info:text} }

7. APOLOGY
{ {include_apology:checkbox} } Include a sincere apology for the customer's experience.

8. RETENTION OFFER
{ {include_retention_offer:checkbox} } Include this retention offer:
{ {retention_offer:text} }

9. CLOSING
End with an appropriate closing that maintains the customer relationship.

ADDITIONAL NOTES:
{ {additional_instructions:text} }

Step 7: Test Your Customer Support Prompts

1. From the prompt details page, click Use on your comprehensive customer support response prompt
2. Fill in the parameter form with sample values:
   • Customer Name: "John Smith"
   • Product Name: "Premium Cloud Storage Plan"
   • Customer Since: "March 2024"
   • Subscription Type: "Business Pro"
   • Previous Interactions: "Two previous tickets about upload speed issues"
   • Issue Description: "Unable to access stored files after recent software update. Receives 'Error 404' when attempting to view documents uploaded last week."
   • Tone: "Empathetic but professional"
   • Priority Level: "High"
   • Toggle on "Include troubleshooting" and provide steps
   • Toggle on "Include follow-up" and select a date
3. Select a Peer to send the prompt to
4. Click Send to generate the customer support response

Step 8: Evaluate and Refine

1. Review the generated response from the Peer
2. Assess whether the response meets your expectations in terms of:
   • Tone and empathy
   • Clarity of troubleshooting steps
   • Professionalism and helpfulness
   • Overall structure and flow
3. Note any improvements you could make to the prompt
4. Edit your prompt to address any issues or enhance its effectiveness

Expected Outcome

By the end of this tutorial, you will have:

• Created a comprehensive customer support response prompt
• Developed additional specialized support prompts
• Tested your prompts to generate professional support responses
• Learned how to structure prompts for different support scenarios

Next Steps

To further enhance your customer support capabilities:

• Create product-specific support prompts with tailored troubleshooting steps
• Develop prompts for different support channels (email, chat, phone)
• Build prompts for specific customer segments or tiers
• Create prompts for handling sensitive situations (complaints, escalations)
• Share your support prompts with customer service teams to ensure consistency

Troubleshooting

Problem: Response tone doesn't match the requested tone. Solution: Provide more specific tone guidelines and examples of the desired tone in different situations.

Problem: Troubleshooting steps are too generic. Solution: Add more product-specific context and examples of effective troubleshooting steps.

Problem: Response doesn't adequately address the customer's emotional state. Solution: Add parameters for customer sentiment and provide guidance on how to respond to different emotional states.

Problem: Technical details are incorrect or outdated. Solution: Regularly update your prompts with current product information and troubleshooting procedures.