Policy Servicing (保單服務)

Selling a policy is the part of the business that generates the commission. Servicing it is the part that decides whether the client is still there in year ten.

A POS that only sells is a brochure. A POS that services is the thing the client actually keeps using — and, in Hong Kong, the thing that most reliably converts a one-off buyer into a client who sends their family.

This lesson covers the changes a client asks for, and more importantly the changes a client needs but does not ask for: the lapse warning, the nomination that was never updated, the address that stopped being correct two years ago.

Learning Objectives

1. Run the post-sale lifecycle — from policy issue through delivery, the free-look window, anniversaries and eventual claims, and know which events are automatic versus which a client must ask for.
2. Process the common alterations correctly — address change, premium mode change, beneficiary/nomination change, and increase or decrease of sum assured — including which ones alter the risk and therefore require re-underwriting; and handle reinstatement with an accurate picture of the coverage gap, because the most damaging servicing error is not a refusal, it is an incomplete reinstatement.
3. Explain lapse and free-look precisely, including what the client gets back in each case and why the difference is large, and build the servicing record as an audit trail, so that every change has a reason, an initiator, an approval level and a client-confirmed outcome.

---

Why Servicing Is Under-Specified

In practice: almost every insurance POS treats servicing as a form-filling screen. The design mistake is treating all changes as equivalent when they fall into three structurally different classes, and the class determines the risk.

The row that causes the trouble is the third. A beneficiary change looks clerical and is not — in Hong Kong it can engage a spouse-consent requirement and a best-interests review where children are involved. A sum assured change looks financial and is not — an increase is a fresh underwriting application in all but name.

The governing rule: if the change alters the amount of cover or the risk being carried, it is a new contract event, not a maintenance task.

---

The Post-Sale Lifecycle

In practice: from the moment the policy is issued, a clock is running. Every stage below has either an automatic action or a window that closes.

POLICY_ISSUED
     │
     ▼
DELIVERY_PENDING ──────────► DELIVERED ──┐
     │                          │        │
     │                          ▼        │
     │                    FREE_LOOK_ACTIVE (typically 15 days)
     │                          │        │
     │              ┌───────────┴────────┴──────────┐
     │              │                              │
     │      WITHDRAWN_IN_FREE_LOOK           FREE_LOOK_EXPIRED
     │      (full premium refunded)                 │
     │                                              ▼
     │                                        IN_FORCE
     │                                              │
     │          ┌───────────────────────────────────┤
     │          │                    │              │
     │          ▼                    ▼              ▼
     │     ANNIVERSARY          PREMIUM_DUE    SUSPENDED
     │     (bonus declared,     (grace period   (premium
     │      age bands,          countdown)       holiday,
     │      TAT reset)                             not covered)
     │          │                    │              │
     │          │                    ▼              │
     │          │              GRACE_PERIOD ──────────┘
     │          │              (default notice,   │
     │          │               usually 30 days)  │
     │          │                    │              │
     │          │                    ▼              ▼
     │          │                 LAPSED       REINSTATED
     │          │                    │              │
     │          │                    ▼              ▼
     │          │            REINSTATEMENT         IN_FORCE
     │          │            (late-cover gap)
     │          │
     └──► MATURED / CLAIMED / SURRENDERED / LAPSED_PERMANENT

Two features of this chart cause most of the client disputes in practice: the grace period and the late-cover gap. Both are timing, both are easy to explain in advance, and both are almost always explained too late or not at all.

Events that are automatic vs events the client must ask for

Everything in the second group is invisible to the system. A client whose address is wrong, or whose nomination still names an ex-partner, produces no error anywhere — until the exact moment somebody needs the policy.

That is the argument for the proactive servicing cadence in the final section of this lesson.

---

Clerical Changes, and the One That Is Not

In practice: address change takes under a minute and has the highest consequence ratio of any change in this lesson.

interface AddressChangeRequest {
  policyId: string;
  previousAddress: Address;
  newAddress: Address;

  // Critical: is the new address the client's own, or someone else's?
  addressType: "SELF" | "THIRD_PARTY";

  effectiveDate: string;          // usually immediate, not next cycle

  // Legal service basis: where notices can be validly served.
  serviceOfProcessConfirmed: boolean;
  clientAcknowledgedInWriting: boolean;

  // If THIRD_PARTY — mirrors the Lesson 09 KYC rule.
  thirdPartyConsent?: {
    obtained: boolean;
    documentRef?: string;
    confirmationCallAt?: string;
    // A third-party residential address usually becomes the mailing
    // address permanently. The client must be told this, not surprised by it.
    becomesMailingAddress: boolean;
  };
}

Why immediacy matters. An address is not a mailing convenience; it is the service basis for legal notice. A formal notice that cannot be served may be treated as not served. So a "lapse warning" posted to an old address that the client vacated two years ago can leave a client believing they are covered when they are not.

Why the third-party check matters. If the new address is someone else's home — a partner's, a parent's, a friend's — then the KYC rule from Lesson 09 applies directly: documented reason, the third party's written consent, and a confirmation call. Because that household will now receive every notice about this policy, including claim correspondence and, eventually, settlement money, this is a genuine privacy matter for both parties and not a formality.

What to tell the client when the address is third-party:

"你新地址係 X 先生嗰度，咁所有關於呢張保單嘅通知 — 包括將來嘅理賠批核同埋賠付款 — 都會寄去嗰度， 即係話 X 先生會睇到。呢個係咪你想嘅？"

Asking that question takes five seconds and prevents a complaint that can take two years.

---

Financial Changes

In practice: premium mode change is the most requested financial servicing action and the most frequently answered badly, because the honest answer is not "yes you can save money".

Premium mode

The trade-off is not "cheaper is better". Quarterly costs less than monthly, but produces a larger quarterly outflow. For a client whose cash flow is tight, converting from monthly to quarterly can produce exactly the missed payment that lapses the policy — and the saving is usually a small fraction of the premium.

The conversation:

  Client: "季繳平啲啦?"

  Wrong:   "係呀，季繳平啲㗎。"          → client switches, then misses a quarter
  Right:   "季繳係會平少少，但你要每三個月一次過交。
           你上次話現金流比較緊，我哋傾下先 —
           你每季都肯定交得出咩？"

  The right answer may be "stay monthly".
  That is a good outcome.

Because the premium remains the same relative to the cover, mode change does not alter the risk, and does not require re-underwriting.

Other financial servicing actions

The policy loan row is the one worth dwelling on. A client takes a policy loan, does not repay it, and the outstanding loan is deducted from any eventual claim. The client believes they still have full cover. They do not. This is a routine servicing action that quietly reduces the death benefit, and it deserves an explicit written warning rather than a line in a statement.

---

Contractual Changes

In practice: these alter what the contract is, and each has a different approval path. Treating them as maintenance tasks is how an agency ends up defending a change it had no authority to make.

Beneficiary / nomination change

Irrevocability is the trap. Where a policy has been assigned as security or a nomination has been declared irrevocable, it cannot simply be changed by the policyholder's request. An agent who processes the change without checking produces a change that will be reversed at the worst possible moment.

Sum assured change

DECREASE  →  premium falls, benefit falls. Usually agent-level approval,
            but confirm no beneficiary has been assigned as collateral
            and that the reduction does not fall below the plan's
            stated need from the FNA (Lesson 04).

INCREASE  →  a fresh underwriting application in all but name.
            ✓ re-run the health disclosure for anything rating-relevant
            ✓ re-underwrite (may load even where the original was standard)
            ✓ recalculate premium
            ✓ fresh proposal version + fresh signature (Lesson 08)
            ✗ never edit the existing policy schedule in place

            And critically: the increase is effective from the policy's
            anniversary, not the day the client asked — the standard
            amount is already earned. If the client dies tomorrow,
            tomorrow's increase does not pay.

That last point is the single most common complaint in this area. Clients assume an approved increase is live immediately. It is not, and saying so at the point of approval costs nothing.

The complaint in full, worked through. A client asks on 14 March for a sum assured increase from HK$1,000,000 to HK$2,000,000. Underwriting approves on 28 March. If the agent reports "approved, effective immediately", then:

Nothing was fraudulent and nothing was forged. The agent did every procedural step correctly and still destroyed a client's trust, and possibly a claim relationship, on a single sentence at the point of approval. The gap between 28 March and 30 April is 33 days in which the client had been told they were covered for an amount they were not.

The fix costs one sentence and one recorded field:

"陳先生，你嘅加保申請已經批咗。不過要留意，加保係由四月三十號，即係保單週年嗰日 先生效。即係話三月三十號到四月三十號呢三十三天，你嘅保額仍然係一百萬。 我會喺批核書上面寫低呢個生效日期，等你隨時可以查返。"

and a effectiveDate field on the change record, distinct from approvedAt and requestedAt. A system that stores only one date for this event will eventually display the approval date, because that is the date it has.

Changing the category of cover

Moving from a medical plan to a critical illness plan is not a switch. It is a new risk exposure with different underwriting characteristics, a different premium basis, and different policy terms. It follows the increase path above.

Product category change in the POS

type ServicingChange =
  | { kind: "ADDRESS";          approval: "AGENT";         reUnderwrite: false }
  | { kind: "CONTACT";          approval: "AGENT";         reUnderwrite: false }
  | { kind: "PREMIUM_MODE";     approval: "AGENT";         reUnderwrite: false }
  | { kind: "PREMIUM_HOLIDAY";  approval: "SUPERVISOR";    reUnderwrite: "PRODUCT_DEPENDENT" }
  | { kind: "BENEFICIARY";      approval: "SUPERVISOR";    reUnderwrite: false; checks: ["IRREVOCABILITY","SPOUSE_CONSENT","MINOR_TRUSTEE"] }
  | { kind: "SUM_ASSURED_DOWN"; approval: "SUPERVISOR";    reUnderwrite: false; checks: ["COLLATERAL_ASSIGNED","FNA_FLOOR"] }
  | { kind: "SUM_ASSURED_UP";   approval: "UNDERWRITING";  reUnderwrite: true;  checks: ["DISCLOSURE_RERUN","FRESH_SIGNATURE"] }
  | { kind: "CATEGORY_CHANGE";  approval: "UNDERWRITING";  reUnderwrite: true;  checks: ["DISCLOSURE_RERUN","FRESH_SIGNATURE","PREMIUM_RESET"] }
  | { kind: "CANCEL";           approval: "SUPERVISOR";    reUnderwrite: false; checks: ["REASON_CODE","CLIENT_RECEIPT"] }
  | { kind: "REINSTATE";        approval: "SUPERVISOR";    reUnderwrite: "CARRIER_RULE"; checks: ["GAP_COMPUTED","CLIENT_ACKNOWLEDGED_GAP"] };

Every one of these produces a state change event row, not an edited record. The audit trail is the deliverable.

---

Reinstatement: The Coverage Gap Is the Whole Point

In practice: reinstatement is where agents most often create a problem that will not surface for years. They process the reinstatement correctly as a transaction and fail to communicate the gap in the cover.

A policy lapsed on a specific date. The client pays the arrears and is reinstated. But between the lapse date and the reinstatement date, the policy was not in force. If a claim occurs in that window, nothing is payable.

Lapse date        : 2026-03-14
Reinstatement date: 2026-09-02
Arrears paid      : HK$4,150

Question the agent MUST answer before processing:
  "陳先生，由三月十四號到而家九月二號，
   呢段時間其實係冇保障嘅。如果呢段期間出事，
   任何醫療費用都唔會賠。

   你仲想喺呢個情況下復效，定係我哋傾下先？"

  If yes → process, and record that the gap was disclosed and accepted.
  If no  → client may prefer a new application instead.

Some carriers apply a shorter late-cover period or reinstate from the date arrears were paid rather than from the date requested. Both are legitimate. Neither is discoverable by the client unless someone tells them, and the client is the one who carries the risk.

The other thing to check on a reinstatement: does it require re-underwriting? A long lapse is a health event as often as a financial one — the client may have been unwell, may have been hospitalised, may have changed medication. A carrier may reinstate at standard, at a loading, or require fresh evidence. If a fresh declaration is required, do not reinstate first and check later.

Claim form and free look

Two distinct things with confusingly similar names, both mentioned constantly:

The point to internalise: after the free-look window, cancelling is surrender, and the client receives the cash value, not a refund. The difference can be the entire premium paid minus the cost of the cover consumed. An agent who says "you can cancel and get your money back" after the window has closed has made a false statement, however kindly intended.

---

The Servicing Record

In practice: the servicing history is what a client, a compliance reviewer or a claims handler will read to reconstruct what happened and who was told what. It has to answer that question without interviews.

{
  "changeId": "CHG-2026-11902",
  "policyId": "POL-88213",
  "changeType": "SUM_ASSURED_UP",
  "requestedBy": "POLICYHOLDER",
  "requestChannel": "AGENT_MEETING",
  "agentId": "AG-4412",

  "from": { "sumAssured": 1000000, "annualPremium": 8400 },
  "to":   { "sumAssured": 1500000, "annualPremium": 12600 },

  "reason": "客戶入息增加，想加大保障",

  "underwriting": {
    "required": true,
    "outcome": "LOADED",
    "loadingPct": 20,
    "disclosureRerun": true,
    "evidenceRequested": ["SPECIALIST_REPORT"],
    "decidedBy": "UW-2201",
    "decidedAt": "2026-08-14T16:02:00+08:00"
  },

  "effectiveDate": "2026-10-02",
  "effectiveNote": "由下個保單週年日起生效；本月多出嘅保障唔受保。",

  "clientCommunications": [
    { "at": "2026-08-15T11:20:00+08:00", "channel": "IN_PERSON",
      "content": "已解釋加費 20% 為永久，保額由 100 萬增至 150 萬，下個週年生效。" },
    { "at": "2026-08-15T11:20:00+08:00", "channel": "WRITTEN",
      "docRef": "DOC-2026-8802" }
  ],

  "approvals": [
    { "role": "AGENT",      "id": "AG-4412", "at": "2026-08-15T11:25:00+08:00" },
    { "role": "SUPERVISOR", "id": "SV-0088", "at": "2026-08-18T09:40:00+08:00" }
  ],

  "clientAcknowledged": true,
  "acknowledgedAt": "2026-08-18T10:02:00+08:00"
}

Four things in that record are not decoration:

• effectiveNote — the effective date stated in the client's own words, in writing.
• clientCommunications — what was actually said, not what should have been said.
• effectiveDate ≠ changeRequestDate — the distinction that prevents the most common complaint in this module.
• clientAcknowledged — without it, the record proves an agent did something, not that the client understood it.

---

Free-look and the First Ninety Days

In practice: the window immediately after delivery is when the client is most able to spot a problem and least likely to speak up.

The correct handling of a free-look window is not passive. A proactive agent sets the expectation at delivery:

"陳先生,保單今日送到,你有一個禮拜時間慢慢睇。 條款、等候期、保障限額同你簽嗰陣講嘅有冇分別,你都可以問我。 十五日內如果唔想要,可以全額退返保費。"

Then check in near the end of the window. That single call catches most of the problems that otherwise surface years later — a waiting period longer than expected, a benefit definition that differs from the illustration, a mode change nobody explained.

The same reasoning extends to the first anniversary, where age banding begins and the first premium increase is visible. A client who sees a premium rise with no warning will assume the agent took a commission or the company is overcharging. A client who was told in advance sees a scheduled change.

---

Proactive Servicing: The Cadence

In practice: nothing in this lesson is reachable by a system alert except the premium calendar. The rest is a human habit, and it is the single highest-return habit in agency practice.

The grace-period call deserves its own note. A policy that has missed a payment is rescuable in almost every case, and almost every case is rescued by someone noticing before the window closes. A client whose direct debit failed at a bank that no longer exists will not pay until someone tells them. Silence at that moment converts a seven-figure asset into a zero, and it does so silently.

Why the rest needs a human habit, stated precisely. Only the premium calendar produces a system alert, because only the premium calendar knows a date is coming. Every other trigger on that table is an inference — that a client might be retiring, that a nomination might be stale after a marriage the agency heard about second-hand. A system can detect that a client has turned 60; it cannot detect that a client has decided to stop working, which is a different event, and the one that matters.

This is not a limitation to be engineered away in the first release. It is the correct division of labour: the system owns the dates it is certain about, and the agent owns the judgements it is not. An agency that automates the second category without the human has not saved work, it has removed the only moment where a stale nomination or an impending retirement would ever have been noticed.

The one cadence item that is also a compliance obligation. The free-look check-in on day 12 looks like service and is closer to disclosure. A client who cancels in the free-look window and had never been contacted is a client whose cancellation was driven entirely by their own re-reading of the policy contract — and, because Lesson 12 established that a free-look cancellation is usually a full commission clawback, also a client who cost the agency a month of income. Both facts point the same way: the day-12 call is the cheapest possible place to discover a misunderstanding, and the most expensive to discover late.

---

Common Servicing Errors

---

Key Takeaways

1. Servicing changes fall into three classes — clerical (address, contact), financial (premium mode, holiday, loan) and contractual (sum assured, beneficiary, category). Only the first is routine. If a change alters the amount of cover or the risk carried, it is a new contract event, not a maintenance task.
2. Address change is the fastest action with the highest consequence ratio, because an address is the service basis for legal notice — an unserved formal notice can leave a client believing they are covered when they are not. Effect it immediately. A third-party address brings the Lesson 09 KYC rule with it — documented reason, written consent, confirmation call — and the client must be told that a third party will receive all notices including claim settlement. Ask that out loud; it takes five seconds and prevents a two-year complaint.
3. A sum assured increase is a fresh underwriting application in all but name: disclosure rerun, re-underwriting (it may load where the original was standard), recalculated premium, fresh proposal version and fresh signature. Never an in-place edit. And it takes effect at the next anniversary, not on the day it is approved — this is the most common complaint in this module, and it is prevented entirely by writing the effective date and the resulting gap into the record in the client's own words.
4. Reinstatement is not "pay the arrears and carry on". There is a late-cover gap between the lapse date and the reinstatement date in which nothing is covered. Compute it, disclose it, and let the client choose — and check whether the carrier requires fresh underwriting, because a long lapse is frequently a health event.
5. Free look and surrender are different things. Inside the free-look window the client can cancel and receive a full refund. After it, cancelling is surrender and the client receives the cash value. The difference can be the whole premium paid.
6. Check irrevocability before processing any beneficiary change, and run the spouse-consent and best-interests-of-children checks where they apply. Some nominations cannot be changed by the policyholder's request at all.
7. Every change is an append-only event row with a reason code, initiator, approval chain, the communications actually sent, and client acknowledgement. An agent who changed a policy needs an agent who did something; the acknowledgement is what proves the client understood it.
8. The grace-period call is the highest-value call in the business. A missed direct debit converts a seven-figure asset into a zero, silently, and almost every one of those policies is rescuable if someone notices in time.
9. Proactively review the nomination annually, and return to the analysis modules when circumstances change — a major life event is a fresh needs analysis (Lesson 04), approaching retirement is a fresh retirement gap review (Lesson 05). Servicing that never revisits the plan is just administration, and a stale nomination after marriage or divorce is invisible to every system and explosive when it matters.

---

Glossary (zh-Hant-HK)