--- title: Troubleshooting WhatsApp Default Response Issues description: "This troubleshooting guide helps you resolve common issues with WhatsApp Default Response Configuration. Follow the solutions provided to quickly identify and fix problems. **Common Issue Categories:** 1. Setup and Configuration Issues 2. Message Delivery Problems 3. Webhook-Related Issues 4. WABA…" url: "https://www.smsgatewaycenter.com/blog/kb/troubleshoot-whatsapp-default-response-issues/" updated: "2025-11-15" category: WhatsApp Business API / Default Response --- # Troubleshooting WhatsApp Default Response Issues This troubleshooting guide helps you resolve common issues with WhatsApp Default Response Configuration. Follow the solutions provided to quickly identify and fix problems. **Common Issue Categories:** 1. Setup and Configuration Issues 2. Message Delivery Problems 3. Webhook-Related Issues 4. WABA Connection Problems 5. Message Type and Content Issues **Issue 1: "No Waba connections found" Error** **Symptoms:** - Error message: "No Waba connections found" - Cannot proceed with default response setup - Empty WABA number dropdown **Causes:** - WhatsApp connections not configured - WABA connections inactive or expired - Account permissions issue **Solutions:** 1. **Verify WABA Connections:** - Navigate to **WhatsApp > Connections** - Ensure at least one active WABA connection exists - Check connection status is "Active" 2. **Reconfigure Connections:** - If no connections exist, set up a new WABA connection - Follow the WABA connection setup guide - Verify connection is properly authenticated 3. **Check Account Status:** - Verify WhatsApp account is activated - Check if account has proper permissions - Contact support if account is restricted 4. **Refresh and Retry:** - Clear browser cache - Refresh the page - Log out and log back in **Issue 2: "Selected Waba Number does not belong to you"** **Symptoms:** - Error when saving configuration - Cannot select certain WABA numbers - Validation error on form submission **Causes:** - Attempting to use WABA from different account - WABA connection ownership changed - Account permissions modified **Solutions:** 1. **Verify WABA Ownership:** - Check Connections page - Ensure WABA number is listed in your connections - Verify you're logged into correct account 2. **Re-authenticate Connection:** - Go to Connections page - Re-authenticate the WABA connection - Wait for connection to be verified 3. **Select Correct WABA:** - Use only WABA numbers from your connections list - Don't manually enter WABA numbers - Select from dropdown only **Issue 3: Default Response Not Being Sent** **Symptoms:** - Customer messages not receiving default response - Messages not delivered - No automatic response triggered **Causes:** - Default response not configured - Configuration inactive or deleted - Message delivery issues - WABA health problems **Solutions:** 1. **Verify Configuration Exists:** - Go to Manage page - Check if configuration exists for WABA number - Verify configuration is active 2. **Check Message Delivery:** - Verify WABA number is active - Check WABA health rating - Ensure customer is within 24-hour window 3. **Test Configuration:** - Send test message to WABA number - Monitor if default response is sent - Check message logs 4. **Review Configuration:** - Edit configuration to verify settings - Check message content is valid - Ensure message type is supported 5. **Check System Status:** - Verify WhatsApp API is operational - Check for system maintenance - Review platform status page **Issue 4: Webhook Not Receiving Requests** **Symptoms:** - Webhook URL configured but no requests received - No data logged in webhook endpoint - Webhook test fails **Causes:** - Invalid webhook URL - Webhook endpoint not accessible - Authentication failures - Server configuration issues **Solutions:** 1. **Verify Webhook URL:** - Check URL format is correct (https://) - Ensure URL is publicly accessible - Test URL manually with POST request 2. **Check Server Configuration:** - Verify server accepts POST requests - Check firewall allows incoming connections - Ensure SSL certificate is valid 3. **Test Webhook Endpoint:** - Use Postman or cURL to test - Send test POST request - Verify endpoint responds correctly 4. **Check Authentication:** - Verify API keys/tokens are correct - Check authentication headers - Review server access logs 5. **Monitor Webhook Logs:** - Enable detailed logging - Check for error messages - Review webhook request history **Issue 5: Message Type Fields Not Appearing** **Symptoms:** - After selecting message type, fields don't appear - Form remains empty - Cannot enter message content **Causes:** - JavaScript disabled or blocked - Page not fully loaded - Browser compatibility issues - Cache problems **Solutions:** 1. **Enable JavaScript:** - Ensure JavaScript is enabled in browser - Check browser settings - Disable JavaScript blockers 2. **Clear Browser Cache:** - Clear cache and cookies - Hard refresh page (Ctrl+F5 or Cmd+Shift+R) - Try incognito/private mode 3. **Check Browser Compatibility:** - Use supported browsers (Chrome, Firefox, Safari, Edge) - Update browser to latest version - Disable browser extensions temporarily 4. **Wait for Page Load:** - Ensure page is fully loaded - Wait for all scripts to load - Check browser console for errors 5. **Try Different Browser:** - Test in different browser - Verify issue is browser-specific - Report browser-specific bugs **Issue 6: Preview Not Updating** **Symptoms:** - Preview panel shows old content - Changes not reflected in preview - Preview stuck on loading **Causes:** - JavaScript errors - Cache issues - Network problems - Preview service issues **Solutions:** 1. **Refresh Preview:** - Make a small change to trigger update - Click outside and back into field - Save draft and reload 2. **Clear Cache:** - Clear browser cache - Hard refresh page - Clear application cache 3. **Check Console:** - Open browser developer console - Look for JavaScript errors - Fix or report errors found 4. **Verify Network:** - Check internet connection - Ensure no network restrictions - Try different network **Issue 7: Configuration Not Saving** **Symptoms:** - Click Save but nothing happens - Form validation errors - Success message but changes not saved **Causes:** - Validation errors - Required fields missing - Network issues - Session timeout **Solutions:** 1. **Check Validation Errors:** - Review form for red error messages - Fill all required fields - Fix format errors 2. **Verify Required Fields:** - WABA Number selected - Message Type selected - Message content provided - All mandatory fields filled 3. **Check Network:** - Verify internet connection - Check for network timeouts - Retry after network stabilizes 4. **Session Issues:** - Log out and log back in - Clear session data - Use fresh browser session **Issue 8: "Your WhatsApp account is not yet active"** **Symptoms:** - Cannot access default response configuration - Error message about inactive account - Access denied **Causes:** - WhatsApp account not activated - Account suspended - Permission issues **Solutions:** 1. **Activate WhatsApp Account:** - Complete WhatsApp account setup - Verify account activation - Contact support for activation 2. **Check Account Status:** - Review account status in dashboard - Verify account is not suspended - Check for account restrictions 3. **Contact Support:** - If account should be active, contact support - Provide account details - Request account activation review **Prevention Best Practices** 1. **Regular Monitoring:** - Check configurations regularly - Monitor message delivery - Review error logs 2. **Testing:** - Test configurations before going live - Verify webhooks are working - Check message delivery 3. **Documentation:** - Document configuration settings - Keep webhook URLs recorded - Maintain change logs 4. **Backup:** - Export configuration data - Keep backups of important settings - Document configuration purposes **Getting Additional Help** If you've tried all solutions and issues persist: 1. **Check Documentation:** - Review other KB articles - Search knowledge base - Check platform documentation 2. **Contact Support:** - Provide detailed error messages - Include configuration details - Share screenshots if possible 3. **Report Bugs:** - Document steps to reproduce - Note browser and system details - Report through support channel **Next Steps:** After resolving issues, review our "Best Practices for Default Response Configuration" guide to optimize your setup. ### More Related Articles - [What is WhatsApp Default Response Configuration and Why is it Mandatory?](https://www.smsgatewaycenter.com/blog/kb/whatsapp-default-response-configuration-introduction/) - [How to Set Up WhatsApp Default Response Configuration](https://www.smsgatewaycenter.com/blog/kb/how-to-setup-whatsapp-default-response-configuration/) - [WhatsApp Default Response Message Types: Complete Guide](https://www.smsgatewaycenter.com/blog/kb/whatsapp-default-response-message-types-guide/) Found this useful?[Add as Preferred Source on Google](https://www.google.com/preferences/source?q=smsgatewaycenter.com)