> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/pulse/queue.md).

# The queue

Pulse is the attention layer: only what needs a human, everything else handled in the background.

Pulse is your attention layer: only what needs a human. The system works continuously in the background. When something needs you to see it or decide it, it raises a hand here, and the rest is reported in your [daily digest](/pulse/daily-digest.md).

What does it do without asking me? Whatever you have approved it to do. Everything else waits here. Pulse is a communication channel, not a dashboard.

The heart of the surface is **Needs you**: the queue of pulses with a pending action. The badge counts exactly those, so **badge zero means nothing is waiting on you**, not "nothing happened." Clear the queue and you are caught up.

## Push and pull

Pulse is the push side of the platform.

|          | Who starts it | What it looks like                                                                                       |
| -------- | ------------- | -------------------------------------------------------------------------------------------------------- |
| **Pull** | You           | You run a play.                                                                                          |
| **Push** | The system    | It raises its hand. An opportunity worth acting on arrives as a pulse, and running it remains your call. |

## What arrives

Every pulse has three parts:

* one [family](/pulse/families.md),
* a severity tier,
* and one primary action, leading.

A pulse is generated at the moment it fires, from what the system actually observed, with one line of reasoning attached. Pre-written sequences are lifecycle email, not pulses.

## The tabs are views

Tabs like Activation, Digest, Alert, Inbound, Setup, and Insight are lenses computed from each item's metadata, never hand-sorted piles.

* **Needs you** is the default.
* **Activation** is a status board for what is currently live.
* **Digest** holds your daily envelopes.

Acting on a pulse (approve, modify, reject, or skip) is covered in [Acting on a pulse](/pulse/acting.md). Where pulses reach you is covered in [Delivery](/pulse/delivery.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aloop.icustomer.ai/pulse/queue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.