L3 support

L3 support is the highest tier in a support escalation model: the specialists, engineers, or policy owners who handle cases that L1 and L2 cannot resolve, such as a system defect or a case with no existing procedure.

Where L1 and L2 work from documented procedures, L3 often means writing the procedure for the first time, or fixing the underlying system issue that caused the case. In financial services, L3 frequently includes compliance or legal input, because a case reaching this tier may set precedent for how similar cases get handled going forward.

What separates L3 support from L2 in financial services?

L2 works within existing procedures, even complex ones. L3 handles cases where no existing procedure applies, where a system is behaving incorrectly, or where the resolution requires a policy decision rather than executing an existing one. In a regulated firm, an L3 case often gets referred to compliance or legal because the outcome could set a pattern other similar cases will follow. This is also usually where a new procedure gets documented and fed back down to L1 and L2 for the next time a similar case appears.

Frequently asked questions

Does an AI agent ever operate at L3?

Rarely, and typically not to make the final call. An AI agent can surface the case, summarise what is known, and flag why existing procedures do not cover it, but the judgment or policy decision at L3 usually needs a human with the authority to set precedent.

How often should an L3 resolution get turned into a new L1 or L2 procedure?

As a rule, every time. An L3 case that stays a one-off means the same gap in coverage reappears next time, whereas documenting the resolution closes it for future cases at a lower tier.

Is L3 support the same as engineering support?

Not always, though they overlap. Some L3 cases need engineering (a system defect); others need policy or compliance input with no code involved. L3 is best defined by no existing procedure applying, rather than by which department handles it.