Broker

In plain words: App: Broker (insurance office)

Designed 1 min read 8 connected pages
The short version written for the Snayu team

An app for a Slovak insurance intermediary handling client requests (starting with compulsory motor liability insurance): it carries each case to an answer, a prepared act, a human handoff or a clear blocker.

Why read it: Read this before working on client-service casework or regulated advice workflows.
  1. 1The firm's legal role, products and named staff authority bound what the app may do.
  2. 2Must stop before unlicensed advice, payment, signature, binding cover or unsupported claims.
  3. 3Unrelated to LychD's internal queue broker despite the name.

Designed Contract only; no domain path enabled.

In this section 3 pages

Cases Broker: Service cases How each client contact becomes a service case with its own purpose, evidence, checks, review and single submission, so the next staff member can see exactly where it stands. open → Insurance Product Knowledge Broker: Insurance product knowledge How Broker keeps dated, attributable insurance product releases (coverage, exclusions, eligibility, pricing) and makes comparisons that state exactly which offers and criteria were considered. open → Channels Broker: Channels and views How clients, staff and technical operators each get their own view (Business Console, Client Web, Control Panel) and how incoming messages and outgoing answers are handled safely. open →
The original text Underlined words open their plain-English card.

A client calls to check their PZP cover: compulsory motor third-party liability insurance. Before the office answers, it must establish the request, the product knowledge that applies, and the authority of the person handling it. Broker carries that service case to an attributable answer, a prepared act, a human handoff, or an exact blocker.

The reference office is a Slovak non-life insurance intermediary beginning with PZP. Its deployment fixes the firm's legal role, jurisdictions, represented institutions, disclosures, complaint route, record duties, and named human authority. Product configuration and fluent prose cannot expand that mandate.

Open the office

Cases follows the contact and requested action. Insurance Product Knowledge supplies dated coverage, eligibility, comparison, quote, and expiry evidence. Channels admits contacts and projects reviewed results through separate staff, client, and technical surfaces.

Contract

Admit one requested action with its ClientContact@1, business policy, product catalogue, and current staff authority. broker.service_case@1, published by broker.office revision 1, carries that bounded case to its result. It must stop before unlicensed advice, undisclosed automation, payment, signature, binding, or unsupported product claims.

Broker names this application office. It is unrelated to LychD's internal queue broker.

Composition Portfolio · Workflow · IAM