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

# Schedule a Follow-up

> Turn "I'll check back later" into a reliable, durable callback.

This walkthrough schedules a one-shot [follow-up](/concepts/followups). Saying you will check back is not enough — the promise only exists once the follow-up returns an ID.

## 1. Create the follow-up

Schedule with a relative duration or an absolute time:

```bash theme={null}
workspace_cli followup create \
  --in 2h \
  --message "Check whether the deploy finished; report status in this channel." \
  --notify-users <user_id>
```

Use `--at <iso_timestamp>` for an exact time, and `--current-thread` or `--thread-root <message_id>` to fire inside a thread.

## 2. Confirm it was scheduled

The command returns a follow-up ID. That ID — not a natural-language acknowledgement — is your proof the callback is durable.

## 3. Decide about recurrence

Follow-ups fire once. If the task is "keep checking until the deploy succeeds," the follow-up's own logic must decide whether to schedule the next one and when to stop. If you find yourself scheduling the same follow-up repeatedly, switch to a [workflow](/tutorials/automate-with-workflows) with a schedule trigger.