CRM Integration

  • Updated

Qiscus Omnichannel have several webhooks and API that can be used to integrate with any CRM of your choice. We provide service to integrate with CRM providers, you can contact our sales team for further discussion.

Should you choose to integrate by yourself, you can read some example scenarios below.

Kindly please note that the Webhooks and APIs are provided for Enterprise user. You can contact our sales team for upgrading to Enterprise.

The main idea of this integration is to have a real-time conversation in Qiscus Omnichannel and put the conversation data as tickets in CRM by utilising intermediary service. You can build your own server to implement the intermediary service or use some automation services like Zapier to name one (We provide Qiscus Omnichannel Zapier App to use). You can have a look at this diagram below on how it works,




Technically, there is a scenario which is usually used in this integration process, it makes use of provided custom webhooks such as: Custom Agent Allocation hook, Mark as Resolve hook and several API endpoints. This scenario is depicted in a communication diagram below,




From the diagram above, Custom Agent Allocation is used to set up a new ticket at CRM whenever a new room or conversation created in Qiscus Omnichannel via any channels. The process is helped by leveraging the Intermediary Service. Here’s the flow:

  • User has a chat with agent using provided channels, Qiscus Omnichannel will hook Intermediary Service to create a new user (if this is the first time conversation) and a new ticket when agent take the room in CRM. This will also trigger CRM to create and send an email to user’s email. So, email is an importance field to be used here. If you are using Qiscus widget, you can get it from email field. As for other channel you can append string or such, following user id.
  • Intermediary Service will pull some information from created ticket at CRM to be put in Qiscus Omnichannel room’s additional information sidebar. This could includes ticket id, location, a link to the ticket, etc. The idea is to populate ticket’s details in the Qiscus Omnichannel room.
  • Next, user and agent have a conversation.
  • When finished, agent mark the conversation as resolved. This will trigger Qiscus Omnichannel to hook Intermediary Service to update this specific ticket id in CRM to be closed.
  • If it’s necessary, conversation data could also be added when updating the ticket in CRM.

Here are some hooks and APIs you can use:

For an example on how you could implement it, please refer to our zapier example

Was this article helpful?



Article is closed for comments.