# How workflows decide what happens to calls and messages

> Workflows alone decide what happens. A call runs one workflow for its number. A message runs every matching workflow, then the default.

Source: https://useline.io/help/workflows/how-workflows-work  
Section: Workflows  
Last updated: 2026-11-05

A workflow decides what happens to each call and message that comes into Line. Nothing else routes a call or a message. Your agent, your hours and your team all act through workflow steps.

## The parts of a workflow

A workflow has one trigger and a set of steps.

| Trigger | Starts when |
|---------|-------------|
| **Call received** | A call comes in to a number that the trigger lists. |
| **Message received** | An SMS, WhatsApp, Web Chat or email message comes in. |
| **Web Chat abandoned** | A visitor leaves a Web Chat before the question is answered. |
| **Agent ended a conversation** | An agent ends a conversation. The workflow gets the summary and the outcome. |

Steps check a condition, such as a **Time Rule**, or do an action, such as **Ring Members/Groups** or **Agent**.

## Calls run one workflow

Each number has exactly one live call workflow.

- If an enabled, published custom call workflow lists the number, that workflow answers.
- If none lists the number, the number's default call workflow answers. It rings your team, sends a missed-call SMS, then takes a voicemail.
- If two enabled call workflows list the same number, the one changed last answers.

If the live workflow fails, the default call workflow runs. If that also fails, the call goes to voicemail.

## Messages run every matching workflow

1. Line saves the message in the Inbox first.
2. Line runs every enabled message workflow whose trigger matches the message, oldest first.
3. The first workflow that reaches a reply sends the reply. Later workflows do not send a second reply, but their other steps, such as an email, still run.
4. If no custom workflow sends a reply, the default message workflow for that number, widget or inbox runs last.

Every number, widget and inbox starts with a default message workflow. It has only a trigger, so messages wait in the Inbox for a person. To make your agent reply, add an **Agent** step.

## Hours and availability

Business hours change what happens only through a **Time Rule** step. Team availability changes what happens only through a **Team Availability** step. **Ring Members/Groups** rings only people whose status is Available.

## See which workflow handles a channel

1. Open **Channels**.
2. Select a channel type, then select a number, inbox or widget.
3. Find **Handled by**. It lists the workflows in the order that they run.

## Who can change workflows

Every member can view workflows and their runs. Only an **Owner** or an **Admin** can create, edit, publish, enable, disable or delete a workflow. You build workflows on the web app only. The mobile app does not edit workflows.

## Plan limits

| Plan | Custom workflows |
|------|------------------|
| Starter | 3 |
| Pro | 10 |
| Business | No limit |

Default workflows do not count towards the limit.

## Related articles

- [Build and publish a workflow](https://useline.io/help/workflows/build-a-workflow.md): In Workflows, select New workflow, choose a template, set the trigger and steps, fix every issue, then select Publish.
- [Set up what happens when someone calls](https://useline.io/help/workflows/call-workflows.md): A call workflow starts with Call received and lists your numbers. It rings your team, forwards the call, runs your agent or takes a voicemail.
- [Set up what happens when a message comes in](https://useline.io/help/workflows/message-workflows.md): A message workflow starts with Message received. Filter by channel, endpoint, keywords or contact, then add an Agent step, an email or a text.
- [Route by business hours with a Time Rule](https://useline.io/help/workflows/time-rule.md): Add a Time Rule step to a workflow. It splits calls and messages into Open hours and Outside hours, using an hours set from Settings > Hours.