Response Path of Logged In User

#1

Hello,

I’m implement FlowXO to our e-commerce platform.

And I would like to display the chat log for our logged in user.
Let’s say when our user logged into our platform they will see their chat history whether he uses on another computer.

Technically, I think it is about Response Path to route back to our user,
but I cloud not find the way how to force set response path for our logged in user or another way to let FlowXO knows that it is the same person whether he uses our platform on difference device or web browser.

Could anyone help me to suggest a solution?

Thank you in advance.

(Karen Barker) #2

Hi there,

Unfortunately using the Web Messenger, there is no way to keep state from 1 device to another as we have no way to link visitors on different machines, locations etc to each other.

You are correct that it would be the response path that you would need to update. However, the Web Messenger has no way of interacting with/getting data from the page it is installed on. As such I can’t think of any way currently you would be able to relate a User ID to a Response Path or even know the User ID within the Web Messenger.

The good news, however, is that we are planning an update for the web messenger. This will include a publically accessible API and as part of this you will be able to send ref data when opening the web messenger at this point it might be possible.

On the other platforms - facebook messenger, slack, telegram then state will be kept from one device to another as long as the user logs into those platforms using the same user name/password.

#3

Hello,

I’m looking forward to the publically accessible API since my customers complain about the chat log,
an my team spent time for 3 days for researching and it still no way.

Cloud you tell rough estimation for the date of updating?

#4

Hi
… in the meanwhile… I suggest saving this problem with traditional systems: requesting username and password to the clients (in the flow) which could be checked with a connected MySQL database o Google Sheet.

Improving this: Clients use to forget their passwords, but they never forget their mobile number, therefore you could also try asking for client mobile number (acting as user name) and sending to it an SMS with a random password (this is a common method in banking when you want to transfer money) which should be posted back to the flow by the client in order to continue.

Chat history could have been previously stored in a database, rescued, and (some way) resumed by the bot after a satisfactory check in of that client.
Good luck