Skip to content
ServiceRecord

Benefit Channel integration spec

This is the model for offering ServiceRecord as a sponsored member benefit. It is written to be reviewable by a sponsor's benefits, legal, and security teams. Where something is set per engagement rather than fixed, it says so.

SCOPING DOCUMENT — commercial terms and rollout are finalized per engagement before launch.

1. What the member experiences

A sponsored member reaches ServiceRecord through a co-branded access path and uses the exact product any visitor uses: paste or upload a VA letter, get a grounded, cited decode for free. Sponsorship does not change the analysis, unlock a different tier, or add an account. The optional $25 Prep Pack is either folded into the sponsorship (free to the member) or left as the member's own optional purchase — a per-engagement choice.

2. Eligibility & access model

The access path is chosen to fit the sponsor, in rough order of simplicity:

  • Sponsored link. A co-branded URL the sponsor distributes through its own member channels. Simplest to launch; access is by possession of the link.
  • Access code. A sponsor-specific code a member enters once, held in session only. Adds light gating without collecting identity.
  • Eligibility check via the sponsor. For sponsors that require it, a member verifies eligibility on the sponsor's own system and is redirected in. ServiceRecord receives a signed, opaque “eligible” assertion — never a roster, name, or member ID.

Built today: the public tool and co-branded entry. Access codes and eligibility redirect are per-engagement integrations, not yet implemented in this repository.

3. Co-branding

Co-branding is limited to a “Provided as a benefit by [Sponsor]” treatment on the sponsored entry point. The decode itself, the charter, and every safety guarantee remain ServiceRecord's and are never skinned away — a sponsor cannot alter, soften, or brand over the “information, not advice” posture or the refusals.

4. The data boundary (non-negotiable)

  • Member letters are read once, in memory, and discarded — same as the public tool.
  • The sponsor never receives a document, a name, an email, an IP, or any record of who used the tool.
  • ServiceRecord does not build a roster and does not tie any event to a member.
  • The only thing that crosses back to the sponsor is aggregate, de-identified usage — described next.

5. Aggregate reporting schema

Sponsor reporting is built on the same privacy-first instrumentation the public product uses (see Privacy §4): plain counts of whitelisted funnel events, with no identifiers. A monthly report to a sponsor contains, at most:

  • decodes_completed — count of analyses run.
  • by_letter_type — counts per document type (rating decision, debt letter, …).
  • prep_pack_offered / prep_pack_unlocked — funnel totals.
  • period — the month covered.

No field in the report can be resolved to a person. Reports are aggregated to a minimum count threshold to prevent re-identification in very small member populations.

6. Billing

The Benefit Channel is billed per eligible member per month (PMPM) and invoiced to the sponsor — not through per-veteran Stripe checkout. Members are never charged for sponsored access. Exact PMPM pricing, minimums, and term are set per engagement. No percentage of any member's benefits is ever charged, under any structure.

Built today: per-veteran Stripe checkout for the standalone $25 Prep Pack. PMPM invoicing is a commercial and billing-integration step handled per engagement; it is not implemented in this repository.

7. Security & compliance posture

  • Documents transit over TLS, are processed in memory, and are not stored, logged, or backed up.
  • When the AI engine is enabled, analysis is performed under provider terms that do not permit training on the data.
  • No member accounts means no credential store tied to the sponsor.
  • DPA, security questionnaire, and any sponsor-specific compliance review are handled during scoping.

8. What we need from a sponsor to start

  • The audience and rough size of the eligible member population.
  • The preferred access model (sponsored link, access code, or eligibility redirect).
  • Whether the Prep Pack is folded in or left optional to the member.
  • A point of contact for the agreement, DPA, and monthly aggregate report.

To scope a Benefit Channel engagement, email partners@servicerecord.example [OWNER: set the real inbox before launch].

ServiceRecord is not a law firm and not accredited representatives. Information, not advice. Not affiliated with the U.S. Department of Veterans Affairs.