What registration settles, and what it does not
Partners stop introducing clients when they cannot tell whether an introduction will still be theirs by the time the deal closes. A contractor mentions a supplier to a client, the client fills in the supplier's enquiry form, a direct seller calls back the same afternoon, and the contractor hears about the sale weeks later. After that happens a couple of times, the contractor recommends a competitor whose rules are clearer. Registration answers one question in advance and in writing: who owns this introduction, from when, and until when.
The channel partner guide names four rules on leads: ownership, deal conflict, routing and one record per organisation. Registration applies all four to a single introduction as it arrives: the registration is the claim, the check decides whether it is new, the approval starts the clock, the route sends the deal to whoever works it and the expiry ends the claim if nothing happens. Several pages already assume the procedure exists. The diagnosis of pipeline coverage that is too low fixes partner introductions that never reach the CRM by agreeing the registration rule and requiring a partner field when an opportunity is created. The co-marketing launch checklist asks for lead ownership to be agreed before a joint campaign goes live. And the manufacturing guide asks distributors to agree in advance which lead and order reports they will share.
What registration does not settle matters as much, because a form that tries to settle everything is a form nobody completes.
| Question | Settled by registration? | Where it is settled |
|---|---|---|
| Which partner owns this introduction, and until when | Yes | The ownership rule, the approval and the expiry date |
| Whether the organisation is already a customer or in an open deal | Yes, by the check before approval | The CRM, after matching and deduplication |
| Who works the deal day to day | Yes, through the route | The routing rule set |
| How much the partner is paid, and when | No | The partner's agreement, designed with the affiliate economics guide |
| Whether a business belongs in the channel programme or an affiliate programme | No | The comparison of channel partner and affiliate programmes |
| Whether the client may receive the vendor's marketing | No | The vendor's own consent records |
| What the partner agreement may lawfully say | No | Whoever owns legal review of partner agreements |
The last row is deliberate: agreements about who may sell to whom can raise legal questions this page does not address, so take advice on the agreement itself and use this tutorial for the procedure that runs under it.
Before you start
- The sales leader and whoever runs the CRM, committed by name. Registration changes who receives deals and how they are recorded, so both belong in the first meeting, not only at sign-off.
- Your partners, sorted by type. The channel partner guide separates resellers and distributors, referral partners, technology partners and implementers; note which of yours actually originate deals.
- The current sourcing rule from the agreement between sales and marketing, which will need a partner line.
- Company records you can trust. The check in step five is only as good as the matching behind it, so fix unattached contacts and repeated companies with the guide to matching contacts to company records.
- A list of recent partner introductions from partner managers' notes and inboxes, as a baseline and to backfill opportunities that partners introduced but nobody recorded.
- A draft responsibility chart. A RACI matrix with one accountable role per decision, sketched now and finished in step nine.
The steps
Decide which partners and deals registration covers
Not every partner relationship needs registration. A technology partner whose integration helps win deals the vendor originated rarely introduces anyone, and asking it to register adds paperwork without settling any question. Registration earns its place where partners originate deals a direct seller could also reach: referral partners who introduce clients, resellers and distributorsA partner that buys a brand's product and sells it on in a market through its own shops, sales force and online channels, taking on much of the marketing. who sell the product on, and implementers who recommend it in their own projects. Write down which partner types register and which deals can be registered at all. As general practice, exclude existing customers, whose growth belongs with the account's owner, and organisations already in an open opportunity. Decide too how registration meets named accounts. If direct sellers work a tiered list as the account-based marketing guide describes, either those accounts are closed to registration or a partner's introduction to one becomes a joint deal led by the account's owner with the partner credited. Either can work; leaving it open produces the first dispute. Record the scope in a short paragraph partners can read.
Write the ownership rule with sales and partners
The ownership rule is the sentence every later step applies. The channel partner guide gives two common forms: the side that registered first in the CRM owns the lead for a set period, or the partner is credited with every account it brought in, whichever route the lead takes afterwards. Choose with the sales leader and a few partners of each type in the room, because a rule partners had no part in reads as the vendor's way of keeping deals. Spell out what owning a deal means: who leads the conversations, whether a direct seller may contact the organisation during the period, how the partner is credited if a direct seller closes, and what happens when two partners claim the same organisation. The sales and marketing alignment guide settles credit disputes with a sourcing rule written into the agreement between the teams; add partner-sourced and partner-influenced to that rule and to the service-level agreementA published promise between teams, or with a supplier, about what each type of request needs and how quickly it will be handled, agreed rather than imposed., so the same words govern sellers and partner managers. Set the length of the period from your own records of how long introductions take to become opportunities, not from another programme. Date the rule, name who agreed it and keep superseded versions.
Define what a registration must hold
A registration needs enough to check, route and later report the deal, and nothing more. As general practice that means the partner and the person registering, the organisation's name and website domain for the matching check, the region or segment routing depends on, a sentence on what the client needs, the expected next step, and confirmation that the client agreed to be introduced. That last field matters more than it looks. The co-marketing partnerships guide, which cites the GDPR and the UK Information Commissioner's Office's direct marketing guidance (sources this page also lists), says a business may hand someone's details to another business only if that person agreed, and the channel partner guide holds partner programmes to the same rule. A client contact's name and work email address are personal dataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier., so ask for a named contact only where the deal cannot be worked without one. The client's agreement is permission for an introduction, not consent to the vendor's marketing, which the list building and consent guide treats as a separate choice the business must be able to show. This is educational, not legal advice; ask whoever owns compliance to approve the wording. Every optional field is one more reason for a busy partner not to register.
Build the route and the CRM fields
Registration lives in the CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it., not in a spreadsheet beside it. The CRM fundamentals guide supplies the pieces: fields required when a record is created and a source picklist that names the partner for introductions that arrive without a landing page, with the channel partner guide adding one person who owns the data model. For registration that usually means a partner field on company, contact and opportunity records, a registration date, a status that moves from submitted to approved, declined or expired, an end date and a decline reason. Make the partner field required when an opportunity is created rather than at close, so partner deals cannot surface later as direct ones, and have whatever form partners use write into these fields rather than into an inbox. Write each route as its own row in the lead routing rules template, with its owner, a fallback and the path a declined registration takes, then run the lead routing QA checklist with test registrations: a new organisation, an existing customer, an open opportunity, a duplicate and a registration whose owner has left.
Check each registration against existing records
Before anyone approves a registration, find the organisation in the CRM. Match on the website domain first, with every known domain held on the one record and with parents, subsidiaries and regional offices arranged as the matching guide sets out, because a partner may register one division of a group a direct seller already owns. The check asks four questions: is the organisation already a customer, is it in an open opportunity, has another partner a live registration for it, and does it exist as more than one record? The last has to be fixed before the first three can be trusted. The diagnosis of duplicate contacts in the CRM traces repeated records to entry points such as forms that create a record on every submission, and a registration form becomes one more if it creates records instead of matching them. Apply deduplicationRemoving double counts when one conversion is reported by more than one source. before approval, attach the registration to the existing company record, and note what the check found, so the decision rests on evidence rather than on anyone's memory of the account.
Approve or decline within a stated time, with a reason
An unanswered registration does more damage than a declined one, because the partner cannot tell whether to keep working the client. Name the role that decides, such as the partner manager with a deputy, and state in the rule how quickly a decision is owed: a time the approver can actually sustain, published to partners and measured from the status timestamps. An approval records the dates the ownership period starts and ends. A decline records a reason from a short picklist, such as an existing customer, an open opportunity, another partner's live registration, outside scope or missing information, and tells the partner what would change the answer; a registration short of information goes back as a question, not a refusal. Reasons show partners the rule applied consistently and, over time, show where the scope or the form is wrong. Report decision times beside them, so a slow queue is noticed early.
Route approved registrations to their owner
Approval should move the deal to whoever works it without anyone forwarding an email. The ownership rule decides who: for a reseller's deal, often the partner itself, with the partner manager as the vendor's owner of record; for a referral, the partner manager, who brings in a direct seller with the partner credited; for a named account, the account's owner with the partner attached. Set up lead routingRules that assign each new lead to an owner, queue or next step based on territory, segment, score or source. so that an approved registration never drops into the rotation that serves website enquiries, which is exactly how partner introductions end up worked as direct. Send the owner the registration itself, with who introduced the client, what the client wants and the agreed next step, and tell the partner who will be in touch. From here the deal is an ordinary opportunity with a partner field, and it belongs in the weekly pipeline review like any other. Add stalled registered deals to the list the review works through, since a partner watching its deal sit untouched soon stops registering.
Set expiry and renewal
A registration that never ends blocks everyone else from the organisation, and partners soon learn to register every name they have heard. Give every approval an end date, set from your own records of how long introduced deals take to reach the stage at which an opportunity is normally opened. Decide what counts as progress, such as a meeting held, a site visit or a quote sent, and what renewal requires: evidence of that progress, requested before the end date and granted a limited number of times. Warn partners before a registration lapses, and record expiry as a status rather than deleting anything. An expired organisation returns to the open pool, and a fresh registration of it goes through the check like any other. Keep the renewal rule in the same document as the ownership rule.
Settle disputes through one named decider
Some claims will collide however carefully the rule is written: two partners who both met the client, a partner and a seller who reached different people at the same organisation, a registration submitted just after a seller logged a first call. Settle them through one role named in advance. A RACI matrix makes the arrangement explicit: the sales leader, or a channel lead who answers to them, accountable for dispute decisions; the partner manager responsible for preparing each case; the seller and partner consulted; and finance informed where payment depends on the outcome. The RACI framework insists on one accountable role per row; where two people can each settle a dispute, partners lobby the more sympathetic one. The decider applies the written rule to the timestamps and the check's record, then writes down the outcome and reasoning in a log of precedents that partner managers consult. When the same collision keeps returning, change the rule through a dated revision rather than ruling differently case by case, because inconsistent rulings teach partners that registering is pointless.
Report registrations through to revenue and review the rule
Registration earns trust only when partners and the business can see what came of it. Build one report that follows each cohort of registrations through approval, opportunity, pipeline and won revenue, by partner and partner type. Keep partner-sourced pipeline apart from partner-influenced and from marketing-sourced pipeline, as the sourcing rule defines them, and read it by cohort, following the business-to-business measurement guide, since introduced deals keep their own pace and the newest cohorts look weak until they mature. Where deals close through resellers or distributors, match the orders they report to the registrations that started them, using the reports the manufacturing guide asks distributors to agree in advance. Each month, reconcile approved registrations against opportunities created, as the pipeline coverage diagnosis prescribes, and chase approvals that never became opportunities. Counts per partner will be small, so read them with the cautions in the guide to reading small numbers. Then review the rule with sales and partners on a set date, using decision times, decline reasons, expiries and the precedent log.
The registration rules on one page
Partners, partner managers and sellers should be able to read the whole procedure in a few minutes, on a page kept with the agreement between sales and marketing and dated at every revision.
| Rule | What to write down | Accountable role | What to watch |
|---|---|---|---|
| Scope | Partner types that register, excluded deals, named accounts | Sales leader | Declines as outside scope |
| Ownership | What approval gives the partner, for how long, and credit if a seller closes | Sales leader, partners consulted | Disputes the rule does not answer |
| Form | Required fields, the client's agreement to be introduced, when a contact is needed | Partner manager; compliance approves wording | Registrations returned incomplete |
| Check | Domain matching, parent and subsidiary records, and the four questions | CRM owner | Duplicates found at approval |
| Decision | Approver, stated decision time, decline picklist | Partner manager | Decision times; decline reasons by partner |
| Route | Where each approved deal goes, with fallbacks | CRM owner, sales agreeing routes | Partner deals worked as direct |
| Expiry | End date, what counts as progress, renewal | Partner manager | Expiries and repeat registrations |
| Disputes | The decider, the evidence used, the precedent log | One named role | The same dispute recurring |
| Reporting | Sourced and influenced apart, cohorts, distributor reports matched | Whoever owns reporting | Approvals with no opportunity |
Give partners the page when they join, point the co-marketing checklist's lead ownership line at it for joint campaigns, and send the revised version, with what changed, whenever the rule moves.
An irrigation controller maker registers its contractors' deals (illustrative)
Ogrumvale Irrigation gets its contractors registering again
Ogrumvale Irrigation is an invented maker of commercial irrigation controllers, sold through 70 landscape contractors who recommend them and 4 distributors who resell them. In one quarter, two contractors and a direct seller all claim the same group of 6 golf courses. Contractors register deals by emailing the partner manager, and 12 of that quarter's 31 emailed registrations are still unanswered after 3 weeks. Next quarter, contractors send only 9.
The partner marketer writes the rule with the sales director and 5 partners: the first approved registration owns the deal for 120 days, and existing customers and open opportunities are excluded. A form of 7 fields records that the client agreed to the introduction and asks for a named contact only when the contractor wants Ogrumvale's seller at a site visit. Checking registrations against company records first means merging 40 duplicate company records. The partner manager decides within 3 working days, with a reason for every decline; a registration can be renewed once, for 60 days, with evidence of a site visit or a quote. The sales director decides disputes, logging each ruling as a precedent.
Over the following two quarters, 148 registrations arrive. 119 are approved and 29 declined: 14 for existing customers, 9 for open opportunities, 4 for another partner's live registration and 2 as outside scope. The median decision takes 2 working days. Of the approved registrations, 71 become opportunities, 11 are renewed once, 23 expire and 25 are still within their period at the end of the second quarter. Disputes fall from 7 in the quarter before the rule to 3 in the second quarter after it. The monthly report shows £1.3 million of partner-sourced pipeline beside £2.9 million of direct pipeline and £0.6 million of partner-influenced pipeline, all in one report for the first time, and the distributors' monthly order reports are matched to 26 registered deals they closed. With so few deals per contractor, the team reads per-partner counts as directions, not rankings.
The demand section places registration beside the partner, event, reference and account-based guides that feed it. If introductions happen but never reach pipeline reports, start with the coverage diagnosis linked above.
Common mistakes
- Making every partner register everything. Aim registration at partners whose introductions a direct seller could also reach.
- Writing the rule without partners or sales. Partners distrust it, and sellers ignore it at the first collision.
- A long registration form. Ask only for what the check, the route and the report need.
- Approving before checking the records. Approving an existing customer or open deal creates the very conflict registration exists to prevent.
- Leaving registrations unanswered. Silence stops partners registering faster than a decline does; state a decision time and measure it.
- Registrations with no end date. Open-ended claims block other partners and invite registering every name heard.
- More than one person who can settle a dispute. Partners lobby whoever is more sympathetic; name one decider and keep a log of precedents.
- Treating an introduction as marketing consent. The client agreed to a conversation, not to the vendor's newsletters.
- Recording partner deals as direct, or influenced pipeline as sourced. Require the partner field when the opportunity is created and report sourced and influenced pipeline separately.
