Approvals
Pulse treats human approval as a first-class part of the product experience. Before a sensitive action runs, the agent can pause and request a decision — keeping a person in the loop without breaking the flow of work.
How approvals work
When the agent reaches an action governed by an approval policy, it stops and emits an approval request into your timeline. The pending action waits until it is approved or rejected. Approve it and the agent resumes exactly where it paused; reject it and the action is abandoned with that outcome recorded.
Because the approval stays attached to the original work, context is preserved across the pause. There is no lost thread when you come back to decide.
Where you can approve
The same approval request can be acted on through three channels:
| Channel | Best for |
|---|---|
| In-chat | Quick decisions in the moment, in context next to the action |
| Email deep-link | Approving away from the app — the link opens directly to the decision |
| Approvals UI | Reviewing several pending requests in one dedicated place |
A decision made in any channel resolves the request everywhere. Approve by email and the in-chat request updates to reflect it.
Approval policies
Policies are configurable and determine which actions require approval and under what conditions. You decide where the line sits — for example, requiring approval before sending external messages, modifying CRM records, or running an irreversible operation, while letting routine work proceed unattended.
WARNING
Approval policies are a safety boundary. Set them around actions with external or irreversible effects so the agent cannot complete them without an explicit human decision.
Human-in-the-loop by design
Approvals make Pulse safe to delegate to. The agent can plan and execute autonomously, run tasks on a schedule, and reach into integrations — but the moments that matter still route through a person. This is what lets teams hand real work to the agent while staying in control of sensitive steps.
Approval requests sit naturally alongside the work that triggered them. You see what the agent intends to do, why, and the exact action awaiting your call — then decide in one click.
When the agent needs information rather than permission, it asks a structured question instead — free text, single choice, or multi-select — and waits for your answer before continuing.
Managing approvals
The dedicated approvals area in settings lets you review pending requests, see resolved decisions, and adjust the policies that govern them. Combined with task run history, you get a clear audit trail of what was requested, who decided, and what happened next.