Developer Docs | Kommunicate

Developer Docs | Kommunicate

  • Book a Demo
  • Try For Free
  • Docs

›Web

Web

  • Installation
  • CMS Installation
  • Authentication
  • Conversation
  • Conversation Assignment
  • Customization
  • Localization
  • Logout
  • Troubleshooting

Android

  • Installation
  • Authentication
  • Push Notification
  • Conversation
  • Customization
  • Localization
  • Logout
  • Migration
  • Troubleshooting

iOS

  • Installation
  • Authentication
  • Push Notification
  • Conversation
  • Customization
  • Configuration
  • Localization
  • Logout
  • Troubleshooting

React Native

  • Installation
  • Authentication
  • Push Notification
  • Conversation
  • Customization
  • Logout
  • Troubleshooting

Flutter

  • Installation
  • Authentication
  • Customization
  • Conversation
  • Push Notification
  • Localization
  • Troubleshooting

Ionic/Cordova/Phonegap

  • Installation
  • Authentication
  • Push Notification
  • Conversation
  • Customization
  • Localization
  • Logout
  • Resolving Errors

Ionic/Capacitor

  • Installation
  • Authentication
  • Push notification
  • Customization

Rich Messages

  • How To Use
  • Types of Rich Messages

Bots

  • Bot setup
  • Dialogflow Integration
  • Lex Integration
  • Kompose Bot Builder
  • IBM Watson Integration
  • Custom Bot Integration
  • Import Kompose Bot
  • Bot Samples

Integrations

  • Zapier
  • WhatsApp
  • WhatsApp 360Dialog
  • WhatsApp Twilio
  • WhatsApp Cloud API

Platform APIs

  • Authentication
  • Endpoints

Dashboard Features

  • Analytics
  • Conversations
  • Users
  • Bot Integration
  • Helpcenter
  • Campaign Messaging
  • Settings

Configuration

  • Single Sign On (SSO) Setup
  • Webhooks
  • Access Token URL
  • Email Fallback

Web Troubleshooting

Bot or agent responses are not updating real time on chat widget

If you are not receiving replies from the bot or the agent in the chat widget, then it might be due to one of the following reasons:

  1. HTML file is opened on the browser from the file system directly. Real time updates require websocket, due to cross origin security policy, websocket doesn't work when html file is opened directly from the file system.

This error can be verified by looking into the browser's console. Check if there are any errors similar to the following:

Access to XMLHttpRequest at 'https://socket.kommunicate.io/stomp/info?t=1547050628459' from origin 'null' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.

To resolve it, serve the html page through the web server such as Apache, Jekyll, Tomcat, Python, Node etc.

Example : How to serve the html file via web server ?

Solution :

Step-1 Open Terminal.

Step-2 Change the current working directory to the directory where HTML file is present.

Step-3 If you are using Python 2 type command python -m SimpleHTTPServer 8000 
for Python 3 python -m http.server 8000.

Open your web browser and enter http://localhost:8000 to run the demo.

  1. Verify if you are running it within a firewall network. Kommunicate uses port 443 for establishing a websocket connection. If your network has blocked websocket protocol or port 443, then Kommunicate web plugin will not be able to establish websocket connection with Kommunicate's MQTT based real time update service.

This error can be verified by looking into the browser's console. Check if there are any errors similar to the following:

https://socket.kommunicate.io/stomp/info?t=1547037843186 net::ERR_CONNECTION_REFUSED

Error in channel notification. Whoops! Lost connection to https://socket.kommunicate.io/stomp

To resolve it, check with your network team for allowing websocket protocol and port 443.

  1. If bot configured through dialogflow is not responding, then verify if the service account private key file uploaded to Kommunicate is correct.

Conversations are getting assigned to human agent instead of bot

  • Verify if you have configured 'Bot Routing Rules' from Settings -> Conversation Rules
  • Select the respective bot to answer queries under "Routing rules for bots".
  • If you have recently modified the 'Bot Routing Rules' then test the new behavior initiating new conversations. Please note that new changes will not be reflected on already created conversations.

Every time when a user navigates to different webpages, a new user with a new conversation gets created

  • If the option "Remove chat session history on page refresh" from Settings -> CHAT WIDGET -> Customization is selected then on every page load, a new user will be created. It’s irrespective of the page, where the webiste is getting reloaded when the user navigate.

To resolve this issue, uncheck the option "Remove chat session history on page refresh" and proceed with "Remove chat widget after a set period time"

Chat widget is not optimized for mobile view

  • Check if you have added the viewport <meta> tag to your website.
  • The tag sets the width of the page to follow the screen-width of the device (which will vary on every device)

You can copy the following snippet and paste it in the <head> tag of your website to make the chat widget responsive.

<meta name="viewport" content="width=device-width, initial-scale=1">

Sound notification is not working

Sometimes when a new chat opens up or a new message is received on the chat, you do not get any sound. It might be a common issue. However, it can be handled by your browser settings. Let's dive into it:

- For Google Chrome: - Click on the Lock Sign which is available near the URL and then click on site settings.

Google Chrome

Google Chrome

Search for sound and change it to allow.

Google Chrome

- For Safari: - When your browser is opened, clic on safari then go to Settings and Allow the auto-play.

Safari

Safari

- For Mircosoft Edge: - Click on the lock sign.

Edge

Settings will be opened. Now, search for autoplay and Allow it.

Edge

Edge

- For Firefox: - Click on menu (three horizontal lines icon) and then click on settings. Go to Privacy and Security and search for Autoplay.

Firefox

Allow Audio and video.

Firefox

If none of the above helps, drop us a mail at support@kommunicate.io

← LogoutInstallation →
  • Bot or agent responses are not updating real time on chat widget
  • Conversations are getting assigned to human agent instead of bot
  • Every time when a user navigates to different webpages, a new user with a new conversation gets created
  • Chat widget is not optimized for mobile view
  • Sound notification is not working

Ready to automate more than 80% of your customer support?

Try for Free
  • support@kommunicate.io
  • United States
    (+1) (310) 402-2374
  • India
    (+91) 974-057-0196
  • Docs
    • Web
    • Android
    • iOS
    • Ionic/Phonegap
    • React Native
    • Flutter
  • Product
    • Kompose Chatbot Builder
    • Live Chat
    • Integrations
    • Helpcenter
    • Dialogflow Integration
    • Features
    • Pricing and FAQs
    • Get Demo
  • Resources
    • Chatbots Templates
    • Blog
    • Kommunity
    • Support Metrics
    • Free SaaS Icons
    • ROI Calculator
    • Comparison
  • Company
    • About Us
    • Partner Program
    • Terms of Service
    • Privacy Policy
    • Jobs
    • SLA
    • DPA
  • Support
    • Knowledge Base
    • Docs
    • Stack Overflow
    • API Status
    • Contact Us
Software Advice Frontrunners for Live Chat Mar-22crozdesk badgeCapterra Shortlist for Live Chat Mar-22GetApp Category Leaders for Live Chat Mar-22GDPR compliant - GDPR Copy 12Created with Sketch.COMPLIANTG2 reviews badge
Copyright © 2023 Kommunicate.io