Skip to content

Endorsement request

Tells the ops team that an agent asked to change an issued policy (an endorsement), with what changes, from what to what, and the supporting document.
Trigger
An agent submits an endorsement request for an issued policy in the ZenInsure app.
Sent to
InternalOps
From
Not decided
To
Ops
Cc
None
Attachments
Supporting document (depends on the change)

Subject

[Permintaan Endorsement] Polis 0215012600871 - BUDI SANTOSO (2192026111012345)

Preview text: Rina Wulandari meminta endorsement polis 0215012600871: Perubahan data tertanggung.

Rendering…
Open questions
  • No such email exists today; content is a proposal. Where ops works endorsement requests (ops app, AppSheet, or by email) is not documented.
  • The sample is a policyholder address change; the same email serves any product, so changes to the insured object (a vehicle plate, a property detail) use the same fields. Endorsement types, which ones need a supporting document, and which change the premium (so a new invoice or a refund follows) are not documented.
  • The email shows one changed field from-and-to; a request that changes several fields at once needs a list, which is not designed yet.
  • Whether the BM is copied, and whether the agent gets an acknowledgement or the insurer's endorsement document back, is not decided.
  • Email to ZenInsure ops: it has no support line and no legal footer. Sender address and recipient list are not decided.