Resellers register deals through a portal form; Make checks the CRM for conflicts on the spot, routes a one-click approval to the channel manager and sends protected-deal terms back automatically. Median approval time: two hours instead of six days.
Typical results
41
Deals registered monthly, up from 25
1
Conflict dispute last quarter
40+
Resellers on the portal
Figures reflect typical results for this kind of automation.
The challenge
Deal registration ran on email: a partner wrote in, someone checked the CRM by hand for conflicts with direct deals or other resellers, and the thread bounced for six days on average. Partners lost confidence, registered deals elsewhere first, and channel conflicts still slipped through — six disputes a quarter.
Before and after
Registration approval time
−99%Deals registered per month
+64%Channel conflicts per quarter
−83%The automation
We built a partner portal form connected to a Make scenario that checks every registration against open opportunities, existing registrations and named accounts in the CRM — instantly. Clean deals route to the channel manager as a one-click approval; genuine clashes arrive with both sides of the story attached. On approval, the partner automatically receives protected-deal terms and the deal lands in the CRM tagged to their account.
How it works
- 01
Partner registers
A reseller submits the deal through the portal form — no email threads.
- 02
Conflict check runs
Make instantly compares the account against open opportunities and prior registrations in the CRM.
- 03
Approval routed
Clean deals reach the channel manager as a one-click approval; clashes arrive with full context.
- 04
Terms sent
Approved partners automatically receive protected-deal terms and margin confirmation.
- 05
Pipeline stays honest
Every registration lands in the CRM tagged to the partner, feeding a live channel dashboard.
Starts from
- Deal registration form
- Existing pipeline
Delivers
- One-click approval routing
- Protected-deal terms
- Live channel pipeline
The impact
Median approval time fell from six days to two hours, and partners noticed: monthly registrations climbed from 25 to 41 as resellers started bringing deals here first. Channel conflicts dropped from six disputes a quarter to one, each resolved with data instead of arguments.
Questions about this automation
What does the conflict check compare a new registration against?
The flow searches the CRM for open direct opportunities on the same account, earlier registrations from other partners and the vendor's named-account list. It matches on company domain and name variants, so a registration under a slightly different spelling is still caught. The result is either a clean pass or a clash report showing both records.
How does the channel manager approve or reject a deal?
Clean registrations arrive as a message with the deal details and approve and reject buttons. Clashes arrive with both sides attached, such as the existing opportunity, its owner and its stage, so the manager can decide quickly. Every decision is logged on the CRM record, and the partner hears back automatically either way.
What does the partner receive once a deal is approved?
The partner gets an email with the protected-deal terms: the registration period, the margin tier that applies and the expiry date. The deal is created in the CRM tagged to that partner, and a reminder goes out before the protection lapses so the partner can request an extension if the deal is still active.