A business with years of support records may be worth a conversation: eleven call prompts that take a public clue to a permission ask, or to a polite close

Short answer

A public sign of long support history, such as a help center with articles dated a decade back, is a reason to ask someone you already know a few questions. It proves nothing about whether tickets were kept, who owns them or whether anyone wants them. Use the clue to open a metadata-only conversation with a known contact, confirm the facts with whoever administers the support system, ask whether the CEO wants a conversation, and close politely when the answers show no fit.

Visual briefFull-size diagram
A four-step path from a public support clue to confirming facts with the system administrator, asking whether the CEO wants a conversation and routing the introduction, with exits at each step to park or close.
The conversation path behind the eleven prompts. Every step can end politely.

For a channel partner's business development lead, the useful skill is not spotting clues. Clues are everywhere. It is turning one into three or four well-ordered questions for a person who trusts you, and knowing which answer ends the thread.

What a public support clue can date, and what it cannot

Every clue has a date and a limit. Write both down before you mention it to anyone.

Public clueWhat it datesWhat it cannot tell you
Help-center articles with visible publish datesWhen the company started documenting support publiclyWhether tickets from those years still exist
An archived snapshot of the help centerThat a public support site existed on the capture dateWhat sat behind the login, or what was later deleted
Community forum threads going back yearsThat customers asked questions in publicAnything about the private ticket system, which is a separate record
A "support since 2008" line on the websiteWhat the company says about itselfWhich system, which owner, what was kept through each migration

The Internet Archive's help pages explain how to open a dated snapshot in the Wayback Machine: enter the page's URL, choose a year, then a date and time. That gives the clue a date you can cite instead of a vague "they've been around a while". A 2013 snapshot of a help center tells you the company published support articles in 2013. It does not tell you a single 2013 ticket survived.

A clue also needs a relationship path, and the path matters more. Who do you already know at the company, in what capacity, and would they take your call? A clue with no person attached is a note in your file, not a lead. A bought contact list is not a path either: it is someone else's undated guess about a stranger.

The support-history conversation prompts

Eleven prompts in four stages. Use them in order, in your own voice, and stop at the first answer that ends the thread. Nothing in them asks for a file, a screenshot, a login or a customer name.

#PromptAn answer that moves it forwardAn answer that stops or parks it
1"I saw your help center has articles back to 2014. Has support been in-house all that time?""Yes, our own team since about then""We moved it to an outsourcer years ago" (park and ask who holds the tickets)
2"I introduce companies to a data licensing program, so I'm asking for a reason. Could I ask a few questions about how support records are kept? Nothing to send.""Sure, go ahead""Not something we'd consider" (close)
3"Which system logs your tickets, and has it been the same one since you started?"One system, or migrations with history carried across"We switched last year and started fresh"
4"Who administers it? They'd know how far back closed tickets actually go."A named administrator who can confirm"Nobody really owns it" (park)
5"As a rough range, how many tickets a year?"A range with a basis, such as monthly reportsNo idea at all (fine; mark it unknown)
6"Are these requests from your own customers, or support you deliver for clients?""Our own customers""Mostly for clients, under their contracts"
7"At its peak, roughly how many full-time employees did the company have, leaving out contractors?"50 or moreA clearly smaller figure
8"Would your CEO want a short conversation about licensing internal records like these? I'd only pass along a summary the CEO approves.""Worth asking""Not now" (park with no follow-up)
9"Who should raise it with the CEO: you, or would you rather I did?"A named person and a rough dateSilence (park)
10No fit: "Thank you. From what you've told me it doesn't match what the program looks for, because of [the reason]. I'll leave it there."Not applicable: this prompt ends the threadIt ends the thread
11Park: "Understood. If the CEO wants to look at it later I'm glad to help, and I won't chase you."The contact may come back on their ownIt ends the thread for now

Prompt 4 exists because the person you know may not see the whole archive. Some helpdesks move old closed tickets out of everyday views. Zendesk, for instance, says it generally archives tickets 120 days after they are closed; archived tickets disappear from views but can still be reached through search, direct links and the API. An agent who has never scrolled past last spring may honestly say "we only keep a few months". The administrator knows better.

Prompt 6 is the one that most often decides fit. SourceX's published screen treats material that belongs to a company's clients as usually not a fit, so support delivered on behalf of clients, inside client contracts, is a different conversation from a company's own customers writing in.

Observed, told, confirmed: keep the three apart

Every fact you collect carries a label, and the label decides what you can repeat.

  • Observed. You saw it in public. Keep the URL and the date. "Help center articles dated from 2014, seen 2026-10-27."
  • Told. A named contact said it. "The COO says the support team has been in-house since 2015."
  • Confirmed. The person who runs the system said it, and the CEO approved the wording for the summary. "Closed tickets retained since 2015 in one helpdesk, per the support administrator."
  • Inferred. Your own reasoning. It stays in your notes and is never forwarded as a fact.

Only confirmed facts go into anything a CEO is asked to approve. Told facts can shape your next question. Inferred ones shape nothing outside your own file.

Three companies, three outcomes (Illustrative)

Illustrative. Generic companies with invented facts; nothing here describes a real company or outcome.

FactCase 1: regional software firmCase 2: equipment-rental companyCase 3: insurance services firm
Public clueHelp-center snapshots from 2012 (observed)Community forum threads from 2015 (observed)"Support since 2010" on its website (observed)
Relationship pathNobody you know works thereThe COO, a client of your firm for six yearsThe CFO, a client of your accounting practice
Support system and yearsUnknownOne helpdesk since 2015, closed tickets kept (confirmed by the administrator)Closed tickets deleted after 18 months under its retention policy (confirmed by the administrator)
Whose requestsUnknownIts own customers (confirmed)Its own customers (told)
Full-time headcount at peakA LinkedIn range only (observed, unverified)140, in 2022 (told by the COO)260 (told by the CFO)
CEO interestNot askedThe COO will raise it this month (told)Not asked
RoutePark: log the clue and its date; no cold outreachDraft a summary for the CEO's approval, then prompt 8Close with prompt 10: there is no multi-year archive

Case 3 is the useful lesson. The public clue was the strongest of the three, and the company was the right size, yet a retention policy had quietly ended the history the clue suggested. Only prompt 4 found that out.

Route only plausible introductions, with permission

An introduction is plausible when four things line up: the records are the company's own, an administrator has confirmed years of retained tickets in a known system, full-time headcount reached 50 or more at peak with contractors excluded, and the CEO knows about the idea and wants a conversation. Short of that, park or close.

When it does line up, register, agree the summary with the CEO, and let the company apply through your partner link. Your own paperwork comes first: no submission goes in until you have signed the SourceX Channel Partner Agreement, and a partner who signed it back when it carried the longer Channel Partner Non-Circumvention and Non-Disclosure Agreement name keeps the version they signed. A support desk with a long history may have crossed other advisers' paths too, so know how credit works: it goes to one partner per company, the one whose valid introduction came first inside the 90-day attribution window, and it is settled when the company files a verified application. A duplicate earns nothing, and the company counts as one if SourceX already holds an application, relationship, lead, account or email correspondence with it.

What stays unknown until SourceX reviews the company: whether its tickets match a current data need, whether its customer contracts limit reuse, and how personal details in the tickets would be handled. None of those is yours to settle on the phone. For what makes one ticket more informative than another, see support tickets with useful resolution context; for the record type itself, the helpdesk ticket threads dataset page.

Where support clues mislead

  • Help centers outlive helpdesks. Articles can move to a new platform with their dates intact while the ticket history does not. If a migration comes up at prompt 3, the helpdesk migration playbook covers the timing.
  • Retention policies end history quietly. A deletion rule can cap the archive at months, whatever the website says. How long companies keep tickets, and why, is covered in how long to keep support tickets.
  • A forum is not a ticket system. Public threads say customers talked in public, nothing more.
  • Growth is not depth. A support team that doubled last year signals volume, not years; the support-team growth worksheet handles that signal.
  • A friendly contact is not the CEO. Enthusiasm at prompt 2 says nothing about prompt 8.

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.

When the prompts end with an administrator's confirmation and a CEO who wants to talk, register for a partner link, compare the company with who qualifies and read the program terms before the summary goes to the CEO.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is an old public help center enough reason to contact a company I have no relationship with?

No. It is a dated note about what the company published, not a path to its CEO. Log the clue with its date and wait until someone you already know there can be asked.

Why ask for the support administrator instead of trusting what an agent says?

Agents see their queues, and many helpdesks move old closed tickets out of everyday views. Zendesk, for example, generally archives tickets 120 days after closing while keeping them searchable, so the administrator is the person who knows how far back the history really goes.

Can I ask the contact for a few example tickets to judge quality?

No. Tickets carry customers' names and requests, and partners stay at metadata level: which system, how many years, roughly how many tickets, who owns them. Quality is assessed in SourceX's review, after the company decides to go ahead.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. support.zendesk.com/hc/en-us/articles/4408887617050-About-ticket…
  4. help.archive.org/help/using-the-wayback-machine

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment