Skip to content
MirrorFirm

Which record types should I request for an escalation task pack?

A checklist of record types that give an agent enough context to decide whether to escalate, who should receive the case, and what the handover should contain.

Ask for these record types so that each task can be solved, and failed, from the information in the environment.

- Cases or applications with requested amount, product, status and current assignee. - Party and facility records that allow aggregate exposure to be calculated. - Authority matrix rows by role, product and condition, with effective dates. - Reviewer records covering grade, team, availability, conflicts and delegations. - Policy and exception documents, including at least one superseded version. - Case notes and attachments, with some gaps and contradictions seeded on purpose. - Prior escalation records showing reason codes, returns and outcomes. - Audit events that record each state change with actor and timestamp.

Also ask for an expected-outcome file per task, naming the correct target role, the acceptable reason codes and any required content in the handover note. Without it you will need to write your own grading rules, which is slower and less consistent.

Agree the exact set during pilot scoping, since your own system may hold some of these under different names.

Requesting the right record types up front avoids a pack that tests routing without the context needed to route correctly.

Audience:
Agent developers
Content type:
Checklist
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Credit escalation