> 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/delivery.md). # Delivery Where pulses reach you: always in-app, and by email or Slack where you opt in. Pulses always land in the app; that is the record, and it cannot be turned off. Email and Slack are opt-in, per user, with preferences you control per family, so one person can get Stalls in Slack while another only reads the digest. ## The interrupt discipline Only the most urgent tier stands alone in email or Slack. Everything else rides the daily rollup, marked "already alerted" if it reached you earlier, so your inbox gets one envelope a day, not a drip. The interrupt cap keeps standalone pings rare; when more qualify than the cap allows, the rest demote into the digest rather than being dropped. ## Slack Slack delivery comes through one bot, **@iHarness**, the same identity you chat with. A pulse in Slack carries the same primary action as in-app; acting in either place resolves it everywhere. ## What delivery never does Delivery preferences change where a pulse reaches you, never whether it exists. Every pulse is on the record in the app regardless of channel, and the [daily digest](/pulse/daily-digest.md) accounts for everything the system did, alerted or not. Lifecycle email, onboarding nudges and scheduled sequences, is configured separately and is not part of Pulse delivery. --- # 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/delivery.md?ask=&goal= ``` `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.