How to analyse on Google Business Messages?
- Getting Started
- Bot Building
- Conversation Design
Code Step Integration Static Step Integration Shopify Integration SETU Integration Exotel Integration CIBIL integration Freshdesk KMS Integration PayU Integration Zendesk Guide Integration Twilio Integration Razorpay Integration LeadSquared Integration USU(Unymira) Integration Helo(VivaConnect) Integration Salesforce KMS Integration Stripe Integration PayPal Integration CleverTap Integration Fynd Integration HubSpot Integration Magento Integration WooCommerce Integration Microsoft Dynamics 365 Integration
- Agent Setup
- Analytics & Reporting
- Commerce Plus
- Troubleshooting Guides
- Release Notes
Intelligent Analytics by Haptik empowers teams to get a comprehensive overview of how the IVAs are performing. Get in-depth insights into how users interact with your IVAs, identify problem areas or features that can be improved, and also collect first-hand user feedback about your IVA experience in real-time. The user messages/conversations with historical data can help answer the toughest questions about users. Boost your IVA's conversations' success with this tool.
To know more about Haptik's Intelligent Analytics, read here.
Google Business Messages tracks key performance metrics to make sure the agent performs well.
Apart from Intelligent Analytics dashboard metrics, Google also shares the following metrics -
- CSAT: The Customer Satisfaction percentage.
- MRR: The Merchant Response Rate i.e. the frequency at which the agent(bot) responds back to the user.
If the agent performance is low, make sure your agent does the following -
- Check for all the webhooks and confirm if the messages are being sent to the user.
- Check for the fallback strategy if some information is missing.
- Reply to every message. Automated replies can help you address common questions.
- Be aware of users' conversation entry points and respond accordingly. For example, users coming from Google Maps are more likely interested in location-specific information like opening hours and stock checks.
- For location-based messages, route questions to the individuals best suited to respond to them.
- If a live agent isn't available, use automation to respond to the user. Let them know your agent's chat hours and how else they might reach someone (for example, a support phone number).
Make use of guidance messages, conversation starters to make the conversational journey easier for the user.
- Whenever possible, gather location and other data from messages you receive rather than asking for it.
- Don't request sensitive information (log-in credentials, banking/credit details, personal identification numbers).
- Only ask for data when it's required. Data overreach creates a bad user experience.
- When you need data, be clear about why and how you'll use it.
- Don't mark conversations as inactive. Communication over Business Messages is asynchronous, so users may not respond immediately.
- Don't follow up on unresponsive users. Users aren't disconnected after navigating away from the conversation.