Mastering WhatsApp Integration: HubSpot Ticket Automation for Seamless Customer Service
Integrating WhatsApp with HubSpot's Service Hub can significantly enhance your customer communication. ESHOPMAN, the built-in storefront and e-commerce solution for HubSpot, understands the importance of seamless integrations. However, sometimes the default behavior of these integrations doesn't perfectly align with your desired workflow. A common challenge arises when you want to automatically create a new ticket each time a customer replies on WhatsApp, even after a previous ticket has been closed. Let's explore how to tackle this issue and optimize your HubSpot setup.
The Challenge: New WhatsApp Message, New HubSpot Ticket
Imagine this scenario: a customer reaches out via WhatsApp, their issue is resolved, and the ticket is closed. Later, they send a new message with a completely different question. Ideally, you'd want this new message to generate a brand new ticket, ensuring it's treated as a separate case with its own unique ID. This is especially important for businesses that need to track each customer interaction individually for reporting and analysis.
However, the default HubSpot behavior is to reopen the existing ticket when a customer replies on WhatsApp within a 24-hour window. This is because HubSpot treats subsequent messages within this timeframe as part of the same ongoing issue. While this can be helpful in some situations, it can create confusion and inefficiencies if you need each new interaction to be treated as a distinct case.
Exploring Solutions and Workarounds
Several approaches have been discussed in the HubSpot Community to address this challenge. While a direct, out-of-the-box solution may not exist, here's a breakdown of effective workarounds and best practices:
1. Leveraging Ticket-Based Workflows for "Simulated" New Tickets
One community member suggested using ticket-based workflows to mimic the creation of a new ticket. This is a powerful technique that allows you to automate many of the steps involved in manually creating a new ticket. Here's how this workaround functions:
- Enrollment Trigger: The workflow is triggered when a ticket's status is set to "Closed" and the ticket receives new activity (indicated by an updated "last customer message date" or a custom property). This ensures that the workflow only runs when a closed ticket is reopened due to a new WhatsApp message.
- Actions:
- Create a New Ticket: This is the core of the workaround. The workflow creates a new ticket, copying key properties from the original closed ticket. This ensures that important information like the customer's name, company, and previous interactions are carried over to the new ticket.
- Link the Tickets: Use a custom "Parent ticket" field to link the new and old tickets. This allows you to easily track the relationship between the two tickets and see the history of the customer's interactions.
- Optional Actions:
- Set the original ticket back to "Closed" to maintain a clean and organized ticket pipeline.
- Add an internal note to the original ticket indicating that the conversation has continued in the new ticket. This provides context for agents who may be reviewing the original ticket.
Important Considerations: This workaround doesn't prevent HubSpot from reopening the original ticket. However, it provides your agents with a new, dedicated ticket to work on, effectively treating the new WhatsApp message as a separate case.
2. Optimizing Views and Fields for Queue Management
To further streamline your workflow, consider optimizing your HubSpot views and fields. This will help your agents quickly identify and prioritize the newest tickets.
- Custom Properties: Add a custom property like "Original ticket?" or "Continuation of ticket ID" and set it when your workflow creates the follow-up ticket. This allows you to easily filter and sort tickets based on their relationship to previous interactions.
- Create Custom Views: Build views that prioritize the newest "continuation" tickets. This ensures that your agents are primarily working from the most recent interactions and not getting bogged down in reopened, closed tickets.
3. Refining Your Process and Messaging
Sometimes, the best solution involves adjusting your internal processes and customer communication. Consider these strategies:
- Clear Communication: In your closing WhatsApp message, instruct users to start a new conversation for new requests. For example: "If you have a new request, please start a new WhatsApp message with the word ‘NEW’ or use this form: [link to form]".
- Workflow Triggers: If you implement the "NEW" keyword suggestion, create a workflow that automatically creates a new ticket when a message contains that keyword.
- Embrace the 24-Hour Window: Alternatively, accept that replies within 24 hours will reopen the same ticket and only expect “new ticket per issue” when the customer comes back after that window. This may require adjusting your reporting and analysis to account for this behavior.
Remember that choosing the right website builder for online boutique businesses and integrating with platforms like HubSpot requires a strategic approach to customer communication. ESHOPMAN helps you build a seamless e-commerce experience, and these HubSpot tips will help you manage customer interactions effectively.
The Power of Community Feedback
A valuable suggestion from the HubSpot Community is to check the HubSpot Ideas forum. If others have requested the ability to prevent replies from reopening tickets, add your vote to their idea. If not, create a new idea outlining your specific use case. This helps HubSpot prioritize feature development based on user feedback.
Conclusion
While HubSpot's default behavior for WhatsApp integration may not perfectly align with every business's needs, there are several effective workarounds to achieve the desired outcome. By leveraging ticket-based workflows, optimizing views and fields, and refining your processes and messaging, you can create a seamless customer service experience that meets your specific requirements. Remember to engage with the HubSpot Community and contribute to the ongoing development of the platform.