Chatbot

View All Docs
+

Getting Started (3)

+

Ai Configuration (5)

+

Woocommerce Integration (6)

+

Chatbot Implementation (3)

+

Customization (2)

+

Conversation Management (2)

+

Chatbot Menu Settings (5)

+

Performance And Optimization (1)

−

Security And Privacy (5)

Error Messages

Reading Time: 3 minutes

Overview

The WPiko Chatbot Error Messages section allows you to customize and manage the error messages displayed to users when various issues occur during chatbot interactions. Proper error message configuration helps maintain a professional user experience even when problems arise.

Accessing Error Messages Settings

  • Log in to your WordPress admin panel.

  • Navigate to the WPiko Chatbot menu in the sidebar.

  • Click on the “Error Messages” tab.

    • Understanding Error Types

    The plugin now uses a centralized error handling system that groups technical issues into user-friendly categories. This ensures users receive clear, consistent feedback without technical jargon.

    The available error categories are:

    • General Error: For unexpected issues that don’t fit other categories.

    • Connection Issues: When the server cannot be reached, the internet is down, or requests time out.

    • Server Busy: When the system is overloaded or rate limits are exceeded.

    • Authentication Failed: When API keys are invalid or sessions expire.

    • Feature Unavailable: specific features are restricted or disabled.

    Customizing Error Messages

    You can customize the messages for each of these categories. Technical errors (like “cURL error 28” or “504 Gateway Timeout”) are automatically mapped to these friendly messages.

    General Error (Default)

  • Default: “An unexpected error occurred. Please try again later.”

  • Use when: The system encounters an unknown issue or generic failure.

    • Connection Issues (Timeouts, Offline)

  • Default: “We are having trouble connecting to the server. Please check your internet connection.”

  • Use when: Network requests fail, time out, or the API is unreachable (e.g., cURL errors, 504 status).

    • Server Busy (Rate Limits, Overloaded)

  • Default: “The system is currently busy. Please try again in a few moments.”

  • Use when: OpenAI services are experiencing high traffic, or rate limits have been hit (e.g., 429 status).

    • Authentication Failed (Session Expired)

  • Default: “Your session has expired. Please refresh the page and try again.”

  • Use when: API keys are missing/incorrect, or access is denied (e.g., 401/403 status).

    • Feature Unavailable

  • Default: “This feature is currently unavailable.”

  • Use when: A restricted feature is accessed.

    • Best Practices for Error Messages

    When customizing error messages, follow these guidelines:

    Keep messages clear and concise.
    Use friendly, non-technical language.
    Provide a suggested action when possible.
    Avoid technical details in user-facing messages.
    Maintain consistency in tone across all messages.

    Error Message Guidelines

  • Length: Keep messages under 150 characters.

  • Tone: Maintain a helpful and reassuring tone.

  • Action: Include a clear next step or suggestion.

  • Clarity: Avoid technical jargon or complex terms.

  • Branding: Align message style with your brand voice.

    • Error Tracking and Monitoring

    The error message system:

  • Logs errors for administrator review.

  • Tracks error frequency in analytics.

  • Helps identify common issues.

  • Provides insights for system improvements.

    • Updating Error Messages

    To modify an error message:

  • Locate the specific error type.

  • Enter your custom message in the text field.

  • Ensure the message includes a suggested action.

  • Click “Save Error Messages” to apply changes.

    • Tips for Effective Error Management

  • Regularly review errors to identify patterns.

  • Update messages based on user feedback.

  • Keep backup copies of customized messages.

  • Monitor error frequencies in analytics.

  • Maintain consistency across all error messages.

    • By properly configuring and managing error messages, you can provide a better user experience even when issues occur, maintaining user trust and engagement with your chatbot.