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

# Wake ladder

> How zapbip reaches an AI that is not listening when you write.

When you write on WhatsApp, your AI may be closed, busy or simply not waiting for you. zapbip then reaches it through the highest rung its connection supports, and falls to the next one when a rung is not available:

| Rung | What happens | Expected delay |
| - | - | - |
| Local | zapbip pushes your message to the [connector](https://docs.zapbip.com/developers/local-connector.md) running on your computer, which resumes your Claude Code or Codex session. | 7 s Claude Code, 6 s Codex |
| Webhook | zapbip calls a link that starts the AI. See the [webhook wake guide](https://docs.zapbip.com/developers/webhook-wake.md). | 9 s Grok Bot, 16 s claude.ai |
| Scheduled | The AI checks its inbox on a timer, so it can listen with no time limit. | up to the interval |
| Standby | Another AI of yours receives a copy of your message and answers instead. | not measured |
| Inbox only | The message waits and zapbip tells you the AI is not listening right now. | until an AI reads it |

In every rung your message is kept in the [inbox](https://docs.zapbip.com/concepts/inbox.md) until an AI reads it. Nothing is lost.

## Local: your own computer

The connector keeps one open line to zapbip while it runs. When you write, zapbip pushes the message down that line and the connector resumes your session on your computer. When the last line closes, zapbip puts back whatever wake you had before. Start it with `npx zapbip@0.1.0 connect`.

## Scheduled: listening with no time limit

Some AIs have no way to be started from outside, and each call they make to zapbip ends after a few minutes. A scheduled wake fixes this: you ask the AI to run a small task on a timer, every few minutes or every hour, and each run reads what you wrote and answers.

You choose how often, from every 1 minute to every 1440 minutes (a day). ChatGPT and claude.ai only run scheduled tasks every 60 minutes or less often, so for them the shortest interval is 60 minutes.

When you write, zapbip tells you roughly when to expect the answer:

WhatsApp: zapbip

If the timer stops running, zapbip says so once, after twice the interval passes without a check, and your messages keep waiting:

WhatsApp: zapbip

The next check ends the warning without another message.

When the [24-hour window](https://docs.zapbip.com/concepts/24-hour-window.md) is closed, this note cannot be sent as it is. zapbip sends one template [notice](https://docs.zapbip.com/concepts/owner-notices.md) per closed window, and the note waits and arrives when you write.

## Standby: another AI answers

Some AIs, such as Grok on the web, cannot be started at all. You can name another AI of the same account as its standby, for example Grok Bot. When you write to the first one, zapbip gives the standby a copy, wakes it, and it answers as itself, saying who it is. The first AI sees the message as handled by the standby.

WhatsApp: zapbip

A standby never forwards to another standby: it is one hop only. If the standby is missing, was removed or is itself a standby, nothing is copied: the message waits with the first AI and you get the usual notice.

The AI sets this up for you during install. To change it by hand, use [set\_wake](https://docs.zapbip.com/mcp-reference/set-wake.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.