AccessSeller-approved · under NDA

This workspace is documentation-first. Buyers evaluate the data dictionary, schema, provenance and quality reporting before any sample is produced, and samples are de-identified. Raw records, credentials and system access are never provided here.

OverviewSaaS
Reference
#2895
Region
United States
Size band
100–500 employees
Years operating
8
Continuous history
5 yrs
Volume
128,000+ records
Score
76/100
Status
LISTED
Data dictionary3 record families
  • Support Ticketsdocumented
  • Engineering Workflowsdocumented
  • Case Managementdocumented
Schema and keysJoin surface

Systems of record

ZendeskJiraLinearGitHub

Cross-system connectivity

ZendeskJiraLinear

Records join on stable operational keys, allowing a single case to be traced across systems from initiation to financial close.

SampleDe-identified · post rights review

Samples are produced only after the rights review below is complete and the de-identification plan is agreed. A sample is a structured extract with entity and person identifiers pseudonymised, free-text redacted where required, and volumes capped.

Sample not yet released — pending rights review

ProvenanceHow the data was generated

All records were generated as a by-product of the seller's own operations inside systems the seller controls. No scraped, purchased or third-party-licensed corpora are included.

Workflow families captured

  • Tier-1 to tier-3 escalation
  • Incident command and postmortem
  • Change review
  • Implementation milestone tracking
RightsDiligence states, not legal advice
  • OwnershipREADY

    Company-generated operational records in owned tenants.

  • Source systemsREADY

    Zendesk, Jira, Linear, GitHub.

  • Third-party dataREVIEW REQUIRED

    Vendor support threads.

  • Customer / client dataREVIEW REQUIRED

    Customer environment details in tickets.

  • Employee dataREVIEW REQUIRED

    Approver identities appear in workflow audit trails.

  • Potential PIIREVIEW REQUIRED

    Names and work contact details appear in free text.

  • Contract restrictionsREVIEW REQUIRED

    Customer MSAs restrict disclosure of ticket content.

  • Licensing permissionsNOT VERIFIED

    Pending rights review.

  • Retention periodREADY

    5 years retained; no scheduled destruction.

  • Geographic restrictionsREADY

    United States operations only.

  • Intended AI useREVIEW REQUIRED

    Seller prefers training plus evaluation, no resale.

  • De-identification requirementsREVIEW REQUIRED

    Entity and person pseudonymisation required pre-sample.

PrivacyDe-identification plan
PII risk
MODERATE
De-identification difficulty
MODERATE
Licensing readiness
REVIEW REQUIRED

Entity and person pseudonymisation, suppression of contact fields and review of free-text comment threads are applied before any extract leaves the seller environment.

QualityReported and verified
Volume
MODERATE
Historical depth
HIGH
Workflow complexity
HIGH
Cross-system
MODERATE
Uniqueness
MODERATE
Data quality
HIGH
Outcome labels
MODERATE
Workflow documentationAgent-relevant
01

Tier-1 to tier-3 escalation

02

Incident command and postmortem

03

Change review

04

Implementation milestone tracking

Applicable AI use cases

Support deflectionEvaluation benchmarksVertical AI agents
Technical documentationDelivery
Delivery format
Structured extracts (Parquet / CSV) + documentation
Transfer
Seller-controlled secure transfer, audited
Refresh
Negotiable: one-time, quarterly or annual
Access controls
Named recipients under NDA
Licensing termsSeller preference
Preference
Non-exclusive, no-resale license
Potential data value
Assessment available after diligence
Qualified buyer interest
11

Terms are negotiated per buyer. SentryRights does not represent any figure as a valuation and does not represent that this asset is licensable before rights review completes.

Demo data — illustrative sample listings, not live marketplace records