Result delivery explained

Updated 1 month ago by Joost Rijlaarsdam

Question:

I've realized I'm a little in the dark about the processes you use to get the chat data to clients. Could you give me an overview please? Forgive me if I've got it wrong or been told the answers before but -

I understand that individual client employees can view conversations from within ChatShipper, but how are they alerted to the fact a lead is waiting for them?

CS: Correct, this can be done in multiple ways.

  1. A result can be emailed
  2. Result Data can be send to a Business System (eg CRM System) 

Question:  

Can a conversation/completed form be emailed to a client, or sent into a CRM system at any given point in the user journey?

CS: YES

Question:

If so, how does an operator say 'this conversation is now a lead'? What processes are/can be activated then?

CS: There are 2 options:

  1. A form (tagged with Lead) can be submitted
  2. A tag can be added to the conversation

 

FORM/Conversation DATA is then processed to (client specific) or webhook

Question:

Can a conversation/completed form be marked as a lead, and be sent to a holding area in CS for checking by a supervisor before being sent?

Yes, 2 options: 

  1. @mention a supervisor
  2. Assign lead to a supervisor channel

Question: 

Are the client's email/API authentication details kept inside the CS admin panel, so data is automatically transferred without agent intervention?

CS: Yes

Question:

If we wanted a lead to go straight into our own lead generation platform for processing there (as we do now), could we trigger the API upon a conversation being tagged as a lead?

CS: Yes


How did we do?