FORKING AUDIENCE:
We want to serve a different chat bot experience based on whether the user is logged in our out. How do you recommend doing this?
Two separate project IDs? If so, do you have recommendations for switching between project IDs at runtime for a Single Page Application?
One project ID with custom variables passed in? If so, will Voiceflow be able to receive updates to such variables at runtime, and interrupt + reroute any conversation logic based on the variable changes? (again, because Single Page Application)
4 Replies
From my engineer: "It's just a question of two different experiences/projects: do they recommend one or multiple projects, and what mechanism do they recommend to switch between experiences/projects at runtime
(at runtime on a SPA)
Single Page Application
If they come back and say, call .destroy() and then .load() again on the new project, I may have a specific follow up question to ask"
What would be the difference in experience for a user who is logged in or not?
We have trained the logged out agent to have a few back and forth interactions about the course material before providing an opportunity to sign up for membership. So a sales pitch is involved. The logged in version has no sales pitch because a person is already a member at that point.
I'd like to set up conditional logic to recognize when a user is logged in or logged out and then deliver them a different agent for that page depending on logged in or logged out.
@Joe Valley Thanks for clarifying. In this case you just need to pass some kind of identifier through the widget and reference that against your db to then direct your flow using business logic. Unless you already have that data associated with the user in your db which can provide a true or false (or whatever you use) response, then you can just pass that into your flow and do a simple true or false logic. Where db are you using for your users?