This page is part of the guide to action-space constraints at a support desk, where a front-line agent can propose a refund but cannot issue one. Its job is a qualification scorecard. Use it after a conversation with the head of support or operations, filled in from answers, never from files.
How the scorecard works
Score each criterion 2 for strong, 1 for borderline and 0 for weak, for a maximum of 18. Three criteria are gates: company size, rights and the authorized contact. A weak score on any gate means the company is not ready for an introduction, whatever the total.
| Total | Reading | What to do |
|---|---|---|
| 14 to 18, no weak gate | Strong fit | Introduce the decision-maker |
| 9 to 13, no weak gate | Borderline | Introduce, stating the weak criteria plainly |
| 0 to 8, or any weak gate | Not yet | Leave the owner a list of what to check |
The scheme is a partner aid built for this page. SourceX does not score companies this way, and a total is not a forecast of anything.
The nine criteria, with strong, borderline and weak answers
The first three criteria apply to any company. The middle five are specific to action-space constraints: they test whether the limits on what staff could do were recorded, or only described. The last confirms who can say yes.
| Criterion | Strong (2) | Borderline (1) | Weak (0) |
|---|---|---|---|
| Company size (gate) | Clearly 50+ full-time employees at peak | Near 50, with many contractors to exclude | Under 50 full-time employees |
| Operating history | Five or more years of records in the current systems | Two to four years, or a recent helpdesk migration | Under a year of retained records |
| Rights (gate) | Company holds its own tickets and payment logs | Outsourced provider holds tickets, or customer terms limit reuse | Records controlled by a vendor with no clear rights |
| Restricted actions | Named list: refunds, credits, cancellations, price overrides | "Bigger refunds need a manager" | No restricted actions anyone can name |
| Enforcement | Software blocks the action for the role | Mix of software blocks and trained rules | Rules exist only in training material |
| Escalation records | Proposal, escalation and approval each logged | Approvals logged, proposals not | Escalations happen in chat or by phone |
| Linkage | Ticket ID carried through to the approval and the refund ID | Links exist for recent years only | Refunds cannot be traced to tickets |
| Configuration history | Each threshold change dated, old values known | Current values known, changes roughly remembered | Nobody knows what the limits used to be |
| Authorized contact (gate) | CEO named, with the COO or head of customer operations involved | Owner named but not yet aware | No one can authorize a discussion |
The enforcement row matters because research benchmarks draw the same line. τ-bench gives agents a domain policy and notes that some rules are enforced by the software while others depend on the agent applying them correctly. Records of both kinds can be useful, but they show different things: a blocked button proves the limit held, a trained rule shows whether people kept it.
Payment software makes strong answers easier to recognize. Stripe documents a tiered setup in which tier 1 agents get a role with refund permission removed (custom roles are in private preview), and its two-party approvals, in public preview, can hold a refund above an amount until a different team member approves it. A company using controls like these, in any system, is likely to score well on enforcement and escalation records.
Scoring three fictional support desks (Illustrative)
All three companies are fictional, and the scores are invented to show how the scorecard reads.
| Criterion | 210-person payments software firm | 130-person online retailer | 45-person digital agency |
|---|---|---|---|
| Company size | 2 | 2 | 0 |
| Operating history | 2 | 1 | 2 |
| Rights | 2 | 1 | 2 |
| Restricted actions | 2 | 1 | 1 |
| Enforcement | 2 | 1 | 0 |
| Escalation records | 2 | 1 | 0 |
| Linkage | 1 | 1 | 0 |
| Configuration history | 1 | 1 | 0 |
| Authorized contact | 2 | 1 | 2 |
| Total | 16, strong fit | 10, borderline | 7, not yet (size gate) |
The payments firm blocks refunds above $500 for tier 1 in its billing tool, logs every approval, and lost some linkage in a 2022 helpdesk move. The retailer's support runs through an outsourced provider, limits are mostly trained, and approvals are logged but proposals are not. The agency has good owners and rights but is too small to qualify, so its score ends there. The graphic on this page plays the payments firm's score: nine ticks and a needle that settles at 16 of 18.
Five questions that move a score
Ask these of the head of support or operations and write down answers, not files.
- Which actions are restricted by role? A concrete list moves "restricted actions" to strong. "Only managers can do the big stuff" stays borderline.
- Is the restriction enforced by the software or only by training? This decides the enforcement score directly.
- When someone cannot act, what do they do, and is it logged? If the honest answer is "they message a manager on chat", escalation records score weak and the opportunity is mostly theoretical for now.
- Have the limits changed, and is the old configuration known? A threshold that moved from $250 to $500 last year changes which escalations were required. Dated changes score strong.
- Who owns these records and can authorize a licensing discussion? The COO or head of customer operations usually owns them, with finance involved because refunds move money; the CEO authorizes the discussion.
Before you ask, it helps to confirm the client is comfortable being introduced at all; see documenting client consent for a referral. For company-level basics that apply to every topic, the company qualification checklist is shorter.
Where the scorecard stops
The scorecard reads answers; it cannot verify them. It does not show how many escalations carry complete records, whether customer data can be handled, or whether any buyer wants this task type. Data companies do build business environments around permission models (Toloka's agent environments page, checked October 18, 2026, describes mockups that replicate real tool schemas, workflows and permission models), but that is evidence of category interest, not of demand for a given company's tickets.
The company test itself comes from the program terms: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
If the score is borderline because records are patchy, the evidence gap analysis shows how to describe each gap. The wider record family is set out under support escalation processes, and a business introducer's guide to operational data licensing covers the conversation with the owner.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client scores 9 or more with no weak gate, register as a partner, confirm the company against who qualifies, and read the program terms before you introduce the decision-maker.