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

> ## Agent Instructions
> You are reading OnlyX Help: the OnlyX Help Center and the OnlyX developer documentation. OnlyX is an AI chatting and CRM platform for OnlyFans agencies. Its AI chatter is called Hugo in the app.
> Pages at the site root (for example /inbox/..., /hugo/..., /billing/...) are Help Center articles for agency owners, admins, chatters and creators who use the app at app.onlyx.ai. Words in bold are the exact button, menu and label names the app shows; keep them exactly as written. When these pages do not answer a question, the person can email support at support@onlyx.ai.
> Pages under /developers are the developer documentation. REST API base URL: https://api.onlyx.ai/v1 (authenticate with `Authorization: Bearer <API key>`; keys start with onx_sk_ and are created in app.onlyx.ai under Settings > API & MCP). MCP server: https://mcp.onlyx.ai/mcp (OAuth, or a Bearer API key). In the API the AI chatter is `ai` on the wire. Money is integer US cents in fields ending in Cents; timestamps are UTC ISO-8601.
> Rules for assistants acting on a user's behalf: discover ids with list calls and never invent them; before any call that reaches a real fan or the live OnlyFans account (sending a message, releasing a chat to the AI, turning AI on for a chat, resolving a hand-off, turning review mode off, changing the welcome message, creating a tracking link) show the user the exact content and get explicit confirmation; send every POST with an Idempotency-Key and reuse it on retry; never resend a message whose delivery status is unconfirmed; never ask a creator for her OnlyFans password or codes - she signs in herself through a connect link and the OnlyX Login app.

# See and cancel Hugo's scheduled follow-ups

> See the messages Hugo plans to send a fan on his own, and cancel one before it goes out.

<Badge color="blue">Owners, admins and chatters</Badge>

When Hugo plans to write to a fan on his own, the plan shows in the conversation. You can check each planned message before it goes out, and cancel it.

## Before you start

* You need an owner, admin or chatter account. A chatter sees only the conversations of their assigned creators.
* Hugo plans these messages himself, mostly through the creator's **AI Follow-ups**. See [AI Follow-ups: let Hugo write first](/hugo/ai-follow-ups). You cannot write or schedule a message here yourself.

## See what Hugo plans to send

Open the conversation in **Inbox**. Look at the strip over the message box, the one with a calendar icon. The strip shows only when Hugo has something planned for this fan.

Each chip in the strip is one message that Hugo sends by himself later. A chip shows:

* The kind of message, in the table that follows.
* When it goes out, for example "in \~42m" or "in \~3h". The time is approximate. "any moment" means it is due now.
* The words it sends, when Hugo has already written them. Otherwise, for example on an **Unopened PPV** reminder, the chip shows what the message is for, and Hugo writes the words when it goes out. The line is cut short: point at it to read all of it.

| Kind | What it is |
| - | - |
| **Check-in** | A nudge to a fan who went quiet. |
| **Follow-up** | A message that follows up on the conversation. |
| **Unopened PPV** | A reminder about a paid message from Hugo that the fan has not opened. |
| **Scheduled** | Any other planned message. |

<Frame caption="**1** A message Hugo plans to send · **2** The cross cancels it">
  <img className="block dark:hidden" src="https://mintcdn.com/onlyx/-OdGXx4TTCpw3fzi/images/help/inbox/scheduled-follow-ups/upcoming-strip-light.png?fit=max&auto=format&n=-OdGXx4TTCpw3fzi&q=85&s=8535becf0a9498dffd28e2b22c3ccc72" alt="The strip over the message box with a Follow-up chip and a Check-in chip, each with its time, its purpose and a cross to cancel it" width="1600" height="533" data-path="images/help/inbox/scheduled-follow-ups/upcoming-strip-light.png" />

  <img className="hidden dark:block" src="https://mintcdn.com/onlyx/-OdGXx4TTCpw3fzi/images/help/inbox/scheduled-follow-ups/upcoming-strip-dark.png?fit=max&auto=format&n=-OdGXx4TTCpw3fzi&q=85&s=d9a30a25529cda6fa8aa7397cda17eae" alt="The strip over the message box with a Follow-up chip and a Check-in chip, each with its time, its purpose and a cross to cancel it" width="1600" height="533" data-path="images/help/inbox/scheduled-follow-ups/upcoming-strip-dark.png" />
</Frame>

## Cancel a message before it goes out

<Steps>
  <Step title="Check what the cross does">
    Point at the cross at the end of the chip.

    The tooltip says what happens. "Cancel now — it also stands down by itself if he replies first" means that the message is cancelled anyway if the fan writes first. "Cancel — this will not send" shows when a reply from the fan does not stop the message.
  </Step>

  <Step title="Cancel the message">
    Click the cross.

    The chip disappears. The message does not go out. There is no confirmation, and you cannot undo it.
  </Step>
</Steps>

You can cancel several chips, one after the other.

## When planned messages stop by themselves

You do not always need to cancel. A planned message also stops when:

* The fan writes first. Most planned messages stand down when he replies.
* Someone on your team sends a message from the inbox. This cancels everything Hugo had planned for the conversation. It also takes the conversation over for 12 hours.
* Too much time passes. While a person has the conversation, or while something stops Hugo, planned messages do not go out. A message that waits too long expires, instead of going out late.

To see which planned messages went out and which stopped, open the fan panel and click **Activity**. See [Fan activity timeline](/inbox/fan-activity).

## If something goes wrong

<AccordionGroup>
  <Accordion title="&#x22;Too late — that one already went out&#x22;">
    The message was already on its way before your click reached OnlyX. It appears in the conversation as it goes out. After OnlyFans delivers it, you have 24 hours to unsend it. See [Copy, quote, hide, tag or unsend a message](/inbox/message-actions).
  </Accordion>

  <Accordion title="&#x22;Too late — it already expired&#x22; or &#x22;Too late — it already cancelled&#x22;">
    The message had already stopped by itself, so there was nothing to cancel. Nothing goes out.
  </Accordion>

  <Accordion title="&#x22;Could not cancel it&#x22;">
    The cancel did not reach OnlyX, so the message is still planned. Click the cross again.
  </Accordion>

  <Accordion title="I don't see the strip">
    Hugo has nothing planned for this fan right now. The strip shows only when there is at least one planned message.
  </Accordion>

  <Accordion title="Hugo sends too many follow-ups">
    The creator's **AI Follow-ups** tab sets how often Hugo writes to quiet fans. An owner or admin can change it there. See [AI Follow-ups: let Hugo write first](/hugo/ai-follow-ups).
  </Accordion>
</AccordionGroup>

## What's next

<Columns cols={2}>
  <Card title="AI Follow-ups: let Hugo write first" icon="bell-ring" href="/hugo/ai-follow-ups" horizontal />

  <Card title="Fan activity timeline" icon="activity" href="/inbox/fan-activity" horizontal />

  <Card title="Take over a conversation and give it back" icon="hand" href="/inbox/take-over-and-resume-hugo" horizontal />
</Columns>