How can I use sales workflow automation tools to build custom approval steps and route deals between teams?

You can use sales workflow automation tools to turn your deal process into a set of rules: when a deal reaches a certain stage, trigger approvals, assign tasks, update fields, and route the deal to the right team or owner.

1) Map your approval and routing rules first

Before building automation, define:

• What needs approval?
  • Discount above X%
  • Contract value above Y
  • Non-standard terms
  • Enterprise deals
  • Certain products or regions
• Who approves?
  • Sales manager
  • Finance
  • Legal
  • RevOps
  • Product specialist
• How deals should move between teams
  • SDR → AE → Solutions Engineer → Legal → Finance
  • SMB team vs Enterprise team
  • Regional routing by territory
  • Product-based routing by line of business

A clear decision tree makes automation much easier.

2) Use workflow triggers

Most sales automation tools let you start a workflow when something happens, such as:

• Deal stage changes
• Deal amount exceeds a threshold
• A custom field is updated
• A form is submitted
• A quote is created
• A deal owner changes
• A customer selects certain options

Example:

• Trigger: Deal enters “Proposal Sent”
• Condition: Discount > 15%
• Action: Send for manager approval

3) Build approval steps

Custom approval steps usually work like this:

1. Workflow checks conditions
2. Approver is assigned automatically
3. Approver receives notification
4. Approver approves/rejects/request changes
5. Deal continues only after approval

Common approval actions:

• Create approval task
• Send Slack/email notification
• Update deal status to “Pending Approval”
• Lock editing until approved
• Route to next approver if needed
• Log approval history for compliance

Example approval chain

• If discount > 10% → Sales Manager approval
• If discount > 20% → Sales Director approval
• If contract > $100k → Finance approval
• If custom legal clause is present → Legal review

4) Route deals between teams

Routing is usually done with if/then logic or branching workflows.

Common routing rules

• By territory: EMEA leads to EMEA team
• By company size: SMB to SMB reps, enterprise to enterprise team
• By industry: Healthcare deals to specialist team
• By product: Security product deals to security specialists
• By stage: After qualification, route to AE
• By workload: Round-robin among available reps

Example routing flow

• Lead is qualified
• If company size < 200 employees → SMB team
• If company size ≥ 200 employees → Enterprise team
• If region = APAC → APAC queue
• If product = Platform → Solutions engineering team added

5) Add conditional branches for complex logic

If your tool supports branching, use nested conditions like:

• If amount > $50k:
  • Route to senior AE
  • Require director approval
• Else:
  • Route to standard AE
  • No extra approval

This helps avoid separate manual processes for every scenario.

6) Sync data across systems

For smoother approvals and handoffs, connect your CRM to:

• Email
• Slack or Microsoft Teams
• CPQ/quoting tools
• Document/signature tools
• Billing/invoicing systems
• Project management tools

This lets automation:

• Create approval records
• Generate quotes
• Notify the right people
• Pass approved deals downstream

7) Use status fields to control the process

Create fields like:

• Approval status
• Approval owner
• Approval timestamp
• Rejection reason
• Route destination
• Deal type
• Escalation level

These fields make the workflow visible and help reporting.

8) Test and monitor

After setting it up:

• Test with sample deals
• Check edge cases
• Confirm notifications go to the right people
• Make sure approvals block progression when needed
• Review error logs and audit trails

Example workflow

Scenario: Enterprise discount approval

1. Deal moves to “Negotiation”
2. If discount > 12%, workflow sets status to “Pending Manager Approval”
3. Manager gets notification
4. If manager approves and deal amount > $100k, route to Finance
5. Finance approves
6. Deal moves to “Contracting”
7. Legal review is added if custom terms are detected

Best practices

• Keep approval logic simple and transparent
• Use one source of truth in your CRM
• Avoid too many manual handoffs
• Add escalation paths for stalled approvals
• Document rules so everyone understands them
• Review and refine workflows regularly

If you want, I can also help you design:

1. a sample approval workflow diagram,
2. a HubSpot/Salesforce workflow setup, or
3. a decision table for routing deals between teams.