Gladly: Mastering Customer Service Interactions
Gladly is a customer service platform designed to streamline communication across various channels, ensuring efficient and consistent support by standardizing agent responses and categorizing interactions for trend analysis.
Core Principles
- MOCHA: Every contact, every conversation, every customer is the overarching principle for all interactions.
- Channel-Specific Protocols: Each communication channel (phone, email, chat, SMS) has distinct rules for handling inquiries and routing.
- Standardized Answers: Utilize pre-written answers to ensure consistency and efficiency in responses, especially for common inquiries like gift messages.
- Topic Categorization: Assign topics to every conversation to identify trends and areas for improvement in customer service.
Action Steps
- Review customer conversations from the past to understand their history.
- Assign conversations to an inbox, not directly to a user, for better workflow management.
- Ensure every phone call has a note and every conversation has a topic.
- When creating a task, assign it to an inbox and clearly state what needs to be done or what was promised.
- When working a task, add a note detailing completion and mark it as complete only when 100% finished.
- Pick the most applicable topic for each conversation, and assign a second or third topic if necessary.
Key Terms
- Gladly: A customer service platform used by Godiva for managing customer interactions across various channels.
- MOCHA: An acronym representing the core principle: Every contact, every conversation, every customer.
- Sidekick: A feature within Gladly that powers chat self-help for customers.
- Inbox: A designated location within Gladly where conversations or tasks are assigned for agents to manage.
- Warm Transfer: A method of transferring a call where the agent briefly explains the situation to the receiving agent before handing over the call.
Pro Tips
- For chat callouts, if a customer is navigating to different pages, do not initiate a chat to avoid annoyance; instead, let them initiate.
- When handling phone calls, pause the Gladly recording when taking credit card information to ensure PCI compliance.
- For emails, if more than two emails are exchanged on the same topic, offer to call the customer to assist them to resolve the issue more efficiently.
- When transferring a live call to Brand support, always perform a WARM TRANSFER to the branch support concierge.
Pitfalls to Avoid
- Closing a task before it is 100% finished leads to incomplete resolution and potential customer dissatisfaction.
- Not pausing the Gladly recording when taking credit card information poses a security risk and violates PCI compliance.
- Promising a callback from Godiva at a specific time without certainty can lead to unmet expectations and customer frustration.
Myth vs Reality
- All customer calls are recorded within the Gladly profile.: Brand support calls for IVR options 4 & 5 are NOT recorded in a Gladly profile; they are handled by the Stafford telephony system.
Real World Examples
- A customer asks about adding a complimentary gift message during checkout.: Agents should use the pre-written 'Adding A Gift Message' answer, which guides the customer to the correct section on the checkout page and specifies message limitations (five lines, 35 characters/spaces per line, no special characters or emojis).
- An order needs a credit issued because the customer forgot to enter an FS code.: Create a task assigned to the 'ecom - orders needing service' inbox, with a due date of the day after the order should ship. Include details like the order number, ship date, amount of credit, and the reason for the credit.
Statistics
- Chat Timeout (No Activity): 10 minutes
- Maximum Chat Duration: 20 minutes
- Brand Support Hours of Operation (HOO): Monday - Friday from 9:00 am – 5:00 pm EST
Timeline
- 1926: Godiva founded in Belgium.
People
- Mary Mikus: Agent/User associated with Gladly answer reviews and task completions.
- Antoinette: Agent involved in customer interactions and task routing.
Related cheat sheets
More like this