Skip to content

farstic/ai-servicenow-architect / .claude/skills/fso-insurance-specialist

fso-insurance-specialist

Verified

Mandatory gateway for FSO (Financial Services Operations) insurance — insurance policy, change coverage, claims, FNOL, adjuster, reserve, SIU, underwriting task, life servicing, Document Processor, Complaint Management, Customer Lifecycle, KYC.

FileKindSize
EXAMPLES.mdmarkdown22.5 KB
SKILL.mdskill md87.1 KB

EXAMPLES.md

View on GitHub
# FSO Insurance Specialist v1.0 — Worked Examples

Three examples: Examples 1 and 2 take the Verdict A path — Example 2 shows where one new field would make it B — and Example 3 the Verdict C halt. Each example shows the full 5-Part Constraint Envelope output for a realistic dispatch input. Read these alongside `SKILL.md` to understand the gateway's output format and depth. Client names are fictional.

---

## Example 1 — Verdict A (Fully Baseline)

### Dispatch input

**Source:** Chief Architect, routing from a user request.
**User request:** *"Our personal auto policyholders should be able to ask for a coverage change from the portal; a policy processor reviews it, sends it to underwriting when unsure, we send a quote, the customer accepts, we update the policy and send the new documents. We also need to see how many of these are rejected by customers."*
**Module:** FSO — Personal Lines Servicing (`sn_ins_policy_b2c`), Personal Lines Underwriting (`sn_ins_underwrite`)
**Customer model:** B2C consumers
**Volume:** ~12K policy service cases/year
**Sensitivity:** PII (policyholder identity, address, vehicle)

### Gateway Response

```markdown
# FSO Insurance Specialist Gateway Response — portal-initiated change-coverage requests on personal auto policies with underwriting referral and quote acceptance

**Domain Expert:** FSO Insurance Specialist v1.0 (CSM Specialist co-fires: Consumer Service Portal + consumer model)
**Release family:** Australia (Store-app versions to be confirmed on instance)

---

## Part 1 — OOB Process Map

This is the shipped change-coverage process of Personal Lines Servicing, end to end:

1. **Request** — the consumer submits the policy service from the Consumer Service Portal (plugin `com.glide.service-portal.consumer-portal` must be active) or a contributor/processor submits from a consumer record or an interaction in the FSO Workspace. A case is created by request type on the Auto Policy Case table in state New and routed by assignment rules.
2. **Initiate and review** (playbook stage) — requester/contributor completes the change details and submits for fulfilment; the predefined change-coverage flow (Workflow Studio) triggers and assignment rules route the generated tasks.
3. **Processor review** — the processor approves (quote sent to the customer/contributor), rejects (case closed), or creates an underwriting task. The task lands on `sn_ins_underwrite_b2c_task` and is worked by a personal underwriter (Approve / Reject).
4. **Customer acceptance** — the customer accepts or rejects the quote; rejection is tracked as "cases rejected by customer".
5. **Fulfillment** — the processor updates the policy record, sends the updated policy documents (Document Processor outbound documents) and closes the change-coverage task; the case ends in state and stage Closed Complete.

Baseline notifications are not documented for this flow (the quote and document sends are described functionally only).

Role gates: `sn_ins_policy_b2c.auto_policy_processor` works the case; `sn_ins_policy_b2c.contributor` (paired with a CSM Contributor user role) submits on behalf of managed accounts; `sn_ins_underwrite.b2c_underwriter` works the underwriting task; `sn_bom_document.b2c_agent` works document tasks.

(citation: markdown/financial-services-operations/request-review-approve-change-coverage-request-workflows.md, markdown/financial-services-operations/submit-ins-policy-service-request.md, markdown/financial-services-operations/work-ins-policy-case.md, markdown/financial-services-operations/work-insurance-underwriting-task.md)

## Part 2 — Data Model Alignment

| Table | Label | Parent | Scope | Role in this design |
|---|---|---|---|---|
| `sn_ins_policy_b2c_base` | Policy Base | `sn_customerservice_case` | sn_ins_policy_b2c | Base of all personal-lines policy cases |
| `sn_ins_policy_b2c_service` | Auto Policy Case | `sn_ins_policy_b2c_base` | sn_ins_policy_b2c | The change-coverage case |
| `sn_ins_policy_b2c_task` | Auto Policy Task | `sn_bom_task` | sn_ins_policy_b2c | Processor tasks generated by the flow |
| `sn_ins_policy_b2c_policy_coverage_info` | Policy Coverage Info | not documented ("Info table") | sn_ins_policy_b2c | Requested coverage changes held until approval |
| `sn_ins_underwrite_b2c_task` | Underwriting Service Task (Personal) | `sn_bom_task` | sn_ins_underwrite | Underwriting referral |
| `sn_bom_auto_ins_policy` | Personal Auto policy | `sn_bom_ins_policy` → `sn_install_base_sold_product` | sn_bom | The master policy updated at fulfilment |
| `sn_bom_policy_coverage` | Policy Coverage | — | sn_bom | Master coverages, written only after approval |

Field lists and the full state/choice list of the case are **not documented** — documented states are New, Work in Progress, Closed Complete; verify on instance before any state-based logic. Info tables' parent is not stated.

Baseline ACL pattern: processor/viewer roles per case type (`sn_ins_policy_b2c.auto_policy_processor` / `.auto_policy_viewer`), Info-table writer role `sn_ins_policy_b2c.info_writer` contained in the processor role.

(citation: markdown/financial-services-operations/installed-with-ins-policy-ops.md, markdown/financial-services-operations/fso-core-insurance-tables.md)

## Part 3 — §1.1 Baseline-First Verdict

### Verdict A — Fully covered by baseline

Every requirement maps to shipped configuration: record producer for the portal form, the predefined change-coverage flow and case playbook, the underwriting task, quote acceptance in the playbook, outbound documents via Document Processor, and the Personal Lines Servicing dashboard indicators "cases rejected by customer" with the Policy Reject Reason breakdown. No new table, scope or state value.

(citation: markdown/financial-services-operations/personal-lines-servicing-dashboard.md, markdown/financial-services-operations/configure-ins-policy-ops.md)

## Part 4 — Routing Recommendation

**PROCEED — baseline configuration only.** Configuration checklist for the Technical Designer (design note, no code): import financial data → service definitions (servicing + underwriting) → record producer for the auto change-coverage form → review the predefined change-coverage flow in Workflow Studio → review the case playbook → CSM Configurable Workspace (processor, contributor, underwriter surfaces) → interceptor + record type selector entries → groups and assignment rules → SLA definitions → Document Processor outbound rules for the updated policy documents.

Co-fire: **CSM Specialist** (Consumer Service Portal, `csm_consumer`). Consults: **Licensing** (Personal Lines Servicing Store entitlement, Consumer Service Portal), **Security & GRC** (PII on the portal form), **Flow Designer Specialist** only if the shipped flow needs modification.

## Part 5 — Anti-Patterns to Block

- Do not create a quote table — the quote and its acceptance live in the playbook's Customer acceptance stage (citation: markdown/financial-services-operations/request-review-approve-change-coverage-request-workflows.md).
- Do not write coverage changes to `sn_bom_policy_coverage` while the case is open — use the Policy Coverage Info table and apply at fulfilment (citation: markdown/financial-services-operations/fso-core-banking-tables.md).
- Do not build an "underwriting case" — underwriting is a task on `sn_ins_underwrite_b2c_task` (citation: markdown/financial-services-operations/installed-with-fso-underwriting-ops.md).
- Do not grant `sn_ins_policy_b2c.contributor` to brokers without a CSM Contributor user role — it does nothing alone (citation: markdown/financial-services-operations/fso-combine-csm-industry-roles.md).

## Open Questions

- OQ-EV-1: Consumer Service Portal plugin active on the instance? (blocks self-service intake)
- OQ-EV-2: Is the policy record updated in ServiceNow only, or must the core policy administration system be updated at fulfilment? The docs describe a manual "update the policy record" — if the core system is the master, this becomes an Integration Specialist item (proposed default: manual in phase 1).
- OQ-EV-3: Exact flow and playbook record names — not documented; read from the instance.
```

---

## Example 2 — Verdict A (configuration of the shipped approval engine and Document Processor)

### Dispatch input

**Source:** Chief Architect, routing from a Discovery Output.
**User request:** *"Claims adjusters must not approve reserves above their authority. We have three adjuster grades with different limits per product (motor, property), and above the top grade the claims manager approves, then the head of claims for very large amounts. We also want every third-party bodily-injury claim to require a police report before the adjuster can settle."*
**Module:** FSO — Insurance claims (`sn_ins_gen_claim`) on Insurance Claims Core, Document Processor
**Customer model:** mixed
**Volume:** ~30K claims/year
**Sensitivity:** PII + injury data

### Gateway Response

```markdown
# FSO Insurance Specialist Gateway Response — tiered reserve/payment approval authority per adjuster grade and product, plus mandatory police report on bodily-injury claims

**Domain Expert:** FSO Insurance Specialist v1.0
**Release family:** Australia

---

## Part 1 — OOB Process Map

**Reserve / payment approval (Insurance Claims Core).** An adjuster creates a Claim Reserve or Claim Payment in the claim workspace. If `sn_ins_claim.reserve_approval` / `sn_ins_claim.payment_approval` are enabled, the subflow *Claim reserve approval flow* / *Claim payment approval flow* runs the decision table *Claim reserve and payment approval rules* with inputs Activity (Reserve/Payment), Product (insurance product model) and Amount; the output is the title of the persona that may approve. Within the adjuster's authority the record is auto-approved; otherwise an approval task appears in the manager's *My approvals – Reserves / Payments* list, and approval or rejection (with comments) writes system work notes. With `sn_ins_claim.reserve_approval_is_sequential` / `sn_ins_claim.payment_approval_is_sequential` = true *(citation: `markdown/financial-services-operations/insurance-claims-core-roles-and-properties.md`)* every next-level manager is notified in sequence; with false the request goes straight to the manager with authority for the amount.

**Required documents.** On FNOL submission the decision table *Insurance claims document rules* maps the case service definition to a document list definition; Document Processor creates a document verification task; list items flagged Mandatory block closure of the verification task until verified.

Role gates: `sn_ins_gen_claim.adjuster`, `sn_ins_gen_claim.manager` (approves above adjuster limit), `sn_doc_processor.agent`.

(citation: markdown/financial-services-operations/approval-engine-for-reserves-and-payments.md, markdown/financial-services-operations/insurance-claims-core-roles-and-properties.md, markdown/financial-services-operations/insurance-claims/add-document-list-definition-to-service-definition.md, markdown/financial-services-operations/doc-processor-associate-document-list-items-to-category.md)

## Part 2 — Data Model Alignment

| Table | Purpose | Scope |
|---|---|---|
| `sn_ins_claim_reserve`, `sn_ins_claim_payment` | Amounts under approval | Insurance Claims Core |
| `sn_ins_claim_coverage` | Coverage the reserve is set against | Insurance Claims Core |
| `sysapproval_approver` | Approval records | global |
| decision table *Claim reserve and payment approval rules* | Authority thresholds (Activity, Product, Amount → persona title) | Insurance claims |
| `sn_doc_processor_list` / `sn_doc_processor_list_item` | Police report as a mandatory list item for the bodily-injury service definition | sn_doc_processor |
| `sn_doc_processor_verification_task` | Verification task; Mandatory blocks closure | sn_doc_processor |
| `sn_ins_claim_injury` | Injury incident on the claim | Insurance Claims Core |

Not documented: how the persona title output is mapped to an actual approver user/group, and the exact property values — verify on instance.

(citation: markdown/financial-services-operations/insurance-claims-core-tables.md, markdown/financial-services-operations/components-installed-fso-document-processor.md)

## Part 3 — §1.1 Baseline-First Verdict

### Verdict A — Fully covered by baseline

The three-grade authority model is **rows of the shipped decision table** *Claim reserve and payment approval rules* (Activity × Product × Amount band → the title of the persona who may approve), with a persona title per adjuster grade and one for each of the two manager levels, plus `sn_ins_claim.reserve_approval_is_sequential` / `sn_ins_claim.payment_approval_is_sequential` = true for the manager → head-of-claims chain. The police-report rule is a **document list definition + a Mandatory list item bound to the bodily-injury service definition** through the *Insurance claims document rules* decision table, and the *Settle claim* step should sit after the document verification task — a playbook adjustment. All of these are configuration records on existing tables, their scripts included: no new field, table, scoped app or state value. The verdict becomes B only if OQ-EV-1 finds that persona titles cannot tell the three grades apart, so that the grade has to be held in a new field on the adjuster's user or group record: that field would be the one schema addition.

If the builder proposes an "adjuster authority" table, that is a §1.1 violation.

(citation: markdown/financial-services-operations/approval-engine-for-reserves-and-payments.md, markdown/financial-services-operations/insurance-claims/automating-other-claim-processes-using-decision-tables.md)

## Part 4 — Routing Recommendation

**PROCEED — dispatch to Technical Designer with constraints:** decision-table row design (Activity × Product × Amount band → persona title), the approver-title mapping mechanism (verify on instance), property settings, document list definition + Mandatory item for the bodily-injury service definition, playbook ordering of Settle claim after verification. **Flow Designer Specialist** if the approval subflows must pass an extra input (adding a decision-table input requires updating the subflow). **Security & GRC** consult for injury data (PHI-adjacent — keep it out of Now Assist summarisation).

## Part 5 — Anti-Patterns to Block

- Do not build a custom approval table or business rule — add rows to the decision table and set the properties (citation: markdown/financial-services-operations/approval-engine-for-reserves-and-payments.md).
- Do not add a decision-table input without updating the executing subflow (citation: markdown/financial-services-operations/insurance-claims/update-insurance-claims-automation-using-decision-tables.md).
- Do not enforce the police report with a custom client script on the settle action — use a Mandatory document list item (citation: markdown/financial-services-operations/doc-processor-associate-document-list-items-to-category.md).
- Do not create a custom "bodily injury" incident table when `sn_ins_claim_injury` covers the injury data (citation: markdown/financial-services-operations/insurance-claims-core-tables.md).

## Open Questions

- OQ-EV-1: How does the instance map the persona-title output to approvers (group membership? role?) — not documented.
- OQ-EV-2: Should the head-of-claims level apply to payments only, or reserves too (two separate property pairs exist)?
```

---

## Example 3 — Verdict C (§1.1 Halt — documented extension point)

### Dispatch input

**Source:** Chief Architect, routing from a user request.
**User request:** *"We sell commercial property and general liability policies. Commercial Lines Claims only has commercial auto. Set up claims for property and liability with their own intake, adjusters and SLAs. Also design the tables."*
**Module:** FSO — Commercial Lines Claims (`sn_ins_claim_cml`) vs Insurance claims (`sn_ins_gen_claim`)
**Customer model:** B2B accounts/contacts
**Volume:** ~4K commercial claims/year

### Gateway Response

```markdown
# FSO Insurance Specialist Gateway Response — commercial property and general liability claims lines

**Domain Expert:** FSO Insurance Specialist v1.0 (CSM Specialist co-fires: account/contact model)
**Release family:** Australia

---

## Part 1 — OOB Process Map

Two documented ways to add a P&C claims line:

- **Case type extension (Commercial Lines Claims).** The app ships only the Commercial auto policy case type; further commercial case types are created by extending the commercial claim base case, each with its own service definitions, playbook, flows, lists and roles.
- **Generic claim (Insurance claims, `sn_ins_gen_claim`).** A configuration-driven framework for single-policy P&C lines: a new line is a claim-type service definition on Claim Case, an adjuster-task service definition, a product-model link (Product Service Relationships), claim incident configuration rows and, where the loss data differs, an incident table extending Claim Incident — with no new case table.

FSO Core already ships the policy tables `sn_bom_cp_ins_policy` (Commercial Property) and `sn_bom_gl_ins_policy` (General Liability), so the policy side needs no new table.

(citation: markdown/financial-services-operations/insurance-claims/insurance-claims-applications.md, markdown/financial-services-operations/insurance-claims/create-a-service-definition-for-insurance-claims.md, markdown/financial-services-operations/fso-core-insurance-tables.md)

## Part 2 — Data Model Alignment

Baseline in scope: `sn_bom_claim_base` (printed also as `sn_bom_claim_case` — verify), `sn_ins_claim_cml_base` → `sn_ins_claim_cml_auto_service` (shipped), `sn_ins_gen_claim_case` / `sn_ins_gen_claim_adj_task` / `sn_ins_gen_claim_task`, Insurance Claims Core tables (`sn_ins_claim_property`, `sn_ins_claim_coverage`, `sn_ins_claim_profile`, `sn_ins_claim_participant`, `sn_ins_claim_reserve`, `sn_ins_claim_payment`, `sn_ins_claim_policy_snapshot`, `sn_ins_claim_incident_config`), policy tables `sn_bom_cp_ins_policy`, `sn_bom_gl_ins_policy`.

Two of the four commercial claims apps' SLA definitions are keyed on the service definition of case and adjuster tasks — separate SLAs per line need no new table.

(citation: markdown/financial-services-operations/insurance-claims/components_installed_with_commercial_lines_claims.md, markdown/financial-services-operations/insurance-claims-core-tables.md, markdown/financial-services-operations/insurance-claims/setting-up-insurance-claims-flow.md)

## Part 3 — §1.1 Baseline-First Verdict

### Verdict C — §1.1 halt protocol (documented extension point)

Whichever approach is chosen, the documented extension requires **new tables**:

- Case-type extension path: two new case tables extending `sn_ins_claim_cml_base` (plus task/adjuster-task/incident tables per line, mirroring the shipped auto set).
- Generic path: possibly one new incident table extending `sn_ins_claim_property` if property or liability loss data does not fit `sn_ins_claim_property` / `sn_ins_claim_injury`.

The docs prescribe both extensions, but under §1.1 a new table is approved by the Chief Architect, not by the documentation. **No table model is produced in this turn.**

### OPEN QUESTION — CUSTOM OBJECT PROPOSAL

1. **Baseline option evaluated.** The generic Insurance claims app covers a new P&C line with configuration only (service definitions + incident configuration + product link) when the base incident tables suffice. It falls short only if property/liability loss data needs its own incident fields, or if the insurer requires the commercial auto playbook/lists to be reused unchanged for the new lines (case-type extension gives each line its own playbook and roles).
2. **Custom object proposed (smallest scope).** Preferred: generic path with, at most, one incident table `sn_ins_claim_property_incident` (proposed — not baseline) extending `sn_ins_claim_property`, created in scope Insurance Claims Core, with reader/writer roles modelled on `sn_ins_claim.trip_writer/reader`, ACLs modelled on Trip Incident, registered in `sn_ins_claim_incident_config`. Alternative: two case types extending `sn_ins_claim_cml_base` (property, general liability) with task, adjuster task and incident tables — larger footprint.
3. **Consequences of approval.** Roles + ACLs + Contains-Roles grants to `sn_bom.fnol_representative` and the processor role; service definitions and categories; workspace lists and cloned Processor/Adjuster/Manager landing pages; SLA definitions per service definition; Store-upgrade impact on extended tables; ADR recorded.
4. **Alternatives if rejected.** Run property and liability claims as service definitions on the shipped auto case type (wrong labels/lists), or defer the lines.

(citation: markdown/financial-services-operations/insurance-claims/create-claim-incident-tables.md, markdown/financial-services-operations/insurance-claims/claim-incident-configuration-table.md, markdown/financial-services-operations/fso-int_guide-creating-new-fso-case-types.md)

## Part 4 — Routing Recommendation

**HALT — §1.1 custom-object proposal required.** Decision needed first: generic Insurance claims vs Commercial Lines Claims case-type extension (this choice is architectural and licensed per Store app — Licensing consult). After approval: Technical Designer (service definitions, incident configuration, roles/ACL pattern, SLA definitions), Flow Designer Specialist (FNOL playbook and triage decision table rows), DevOps/Release (Store install order, demo data off in prod).

## Part 5 — Anti-Patterns to Block

- Do not extend `sn_bom_case` directly — an application base exists (citation: markdown/financial-services-operations/fso-int_guide-extending-fso-case-types.md).
- Do not create tables in the wrong scope — incident tables in Insurance Claims Core, policy tables in FSO Core (citation: markdown/financial-services-operations/insurance-claims/create-claim-incident-tables.md).
- Do not modify the shared FNOL landing page — clone the per-persona landing pages (citation: markdown/financial-services-operations/insurance-claims/insurance-claims-dashboards-and-workspaces.md).
- Do not create custom policy tables — `sn_bom_cp_ins_policy` and `sn_bom_gl_ins_policy` ship (citation: markdown/financial-services-operations/fso-core-insurance-tables.md).

## Open Questions

- OQ-EV-1 (blocking): generic Insurance claims or Commercial Lines Claims extension? Which apps are licensed?
- OQ-EV-2 (blocking): does property/liability loss data fit `sn_ins_claim_property` + `sn_ins_claim_injury`, or is a dedicated incident table needed?
- OQ-EV-3: policy data source — are `sn_bom_cp_ins_policy` / `sn_bom_gl_ins_policy` loaded locally or looked up remotely?
```

---

*End of FSO Insurance Specialist EXAMPLES.md v1.0.*
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall