Medical-device RMA intelligence

The agent layer above your RMA queue.

Seriscope reads every return the moment a unit lands — matching the serial against warranty and recall records, scoring the order for fraud patterns, and writing the disposition: refund, replacement, repair, or recall. Routine touchpoints stay in your QMS. The decision moves up here.

Open a return See pricing

Sits on top of Trackmedium, QT9, RMAPortal, Salesforce, ReverseLogix
Constrained against Part 806, ISO 13485, 21 CFR Part 820
Same logic at 4 a.m. Saturday and 2 p.m. Tuesday

Capabilities

Three guardrails built into the routing.

The decision is constrained against the regulatory frame your returns live in. Not bolted on after the fact.

Compliance guardrails

Part 806, ISO 13485, and 21 CFR Part 820 are part of the decision.

Regulatory constraints are hard-coded into the routing logic — not added as a post-hoc reconciliation on the way to the audit trail.

Each disposition is logged with the inputs that produced it.
A constraint that fails the read is louder than a constraint that passes.
Risk class maps to disposition class — a higher-risk action cannot land in a lower-risk lane.

Recall watch

A flagged serial hard-routes. Refund and replace are not reachable.

Part 806 recall files are ingested as a first-class input. The moment a serial matches, the recall lane owns the decision.

Recall watch is a continuous ingestion process, not a periodic sweep.
Refund and replacement paths are unreachable from a matched recall read.
The recall-flagged unit is logged against the matching campaign file.

Human-in-the-loop approval

A flagged disposition does not close the loop without an approver.

Every flagged disposition — recall hit, fraud hold, policy conflict — is written to the approval queue and waits on a human reviewer of record.

Standard dispositions route through automatically.
Flagged dispositions appear in the pending-review queue for sign-off.
The audit trail records the approver, the time, and the rule that produced the hold.

Core flow

One read per unit. Five steps to a disposition.

Each return note moves through the same pipeline. The order matters — a recall match at step 3 arrives before a refund eligibility check at step 5.

RMA intake
The return note arrives.
A unit lands in the queue. Serial, customer, channel, fault class are extracted.
AI disposition
The agent reads the return.
Warranty window, fault history, and ordering patterns are scored against the current rules.
Recall diff
Part 806 files are diffed against the serial.
A match hard-routes the unit to the recall lane; refund and replace lanes are unreachable from that path.
Compliance check
Regulatory constraints constrain the choice.
ISO 13485, 21 CFR Part 820, and the channel-specific frame gate the lane a disposition can land in.
Approval queue
Flagged dispositions wait on a reviewer.
Standard dispositions close the loop. Flagged dispositions — recall hits, fraud holds, policy conflicts — surface in the approval queue.

Internal reference

Competitor positioning and segment context sit with the operator team.

The comparison context — how this product lines up against Trackmedium, QT9, RMAPortal, Salesforce, and ReverseLogix — is held in the internal-reference area alongside the LinkedIn outreach template and the segment-channel briefs. Those pages are reachable from the site footer; they are not linked from the public surface.

Try it

Open a return, or scope the pricing.

Both end at the same agent — one through a single unit, one through the subscription details.

Open a return See pricing