Skip to main content

​
What are Emplorium Flows?

A Flow is a sequence of modular blocks that define a conversational path. You design these paths using an intuitive drag-and-drop builder, allowing for complex logic and personalized visitor experiences. Flows are typically initiated by a Start Condition (similar to a Trigger) and then progress through various Action Blocks based on visitor input or predefined logic.
Flows Example Pn

​
Building a Flow: Start Conditions & Modular Blocks

Creating a Flow involves two main components: defining when the Flow should begin and assembling the series of actions and questions it will execute.

​
1. Start Conditions: Initiating a Flow

A Flow can be initiated by various visitor actions or environmental factors. These conditions determine when your automated journey begins.
  • When Visitor Lands on a Page: Starts when a visitor arrives on a specified URL.
  • When Visitor is Online: Triggers if the visitor is actively Browse your site.
  • When Visitor Sends a Message: Initiates the Flow when the visitor sends any message in the chat.
  • On Scheduled Days: Allows Flows to run on specific days of the week.
  • From a Specific IP Range: Targets visitors from a defined IP address range.
  • For Identified Visitors: Triggers for visitors whose profiles are known.
  • For Known Emails: Initiates for visitors whose email addresses are recorded.
  • For Verified Phone Numbers: Starts for visitors with known phone numbers.
  • Based on Visitor Country: Triggers based on the visitor’s detected country.
  • For Specific Browsers: Targets users based on their web browser (e.g., Chrome, Firefox).
  • For Certain Browser Versions: Targets users with specific browser versions.
  • For Specific Operating Systems: Triggers for users on particular operating systems (e.g., Windows, macOS).
  • Based on Device Type: Initiates for users on Desktop, Mobile, or Tablet devices.
  • When Agents Are Online: Triggers if at least one agent is available.
  • When Agents Are Offline: Triggers if no agents are currently online.
Start conditions for Flows are very similar to those for Triggers. You can think of a Flow as a more advanced, multi-step “action” that a simple Trigger might initiate.
Flows Conditions Pn

​
2. Modular Blocks: Designing the Conversation Path

Once a Flow starts, you connect various modular blocks to create the desired user journey. These blocks represent different actions or interactions.
This block allows the Flow to send a message to the visitor.Options: Text, rich reply (with buttons), image, or quick reply options.
This block sends a message and then pauses the Flow, waiting for a user reply to proceed. Useful for gathering specific input.
Present a predefined form to the visitor. This can be used to set or update a profile field based on the collected conversation data.
Directs the conversation to Aura AI, allowing the AI agent to handle the next set of user queries based on its knowledge.
Push user-provided data or other information collected in the Flow to an external system via an API call (e.g., update a CRM record). Requires a configured Data Update endpoint.
Create conditional branches in your Flow using AND/OR operators. This allows the Flow to take different paths based on visitor responses, profile data, or other criteria.
Automatically apply specific labels or tags to the chat based on user behavior or the outcome of the Flow. Useful for segmentation and reporting.
Routes the conversation to a human agent when certain conditions are met (e.g., if the user asks for human help, or if the Flow can’t resolve the issue).
Cleanly stops the Flow once a desired outcome is met or the conversation concludes.
Flows Example Pn

​
Designing Effective Flows: Use Cases & Strategy

Flows empower you to automate complex interactions that go beyond simple trigger-response mechanisms.

​
Common Use Cases for Flows

Lead Qualification & Nurturing

Build a multi-step conversation to ask qualifying questions (e.g., company size, pain points), collect contact info via forms, and then assign qualified leads to sales.

Automated Support Triage

Guide users through a series of questions to identify their issue, offer relevant KBA articles, and escalate to the correct department or agent if self-service isn’t sufficient.

Feedback Collection

After a support interaction or a successful purchase, trigger a Flow to ask for feedback, collect ratings, and identify areas for improvement.

Appointment Scheduling

Combined with Data Requests/Updates) Allow users to book meetings or appointments directly within the chat by collecting necessary details and updating an external calendar system.

Customer Onboarding & Feature Adoption

Create interactive tours or mini-onboarding sequences. Ask users about their goals, provide quick tips, and direct them to relevant features or documentation.

​
Managing & Testing Flows

  • Status Toggle: Easily activate or deactivate Flows without deleting them.
  • Flow Performance Analytics (Coming Soon): Gain insights into how your Flows are performing, including completion rates, drop-off points, and escalation rates.
  • Virtual Visitor: Thoroughly test your Flows in a sandbox environment using the Virtual Visitor to ensure they behave as expected before going live. This is crucial for complex flows.ù
We’ll add flow testing within the same page soon!

​
Best Practices for Building Robust Flows

Follow these guidelines to create effective and user-friendly Flows:
1

Map Out the Journey First

Before building, sketch out the user’s journey, decision points, and desired outcomes. This helps avoid getting lost in the visual builder.
2

Keep it Concise & Conversational

Design messages that are easy to read and natural. Avoid overly long messages or too many questions at once.
3

Provide Clear Options

When using “Ask a Question” or rich replies, give users clear, easy-to-understand options to guide them.
4

Design for Fallback & Escalation

Always include Escalate to Agent blocks at points where the Flow might not be able to resolve an issue, ensuring a smooth handoff.
5

Utilize Branch Logic Smartly

Use Branch Logic to personalize paths based on visitor input or known profile data, making the Flow more relevant.
6

Test Extensively with Virtual Visitor

Simulate every possible path and user input. Test edge cases, incorrect inputs, and the escalation process to catch errors early.
7

Iterate & Optimize (with Analytics)

Once Flow performance analytics are available, use them to identify bottlenecks, optimize conversation paths, and improve conversion rates.

​
Next Steps

⌘I