Additional Business Logic Extensions

Below are some examples of possible business logic that can be applied to adjust the work processes to meet specific organization needs, using the SimpleChat SDK

  1. Workflow that sends the customer a link to a privacy statement
  2. Workflow that sends the customer a link to an article according to the More Info Link field in the selected customer's reply to a SimpleChat question
  3. Workflow that sends a request to type an identifier such as an e-mail and according to it locates and fills the contact (using a custom workflow step)
  4. Workflow that sends an OTP code to the customer (using a custom workflow step), waits for a reply from the customer and then compares it with the code that was sent
  5. Workflow to associate the activity with an existing open case or to create a new case (using a custom workflow step to locate the case), including defining the subject of the case from the subject of the conversation, the channel, or the customer's reply to a SimpleChat question
  6. Workflow to route a newly created conversation to a queue according to business specific logic such as whether or not the customer is a VIP (instead of the built-in mechanism)
  7. Workflow to fill a due date of a newly created conversation according to business specific logic. Controls how the conversation will be prioritized (neutralizes the built-in mechanism)
  8. Workflow that displays information from the system to the customer (information from the customer profile, from the related case, etc.)
  9. Workflow in status Waiting for Available Agent that sends the customer a message such as "All agents are currently busy, please wait ..."
  10. Workflow to close the conversation as Customer Didn't Respond if a customer did not answer and a threshold time to wait for a reply expired
  11. Workflow that sends the customer a request to send his location in Facebook Messenger channel, waits for the customer to send his location (received as text) and then runs logic to locate and send the nearest branches to the customer using a SendSelection API call
  12. Workflow when an outgoing built-in activity such as a letter or fax is created that generates a SimpleChat Conversation on a desired channel such as SMS with the same details. Can be used to distribute campaigns or quick campaigns using SimpleChat channels
  13. Workflow when a chat from a personal portal area is created that locates and fills the customer according to the ID passed to the Caller Name field (using a custom workflow step)
  14. Plugin when a conversation is created that identifies the customer using business specific logic instead of the built-in logic which is based on the customer profile.

Important: the custom logic must mark the Customer Identification field to disable the built-in logic, and the plugin must be implemented before step 100 in execution pipeline in order to run before the built-in logic

  1. Add a Divert to SMS button that is displayed for conversation in Chat channel and when clicked an SMS conversation with the same customer opens up. Allows continuation of conversation if customer was disconnected in the chat channel (i.e. if browser was closed)