Insights

What the QMSR Changed for Complaint Handling on Your Support Line

Table of Contents

The Quality System Regulation is gone. On 2 February 2026 the QMSR replaced it, amending 21 CFR Part 820 to incorporate ISO 13485:2016 by reference, and Part 820 was hollowed out in the process — Subparts C through O now read Reserved.

If you run device support in house, your quality function has been living with this since February. If you outsource tier-1, there is a reasonable chance the change reached your quality management system and stopped there.

Start with what did not change

The tempting version of this story is that FDA rewrote complaint handling. It didn’t, and building a support program on that assumption would send you looking for problems that aren’t there.

Put the old 21 CFR 820.198 next to the new 820.35(a) and the substance mostly survives. Complaints involving the possible failure of a device, labeling or packaging to meet specifications still have to be reviewed, evaluated and investigated. You can still decline to investigate where a similar complaint has already been investigated — and the new text is slightly firmer than the old one about documenting why. The list of what a complaint record must contain came across essentially intact.

What moved is the location. The complaint handling process now lives in ISO 13485 clause 8.2.2, incorporated by reference. The records stayed in federal regulation, at 820.35.

That sounds like bookkeeping. It has two consequences that land directly on a support line.

Three things left the federal text

These provisions were in 820.198 and are not in 820.35(a):

  • The requirement that complaints be received, reviewed and evaluated by a formally designated unit.
  • The requirement that, where no investigation is made, the record include the name of the individual responsible for that decision.
  • The requirement that complaints reportable under Part 803 be promptly reviewed by a designated individual and kept in a separate portion of the complaint files.

A provision leaving the Code of Federal Regulations is not the same as an obligation ending. Clause 8.2.2 carries its own requirements, and FDA has characterized the QMSR as substantially similar to what it replaced. The practical difference is that the answer to “what are we required to do here” is now partly in a standard you have to buy rather than a regulation anyone can read for free.

Which matters when the people doing the work sit at another company. A vendor’s agent cannot look up the rule.

The part that stayed, and it touches the phone

Here is 820.35(a) on what a complaint record must contain. For complaints reportable to FDA under Part 803, complaints the manufacturer determines must be investigated, and complaints investigated regardless, the record must include:

  1. The name of the device
  2. The date the complaint was received
  3. Any unique device identifier or universal product code, and any other device identification
  4. The name, address, and phone number of the complainant
  5. The nature and details of the complaint
  6. Any correction or corrective action taken
  7. Any reply to the complainant

Item four is the one worth sitting with. A patient calls about a device that isn’t working the way they expect. The agent is helpful, walks them through it, resolves the call, logs a clear note — and captures a phone number, because that is what a support ticket needs.

Nobody asked for an address. If that interaction turns out to have been a complaint, the record has a hole in it, and the hole is discovered later by someone who wasn’t on the call and can’t go back for the answer.

This is not a training problem so much as a form-design problem. The fields an agent fills in at the moment of contact decide what your complaint record can contain, and a support tool configured for support tickets will not ask for the things a complaint record needs.

The provision that reaches into your vendor

If one regulation should shape how a manufacturer contracts outsourced device support, it is 21 CFR 803.17. It requires a manufacturer to develop, maintain and implement written MDR procedures covering, among other things:

“Internal systems that provide for: (1) Timely and effective identification, communication, and evaluation of events that may be subject to MDR requirements; (2) A standardized review process or procedure for determining when an event meets the criteria for reporting under this part.”

Read identification carefully. The first opportunity to identify a potentially reportable event is usually the first time a human being hears about it, and for most device manufacturers that is a phone call or a chat. If that conversation happens at a vendor, your identification system runs through their agents, their tooling and their escalation path, whether or not the procedure acknowledges them.

The clocks that follow are unchanged. Under 803.50, a manufacturer reports within 30 calendar days of becoming aware of information reasonably suggesting that a marketed device may have caused or contributed to a death or serious injury, or malfunctioned in a way that would be likely to do so if it recurred. Under 803.53, five working days where the event necessitates remedial action to prevent an unreasonable risk of substantial harm to the public health.

Worth stating plainly, because vendors are occasionally vague about it: those obligations bind manufacturers, importers and user facilities. A contact center is none of the three. Nothing your support vendor does or fails to do moves the obligation off you, and any vendor who implies otherwise is selling you something that does not exist. Our own medical device technical support work is built on the opposite premise — agents recognize and escalate, and formal reporting stays inside your quality system.

The question nobody can answer for you

Under 803.3, a manufacturer becomes aware when “any of your employees becomes aware” of a reportable event.

An outsourced agent is not your employee.

We looked for a primary source resolving what that means for the awareness clock when the call lands at a vendor, and did not find one. So this post is not going to tell you the answer, and you should be wary of a vendor who offers one — it is a claim about your regulatory position, not theirs.

What it does mean is that the handoff point has to be defined by your procedures rather than inferred from the regulation. When does information reaching an agent count as reaching you? What has to happen, and in what time, for that to be true? Those are answerable questions, and they are answered in a procedure and a contract rather than in the CFR.

Put it to any vendor you are evaluating. The good answer is a defined path with a time attached. A vendor who has never been asked will tell you that in the first sentence.

Four things worth checking this month

Your complaint procedure’s citations. The December 2025 technical amendments repointed roughly 162 references across FDA’s device regulations from 820.180 and 820.198 to 820.35. If your own procedure, or the work instruction your vendor’s agents were trained on, cites 820.198, it cites a section that no longer exists. The requirements mostly still hold, which is precisely why nobody notices.

What your support tool captures. Against the seven items in 820.35(a), field by field. Address is the one most commonly missing.

Where your MDR procedure’s identification system actually begins. If the procedure describes internal intake and your intake is outsourced, the document and the operation have drifted apart.

How a procedure change reaches an agent. When your quality team revises something, what is the path to the work instruction the vendor’s agents follow, and how long does it take?

How we approach it: Agents are trained on your device, your protocols and your escalation rules rather than a generic support script — how that training works is written up separately. Complaint details are captured in set form fields built to the record your procedure requires, not left in free-text notes. Potential adverse events and safety signals are escalated immediately to your quality and regulatory teams under your procedures, and formal reporting stays inside your quality system where it belongs. When you change a procedure, the change is updated in agent work instructions and briefed to agents before it takes effect, with a record of when each agent was briefed.

This describes what published federal regulations say and is not legal or regulatory advice. Your obligations depend on your device, your quality system and your role under Part 803, and your regulatory function should determine them.

The short version

The QMSR did not rewrite complaint handling. It moved the process requirements into a standard you have to buy, kept the record requirements in 820.35, and left a lot of procedures citing a section that no longer exists.

For anyone whose device support is outsourced, the useful consequences are narrow and checkable: whether the fields your agents fill in can produce a complete complaint record, where your MDR identification system actually starts, and what your procedures say happens when information reaches somebody who does not work for you.

Our medical device technical support page covers how these programs are built and where the boundaries sit, and we’ve written about why device support isn’t help desk support. The pharmaceutical lane works differently and is worth reading separately if you run both. Or tell us how your device calls are handled today and we will work through the four checks above with you.