Using Pagr
Notifications
An agent that texts you about everything is worse than one that texts you about nothing. Three policies decide how much of an agent's progress reaches your phone.
The three policies#
| Policy | You hear about |
|---|---|
default | Sessions starting, agents needing input, approval requests, completions and failures. |
blocked_or_done | Only when an agent is blocked, needs an approval, finishes or fails. Progress goes quiet. |
quiet | Only approvals and direct questions from an agent. |
The policy applies to proactive messages — the ones Pagr starts. Anything you ask for directly is always answered.
Changing the policy#
Say it in the thread. There is nothing to open.
you don't text me unless they're blocked or donepagr Okay — I'll only text you when an agent is blocked, needs approval, finishes or fails. you be quietpagr Okay — I'll stay quiet except for approvals and direct questions. you back to normal updatespagr Okay — back to normal updates.The preference is stored on your account and survives sessions and reboots. A review workflow can also carry its own policy, so a long unattended review can stay quiet without changing your global setting.
What is always delivered#
Two things ignore the policy, because ignoring them would break the product:
- Approval requests. An agent waiting on permission is blocked until you answer. Even
quietdelivers these. - Direct questions. When an agent asks you something and cannot continue without an answer.
If you would rather not be asked about low-risk work at all, the answer is smart approvals rather than a quieter policy — see approvals.
STOP and START#
These are carrier compliance keywords, not settings, and they sit above the notification policy entirely. They are matched only as a bare, uppercase word.
| Message | Effect |
|---|---|
STOP | Outbound messaging to that number is disabled immediately, and Pagr does not send a confirmation — it may not. Also matches UNSUBSCRIBE, CANCEL, END, QUIT. |
START | Re-enables outbound messaging and confirms. Also matches UNSTOP. |
Lowercase “stop” is not a compliance keyword. It interrupts an agent session, which is almost always what you meant.