Sales features

A deal approval process for big discounts and wins

Set up your deal approval process once: decide which quotes, discounts and deal moves need a second pair of eyes, and DigiPix Flow routes every matching request to a named approver in the right role, gives it a due time, keeps it in one inbox until someone decides, and records who said yes, who said no and why — so sign-off stops living in a manager's WhatsApp chat.

  • Proposal and deal requests in one inbox
  • Routed by role, never to the person asking
  • A due time on every request, with reminders
An example of the DigiPix Flow Approvals page for Deepak Kulkarni, with desks for Pending mine, Pending team, Decided, Stale and My requests. A request for a 14% discount on PROP-00018, Showroom lighting, arrives from Sneha Nair under the Deep discounts rule. When it passes its due time it is marked overdue and the Stale count rises, Amit Mehta reassigns it to Deepak Kulkarni, and Deepak approves it with a comment, after which it moves from pending to decided.
desks, from Pending mine to My requests
5
deal triggers: won, discount, stage entry
3
of deal growth before a sign-off must be renewed
0.5%

What a rule can check

  • Proposal amountRules on the quote's amount band
  • Proposal discountRules on the discount percentage
  • Close as WonDeal rules on the amount being closed
  • Deal discountMeasured across the deal's line items
  • Stage entrySign-off before a deal enters one stage
  • Approver roleSales manager, Finance or Org admin
THE PROBLEM

Where sign-off goes wrong

See how it's fixed
  1. Sign-off buried in a group chat

    A rep asks for an extra 8% on WhatsApp, the manager sends a thumbs-up between meetings, and the quote goes out. A month later nobody can find the message, and nobody can say whether that thumbs-up was for this deal or the one before it.

  2. Requests that sit with no one

    The person who usually approves is travelling, the request has no deadline, and the rep doesn't know who else can say yes. The buyer waits, the competitor calls back first, and the discount that needed a quick answer costs you the order.

  3. An approval stretched to fit a bigger deal

    A manager signs off a ₹4 lakh deal. Two weeks later the same deal is ₹9 lakh with the same discount, and the old approval is quietly treated as if it still covers it. The margin loss only shows up when the month closes.

ONE INBOX

Every request waiting on a decision, in one place

The Approvals page brings proposal and deal requests into one list, split into desks: what's waiting on you, what's waiting on the team, what has been decided, what is past its due time, and the requests you raised yourself. Search by proposal number, deal or approver, and filter to proposal or discount requests. Reps without approver access still get My requests, so they can follow what they asked for without chasing anyone.

  • Desks for Pending mine, Pending team, Decided, Stale and My requests
  • Proposal and deal requests side by side
  • Search by proposal number, deal or approver
  • A requester's own desk showing who decided and why
See approvals on the pipeline
An example of the DigiPix Flow Approvals page on the Pending mine desk, with desks for Pending mine, Pending team, Decided, Stale and My requests. Four requests wait on this approver: a proposal for PROP-00012 under the Large quotes rule, a 14 percent discount request, a deal waiting to close as won above ten lakh and a deal entering Negotiation, each with its amount, requester and time left. The Stale desk holds two overdue requests.
APPROVAL RULES

One approval matrix for what needs sign-off

Approval rules sit in Settings as a single matrix. Proposal rules match on an amount band and a discount percentage. Deal rules match on closing as Won above an amount, a discount across the deal's line items, or entering one stage you choose. Rules run in the priority order you set, can be switched off without being deleted, and a preview tells you which rule and approver a given total and discount would hit before you save.

  • Proposal rules on amount band and discount %
  • Deal rules for Close as Won, discount and stage entry
  • Priority order, with an on/off switch per rule
  • A preview of the rule and approver before you save
Explore proposals
An example of the DigiPix Flow approval matrix in Settings: two proposal rules, Large quotes from five to twenty-five lakh for a sales manager within two business days and Deep discounts of twelve percent or more for Finance within eight hours, and three deal rules for closing as won above ten lakh, a line-item discount of fifteen percent and entering Negotiation, the last one switched off. A preview shows that a ₹6,40,000 proposal with an 8 percent discount would go to any sales manager with a two business day due time.
ROUTING

The right approver, picked the same way every time

Each rule names an approver role — Sales manager, Finance or Org admin — and can name a specific person as well. When a rule routes by role, DigiPix Flow picks one active holder of that role: never the person who raised the request, and never someone without the access to decide it. The requester's own reporting line is tried first; otherwise the request goes to whoever has the fewest approvals waiting.

  • Sales manager, Finance and Org admin approver roles
  • Name a specific approver on any rule
  • The requester is never picked when routing by role
  • Reporting line first, then the least loaded approver
Explore roles and permissions
An example of how DigiPix Flow picks one approver for PROP-00021, raised by Rahul Kumar under a Large quotes rule that routes to the Sales manager role. Rahul is skipped because he raised the request, Sneha Nair is skipped because she can't decide proposals, Amit Mehta is eligible with two pending approvals, and Deepak Kulkarni is picked because he is Rahul's manager. Below, the three approver roles and the roles that count for each.
DUE TIMES

A due time on every request, and a nudge when it slips

Every rule carries a response time in hours or business days. Business days skip Saturdays and Sundays and are counted in your workspace's time zone, so a Friday request isn't due on Sunday. Each request shows how long is left or how far overdue it is, overdue requests move to the Stale desk, and a background check records the breach and escalates it if it keeps waiting.

  • Due times in hours or business days, per rule
  • Weekends skipped, in your workspace's time zone
  • Time left or time overdue on every request
  • Approver reminded once a request passes its due time
See how follow-ups escalate
An example of DigiPix Flow approval due times: a request submitted on Friday 12 September at 16:00 under a two business day rule comes due on Tuesday 16 September at 16:00, with Saturday and Sunday skipped. Once it passes its due time, the breach is recorded and the request moves to the Stale desk, the approver is reminded, and by default it escalates four hours and then twenty-four hours after the due time.
DECIDE

Approve, reject with a reason, or pass it on

Only the approver a request is assigned to can decide it. They see the numbers of the version that was submitted, with the change from the previous version, and approve or reject; rejecting needs a comment, so the rep knows what to fix. An approver can reassign their own request to a colleague, the due date carries over, and the requester can cancel a request they no longer need.

  • Only the assigned approver can decide
  • The submitted version's line items and total
  • A comment required to reject
  • Reassign with the same due date, or cancel the request
An example of deciding a DigiPix Flow approval request: PROP-00012 version 2 for Sharma Legal LLP, requested by Kavya Iyer and assigned to Deepak Kulkarni, showing the line items and total of the submitted version and the change from version 1. The approver types a comment, which is required to reject, and chooses Approve or Reject, with an option to reassign the request to Amit Mehta while keeping the same due date.
AMOUNT CHECKS

An approval covers the number it was given for

A deal approval is tied to the amount the deal had when it was requested. If the deal grows by more than half a percent after sign-off, the approval no longer counts: the deal shows that its amount changed and asks for a fresh request. A deal that shrinks keeps its approval. Proposals work the same way by version — revise an approved proposal and the new version goes back to draft.

  • Deal approvals bound to the amount at request
  • Growth above 0.5% needs a fresh sign-off
  • A smaller deal keeps its approval
  • A revised proposal goes back to draft
See deal stage rules
An example of a DigiPix Flow deal approval tied to its amount: Warehouse racks for Patil Logistics was approved to close as won at ₹12,40,000 by Deepak Kulkarni. The deal has since grown to ₹13,10,000, so it shows that the amount changed since approval and the Big wins rule needs a fresh sign-off, with a Request again button. A table shows that growth of 0.4 percent or a smaller deal keeps the approval, while 5.6 percent growth does not, and a revised proposal goes back to draft.
SEND GATE

No proposal leaves before it's approved

A workspace setting, on by default, requires every proposal to go through an approval request before it can be sent. With it on, a proposal can't be marked approved directly or emailed to the buyer until the current version has been approved by the approver its rule picked. Switch it off if your team doesn't need proposal sign-off; deal rules keep working either way.

  • Require approval before send, on by default
  • Sending unlocks only for the approved, current version
  • No shortcut to mark a proposal approved
  • Deal rules apply whichever way the switch is set
Explore proposals
An example of DigiPix Flow's Require approval before send setting switched on. PROP-00019 version 3 is pending approval with Amit Mehta, so its Send by email button is locked and it cannot be marked approved directly. PROP-00012 version 2 has been approved by Deepak Kulkarni as the current version, so sending is unlocked.
AUDIT TRAIL

A record of every request and every answer

Raising a request, deciding it, reassigning it and cancelling it are each written to the audit trail with who did it and when. A decision keeps its approver, time and comment, and a reassignment keeps who it moved from and to. Changes to the approval matrix itself are audited too, and two people editing the rules at once can't overwrite each other.

  • Requested, decided, reassigned and cancelled, each audited
  • Approver, time and comment kept on every decision
  • From and to recorded on every reassignment
  • Matrix changes audited and protected from overwrites
Explore the audit trail
An example of DigiPix Flow's audit trail filtered to approvals: Neha Patil changed the approval rules, Kavya Iyer requested approval for PROP-00012, Amit Mehta reassigned it to Deepak Kulkarni, Deepak approved it, and Sneha Nair cancelled a request for PROP-00018. The selected decision shows who decided, when, the decision and the comment left with it.
HOW IT WORKS

From rule to recorded decision, in five steps

  1. STEP 01

    Set the rules

    Add proposal and deal rules with amount bands, discount %, stages, roles and due times.

  2. STEP 02

    Request sign-off

    A rep submits a proposal or a gated deal action, and the matching rule applies.

  3. STEP 03

    Route to an approver

    One approver in the rule's role is picked — never the requester — with a due time.

  4. STEP 04

    Decide on time

    The approver approves or rejects with a reason; overdue requests escalate and get a reminder.

  5. STEP 05

    Keep the record

    Every request, decision and reassignment is audited, and the rep is told who decided.

THE DIFFERENCE

Approvals in a CRM vs messages to the boss

What it coversWhatsApp messages to the bossDigiPix Flow
What needs approvalWhatever the rep thinks to ask aboutRules on amount, discount %, closing as Won and stage entry
Who approvesWhoever replies firstOne approver in the rule's role, never the requester
DeadlineNone, until the buyer gives upA due time in hours or business days, per rule
When the approver is busyThe request waitsReminders once overdue, escalation, and reassignment
Reason for a noA missed callA comment required to reject
A deal that grows after sign-offThe old thumbs-up still countsGrowth above 0.5% needs a fresh approval
Proof laterScroll up and hopeRequests, decisions and reassignments in the audit trail

Approval questions, answered

What can require approval in DigiPix Flow?

Proposals, by their amount band and discount percentage, and three deal actions: closing a deal as Won above an amount, a discount across the deal's line items above a percentage, and entering a specific stage. Each is set up as a rule in the approval matrix in Settings.

Who approves a request?

Each rule names an approver role — Sales manager, Finance or Org admin — and can also name a specific person. When a rule routes by role, one active holder of that role is picked: the requester's reporting line first, otherwise whoever has the fewest approvals waiting. The person who raised the request is never picked, and neither is anyone who doesn't have access to decide it.

Can a request be approved by more than one person?

No. Every request has exactly one approver at a time, and only that person can approve or reject it. If they can't get to it, they can reassign it to a colleague, and anyone with workspace-wide access can reassign requests held by someone else.

How do due times work?

Every rule has a response time in hours or business days. Business days skip weekends and are counted in your workspace's time zone. The request shows how long is left, moves to the Stale desk once it's overdue, and a background check records the breach and escalates it if it keeps waiting. Reassigning a request keeps its original due date.

Will approvers be reminded?

Yes. An approver is reminded once a request passes its due time, and after two days for any request that has no due time.

What happens if a deal grows after it's been approved?

A deal approval is tied to the amount the deal had when approval was requested. If the amount grows by more than 0.5% afterwards, the approval no longer counts and the deal asks for a fresh request. If the deal gets smaller, the existing approval still stands.

Can a proposal be sent without approval?

Not while Require approval before send is switched on, which it is by default. The current version has to be approved through an approval request before it can be emailed. If your team doesn't need proposal sign-off, an admin can switch the setting off; deal approval rules keep working either way.

Does the approver need to give a reason?

A comment is optional when approving and required when rejecting. The requester is notified of the decision with the approver's name and the comment, and can follow every request they raised from the My requests desk.

Are approvals audited?

Yes. Raising, deciding, reassigning and cancelling a request are each recorded in the audit trail, as are changes to the approval matrix. A decision keeps who made it, when and the comment they left.

Something we haven't covered? Talk to an expert

Put every yes on the record

Talk to an expert — bring the discount and deal limits your team works to today, and see them set up as approval rules in DigiPix Flow.

  • A real person, not a bot
  • Bring your discount limits
  • See the approvals inbox for yourself
Talk to an expert