Skip to content

Keyword-based flows

Keyword-started WhatsApp conversations, designed on a canvas

Conversation flows are designed around a start keyword. When a published flow matches inbound text, Vowels Connect runs the steps you connected on the canvas, from buttons and lists to media and a handoff to your team.

Illustrative example of the flow canvas. Previewing in the builder does not send WhatsApp messages.

The problem conversation flows solve

The problem

Customers often need the same guided answers: opening hours, order status, a menu of services. Answering each one by hand ties up the team, and a plain auto reply cannot ask follow-up questions.

What changes with Vowels Connect

A flow asks with buttons and lists, branches on the answer, sends the right text or media, and hands off to a person when needed. The customer starts it by sending a keyword you choose.

How it works

Design, preview, publish

  1. 1

    Set a start keyword

    Every flow begins with a keyword, such as “menu”. Published flows must each use a different keyword.

  2. 2

    Connect the steps

    Drag steps onto the canvas and connect them. Buttons and list options each get their own path.

  3. 3

    Preview safely

    Walk through the conversation in the builder. Preview never sends a WhatsApp message.

  4. 4

    Publish

    Publish the flow. From then on, an inbound message that matches the keyword starts it.

Key capabilities

Steps you can use in a flow

  • Text messages

    Send text at any step, with variables such as the customer name or an answer saved earlier in the flow.

  • Buttons and lists

    Offer reply buttons or a list of options. Each choice can lead to a different next step.

  • Images, video, and documents

    Send files from your media library, such as a brochure or a product video.

  • Payment QR

    Send a QR code image from your media library with a reference and payment instructions.

  • Conditions and delays

    Branch on an answer saved from a button or list, or on a field such as the customer name, or wait before the next step.

  • Handoff

    Pass the conversation to the shared inbox so a teammate can take over.

Use cases

Flows customers actually use

  • Main menu

    A “menu” keyword offers buttons for order status, store timings, and talking to a person.

  • Lead qualification

    Ask what the customer is interested in with a list, collect their answer, and hand off to sales with context.

  • Brochures and catalogues

    Send the right document or video based on the option a customer picks.

Part of the platform

How flows connect to the rest

  • Shared inbox receives handoffs and shows when a contact is inside a flow.

  • Automation handles event-triggered work; flows handle keyword-started conversations.

Conversation flow questions

Will editing a flow message my customers?

No. Preview stays in the builder. Only a published flow can send, and only after a matching keyword starts it.

What starts a flow?

A published start keyword. The inbound text has to match that keyword for the flow to start.

Can two flows use the same keyword?

No. Each published flow needs its own keyword, so a message always starts at most one flow.

What happens when a flow hands off?

The conversation continues in the shared inbox, where a teammate can reply.

Design your first conversation flow

Build and preview flows on any plan, then publish with a keyword from the Growth plan.