Skip to content
VideoGovernanceBeginner

How approvals work

The path a prepared change takes from an agent to your CRM, and every point a person can stop it.

RRRevTech RevOpsRevenue operations team 3 minUpdated

Product walkthrough

See it in RevTech

A walkthrough of the approval path: an agent prepares a change, routing sends it to a reviewer, and the CRM is written only after a person releases it.

How approvals workComing soon
A walkthrough of the approval path: an agent prepares a change, routing sends it to a reviewer, and the CRM is written only after a person releases it.
Part 1 of 3

The path a change takes

Nothing an agent prepares reaches your CRM without passing a person. The walkthrough follows one change the whole way: an agent assembles it with its reasoning, routing decides who reviews it based on the object and the severity, the reviewer approves, edits, or rejects, and only then is anything written back.

The recording also covers what happens when nobody acts. Items do not expire silently or apply themselves after a timeout. An unreviewed change stays unreviewed, which is the conservative failure mode and the correct one.

Part 2 of 3

What is recorded, and what reaches the CRM

A governance page that overstates what the platform enforces is worse than no page at all, so this is the boundary as it stands. Ordinary work resolves three ways, and each is recorded in a production tenant: mark the work complete, ignore it with one of five reasons, or escalate it to a named teammate. Those are the decisions an audit trail is built from.

Sign-off is a recorded decision too. A drafted campaign, a new version of a play, a new analyst question and a drafted artifact each arrive as a review card with three answers: Approve, Request changes and Reject. "Not like this" and "this should not happen" are different answers, so both ask for a reason, and the reason is stored with the decision for the author to act on. The card stays put until the decision is saved, so a write that fails leaves it exactly where it was. Each decision needs the permission that owns the thing being approved: marketing:write for a campaign, revplays:publish for a play, ai_agents:write for an analyst question, and artifacts:write for an artifact.

Two writes that used to happen only in the CRM can now be made from the card, and both wait for the CRM to confirm. On a card about an unowned account, contact or deal, an owner picker sits beside the complete control, and whoever is selected when you complete it becomes the record's owner in the CRM. Record Outcome on a call and Add LinkedIn Activity on a LinkedIn message open a form that saves to the action's account, contact or deal, and the write-up stays on screen until the CRM has answered. The LinkedIn form records a message you sent yourself; RevTech does not send LinkedIn messages.

  • Recorded on every card: complete, ignore with a reason, escalate
  • Recorded decisions, with the reason stored: Approve, Request changes and Reject on campaign, play-publish, analyst-question and artifact-review cards
  • Written to the CRM from the card, once the CRM confirms: a record's owner, a call outcome, a LinkedIn message you sent
  • Released by a person outside the queue: deal fields edited in place on My Pipeline (HubSpot deals; Salesforce deals are read-only there), and updates proposed by the assistant, which come back as an editable proposal with an Apply button
Part 3 of 3

Who reviews what

Routing is configuration, not a default you inherit. Severity, object type, and team ownership all feed it, and RevOps sets the mapping.

  • Low and medium severity typically routes to the record owner
  • Critical items route to a manager or RevOps
  • Anything customer-facing routes to a person regardless of severity
RevTech: RevOps Home connects team performance, operational actions and a Pipeline Hygiene preview.
RevOps Home connects team performance, operational actions and a Pipeline Hygiene preview. Captured from the current application with illustrative sample data. Screenshot of the RevTech application; sample data.
RevOps Home connects team performance, operational actions and a Pipeline Hygiene preview.

What to take away

  • Nothing reaches your CRM without passing a person.
  • An unreviewed item stays unreviewed. Nothing applies itself on a timeout.
  • Routing is configuration you set, not a default you inherit.
  • Every answer is recorded. Complete, ignore with a reason and escalate resolve ordinary work; Approve, Request changes and Reject are recorded decisions on sign-off cards.
  • Request changes and Reject both need a reason, and the reason is stored with the decision.
Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo