> ## Documentation Index
> Fetch the complete documentation index at: https://docs.osvi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Scheduled Conversations

> See every pending and past follow-up call or message before it goes out, and cancel anything not yet sent

**Scheduled**, under **Conversations** in the sidebar, lists every follow-up call or chat message your agents have scheduled — pending ones still waiting to fire, and past ones showing what happened.

<Note>
  Scheduled isn't publicly released yet. Until it is, contact [support@osvi.ai](mailto:support@osvi.ai) to have it enabled for your workspace.
</Note>

## Where scheduled items come from

An entry here can be created automatically by a [journey](/platform/journeys) — its **Send a message** or **Place a call** action — or by one of your agents' own automatic follow-up behavior, such as calling a customer back after a chat goes quiet. Where an item comes from a journey, its **Journey** column names it.

## What's on the list

| Column | Shows |
| - | - |
| **Fires** | When it's due (or was sent), both as a timestamp and relative to now |
| **Action** | **Call** or **Chat** |
| **Customer** | The phone number or contact name |
| **Journey** | The journey it's attributed to, if any |
| **Status** | `scheduled`, `dispatching`, `dispatched`, `cancelled`, `failed`, or `escalated` |
| **Outcome** | The cancel reason, the decision that produced it, or the last error — whichever applies |

Filter the list by status, by action type (**Phone call** / **Chat message**), or by customer phone number.

## Opening a row

Click any row for its full detail: when it fires, its decision mode (and, if the Journey Manager decides, what happens on failure), how many attempts and reschedules it's had, its chat session (for a chat message), any cancel reason or last error, and — for a deeper look — the fire-time decision, the decision snapshot taken when it was scheduled, and the payload it will dispatch with.

## Cancelling one

A row can only be cancelled while it's still **scheduled** — once the scheduler has claimed it (`dispatching` or later), cancelling is no longer possible and the button disappears; attempting it anyway reports that it's too late. There's no reschedule option — cancel it and let the agent or journey that created it schedule a new one if needed.