# Build a sales and support menu

Ask one clear question and route customers to two different replies using a real multiple-choice node.

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Active Lines | 2 | 5 | 15 | Unlimited |
| Active workflows | 3 | 10 | 45 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## What this workflow does

A fresh customer conversation starts a two-choice question: **Sales** or **Support**. Each answer follows its own branch to a different Send Text Message node.

The example uses exactly three ordinary nodes after **New Chat Created**. It does not assign a human agent or update a status automatically.

## Configure the menu

Import the example at the end of this guide. Open **helpMenu** and edit the question and answer options. The number and labels of the answer options determine the branches.

Open **salesReply** and **supportReply** and replace the text with the response your business actually wants to send. Keep it clear whether the customer should reply, follow a link, or wait for your team.

## Test both paths

1. Save and assign the workflow to a test Line.
2. Enable it and start a fresh chat.
3. Choose Sales and verify the sales response.
4. Start another fresh chat and choose Support.
5. Check that only the selected branch sends a response.

## Extend it

Add Receive Message to collect the customer’s details. For a human handoff, use a team-supported Line with **Private AI mode** disabled, apply the intended conversation status, and make sure other workflows respect that status. A status does not make a [private AI conversation](/channels/private-ai/) visible to human agents.

If you add another answer option, connect its new branch and test it. If you remove or reorder options, review the connected paths rather than assuming the old mapping is still correct.


## Copyable workflow

https://docs.chatigram.com/examples/support-menu.json