Skip to main content
Kemahiran.AI
BM
Open menu

Customer-Service Response Playbook Builder

Turn approved policies and service standards into reusable response patterns, authority limits and escalation paths.

Start here

Two ways to use this skill

Use it immediately without installation, or upload the package to save it as a reusable Gemini Skill.

Quick use

Use directly in Gemini

  1. Copy the complete instructions in one click.
  2. Paste them into a new Gemini conversation.
  3. Replace the variables and attach the required materials.

Reusable setup

Add to Gemini Skills

  1. Download the ZIP package below—do not unzip it.
  2. In Gemini, open Customize → Skills → Create → Upload.
  3. Select the ZIP, review its details, then create the Skill.
Download for Gemini Skills
Estimated time: 35 minutes

Package includes: README.md, SKILL.md, LICENSES.md

Prepare before starting

  • Approved service policies
  • Channels and authority limits
  • De-identified common scenarios

If the Skills menu is not yet available on your account, use Copy instructions. Gemini Skills availability may still vary by account type and staged rollout. Official Gemini Skills guide(opens in a new tab)

Complete guide

What you will get

A response playbook with principles, message structure, editable patterns, escalation triggers and a quality checklist constrained by real policies and authority limits.

Before you begin

Prepare approved return, refund, privacy and escalation policies, service standards, brand tone, channels and agent-authority limits. Use de-identified customer scenarios.

How to use it

  1. Identify the applicable policies and authority limits for each channel.
  2. Remove names, order numbers and unnecessary customer information.
  3. Copy the instruction below and complete the sample scenarios.
  4. Trial the patterns on common cases, boundary cases and escalation cases.
  5. Obtain policy-owner approval before team use.

Copyable instruction

Build a customer-service response playbook using only the policies, service standards, brand tone and authority limits I supply. If a relevant return, refund, privacy or escalation policy is missing, list the gap and stop; do not invent policy.

Approved policies: {{POLICIES}}
Channels: {{CHANNELS}}
Brand tone: {{TONE}}
Agent authority limits: {{AUTHORITY}}
Escalation path: {{ESCALATION}}
De-identified scenarios: {{SCENARIOS}}

Provide response principles, message structure, required/prohibited content, a scenario matrix, editable patterns by channel, escalation triggers and a QA checklist. Do not promise compensation, dates, outcomes or exceptions without authority. Do not include real customer data. Trial patterns on the scenarios and mark policy conflicts [POLICY OWNER REQUIRED].

Worked example

Synthetic example: a late order where policy allows only a delivery investigation, not an automatic refund. The response must acknowledge the issue, explain the investigation step and avoid promising an unapproved refund or resolution date.

Quality check

  • Every response follows the stated policies and authority limits.
  • The tone is clear and empathetic without admitting unverified liability.
  • Promises, compensation, dates and exceptions are not invented.
  • Escalation triggers and routes are explicit.

Limitations and responsible use

This playbook is not legal advice and does not replace organisational policy. The policy owner and legal or compliance team should review it where relevant. Do not enter real customer data into an unapproved tool.