--- title: "Digital flows" slug: "digital-flows" description: "Create inbound digital interaction flows using an intuitive visual interaction flow editor that lets you place and configure interaction flow nodes and link them together according to your business processes." updated: 2025-09-09T10:41:02Z published: 2025-09-09T10:41:02Z canonical: "docs.voiso.com/digital-flows" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.voiso.com/llms.txt > Use this file to discover all available pages before exploring further. # Digital flows **Who should read this article**: Administrators, Supervisors Create inbound digital interaction flows using an intuitive visual interaction flow editor that lets you place and configure interaction flow nodes and link them together according to your business processes. ## Introduction The Flow Builder for Digital interactions enables you to create complex interaction flows and chatbots, incorporating messaging, response analysis, routing to agents and queues, conditional routing, and backend data retrieval. ![Flow Builder Overview Digital Channels](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Flow%20Builder%20Overview%20Digital%20Channels.png) Refer to the following articles for suggestion on getting started using the Flow Builder for inbound digital interaction flows: - [Build your own chatbot](/v1/docs/build-your-own-chatbot) (coming soon!) - [Business hour rules](/v1/docs/business-hour-rules) Important [Business hours](/v1/docs/inbound-flows#business-hours) in a flow use the contact center’s time zone as specified in [System Settings](/v1/docs/administration-system-settings). This may differ from the time zone set for individual users in their [profile](/v1/docs/users-users). When configuring business hours, be sure to account for any difference between the contact center time zone and your agents’ time zones. You can use the **[Conditions](/v1/docs/conditions)** node in **[Flow Builder](/v1/docs/inbound-flow-builder-overview)** to test the `start-time` of a message and [route it to](/v1/docs/flow-builder-route) different queues, agents, or other targets based on the time zone of the contact or agent. ## Nodes The following nodes are available in the digital interaction Flow Builder: | Icon | Node | Description | | --- | --- | --- | | ![Flow Builder Start Node](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Flow%20Builder%20Start%20Node.png) | [Start](/v1/docs/flow-builder-start) | The first node of every flow. When an interaction reaches the flow according to the business rules, such as day and time, the flow starts here. A flow may have only one Start node. | | ![Flow Builder Digital Message Node](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Flow%20Builder%20Digital%20Message%20Node.png) | [Message](/v1/docs/message) | Send an automated chat, WhatsApp, or Telegram message to the contact. This node leverages [variables](/v1/docs/flow-builder-variable-management) to personalize messages. | | ![Flow Builder HTTP Request Node](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Flow%20Builder%20HTTP%20Request%20Node.png) | [HTTP Request](/v1/docs/http-request) | Seamlessly integrate interaction flows with web services, such as CRMs, help desks, e-commerce software, websites, and other data sources. | | ![Flow%20Builder%20Condition%20Node](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Flow%20Builder%20Condition%20Node.png) | [Conditions](/v1/docs/conditions) | Routes interactions based on defined rules or criteria, enabling logic-driven decisions that determine how a contact’s request is handled. | | ![Flow Builder Route Node](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Flow%20Builder%20Route%20Node.png) | [Route](/v1/docs/flow-builder-route) | Direct the interaction to a Queue or Agent. | | ![Flow Builder End Node](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Flow%20Builder%20End%20Node.png) | [End](/v1/docs/flow-builder-end) | The last node of the flow if an interaction was not routed to any other node. Archives the interaction. A flow may contain multiple End nodes. | An area of the world that observes a uniform standard time for legal, commercial, and social purposes. Time zones commonly follow the boundaries between countries and their subdivisions instead of following evenly spaced divisions on the globe for the convenience of keeping a consistent time. A technology that places inbound voice calls and omnichannel interactions into a virtual waiting line in which contacts waits to be connected with an agent. Queues direct calls to the best available agent to reduce waiting times. Interactions with different priorities can be assigned to different queues. Queues can play music and other messages to callers waiting to connect to agents. Voiso queues also offer contacts a callback option if the wait time on the queue is long. A user who handles inbound and/or outbound interactions with contact. Sometimes referred to as a Customer Service Representative (CSR). The front-line employee who interacts directly with contacts and assists with tasks such as placing orders, resolving billing issues, and answering policy questions. ## Related - [Flow Builder Overview](/inbound-flow-builder-overview.md) - [Flows](/inbound-flows.md) - [Blog: Build your own chatbot](/build-your-own-chatbot.md) - [Create a simple chatbot](/creating-a-simple-chatbot.md)