User guide
For BimaHaq staff & partners

The insurance-expert portal

Empanel, take expert calls, and write the recap that ops approves.

As an empanelled insurance expert you staff the expert call in the Claim Review + Expert Call (₹1,499) service: you apply for empanelment, claim or receive a call from the pool, place the call outside the app, then hand-write the recap. Your recap is human-written (never AI) and always goes to ops for review before the customer sees it.

Workspace: /expertSign in: You do not self-signup. An admin invites you and you set your password from the email link, then sign in at /auth/login — you land on your expert workspace at /expert.
Fees mentioned in this guide
  • Claim Review + Expert Call₹1,499
  • Claim Review₹749

Prices are indicative and shown from our live catalogue. Final price is confirmed at checkout.

1. The big picture

Your whole path lives on one screen — /expert. First you empanel and wait for admin approval; once empanelled you take calls and write recaps. Nothing you write reaches a customer until ops approves it.

The expert journey
StartAdmin invites you; you sign in
Fill empanelment profile + upload credentials
DecisionAdmin empanels you?
  • no — revise & resubmit: go to Fill empanelment profile + upload credentials
Input / outputClaim or receive a call
Place the call outside the app
Hand-write the recap (no AI)
DecisionOps approves the draft?
  • sent back to revise: go to Hand-write the recap (no AI)
DoneApproved recap delivered to customer
Diagram source (mermaid)
flowchart TB
  start(["Admin invites you; you sign in"])
  apply["Fill empanelment profile + upload credentials"]
  review{"Admin empanels you?"}
  pool[/"Claim or receive a call"/]
  call["Place the call outside the app"]
  recap["Hand-write the recap no AI"]
  ops{"Ops approves the draft?"}
  done(["Approved recap delivered to customer"])
  start --> apply
  apply --> review
  review -->|"yes — empanelled"| pool
  review -->|"no — revise & resubmit"| apply
  pool --> call
  call --> recap
  recap --> ops
  ops -->|"yes, delivered"| done
  ops -->|"sent back to revise"| recap
  1. Admin invites you; you sign in
    • then Fill empanelment profile + upload credentials
  2. Fill empanelment profile + upload credentials
    • then Admin empanels you?
  3. Admin empanels you?
    • yes — empanelled: Claim or receive a call
    • no — revise & resubmit: Fill empanelment profile + upload credentials
  4. Claim or receive a call
    • then Place the call outside the app
  5. Place the call outside the app
    • then Hand-write the recap (no AI)
  6. Hand-write the recap (no AI)
    • then Ops approves the draft?
  7. Ops approves the draft?
    • yes, delivered: Approved recap delivered to customer
    • sent back to revise: Hand-write the recap (no AI)
  8. Approved recap delivered to customer
Compliance: You provide claims guidance only — not legal advice. You never promise an outcome, and any payable figure you note is a non-binding estimate, subject to policy terms.
Note: Everything happens on /expert. The (app) route group is invisible in the URL, so your workspace is simply /expert.

2. Get invited & sign in

Experts do not create their own accounts. An admin adds you to the panel and emails you an invite; you set a password from that link, then sign in.

  1. 1
    Set your password

    Open the invite email from the admin; the link opens the “Choose a new password” page — set and confirm your new password.

    Update password /auth/reset-password
  2. 2
    Sign in

    Enter your email and password.

    Sign in /auth/login

    You land on your expert workspace at /expert

Watch out: There is no self-signup for experts. If you were not invited by an admin, you cannot reach the expert workspace.
Tip: Your workspace at /expert is gated to the expert (and admin) role — if you land elsewhere, you are signed in under the wrong role.

3. Apply for empanelment

Before you can take any call you must submit an empanelment profile and upload your credentials for admin review. Until you are empanelled, the calls area shows nothing — you see only this profile.

  1. 1
    Open the empanelment profile

    After signing in, the profile card loads. If you have no profile yet it starts empty.

    Empanelment profile /expert
  2. 2
    Pick a document type

    Choose CV / résumé, III certificate (LIII / AIII / FIII), Degree / diploma, ID proof, PAN card, Cancelled cheque / bank proof, or Other.

    Document type /expert
  3. 3
    Upload a credential file

    Select a .pdf, .jpg, .jpeg, .png, .webp, .doc or .docx file, then upload it.

    Upload /expert

    The document is attached to your profile

  4. 4
    Enter your full name

    Type your full name — this field is required.

    Full name * /expert
  5. 5
    Tick your areas of expertise

    Check any that apply: Health / Mediclaim, Motor Own Damage, Motor Third Party, Life, Personal Accident, Travel, Property, Fire & Engineering, Marine, Liability, Workmen Compensation, ULIP, Annuity, Other.

    Health / Mediclaim /expert
  6. 6
    Fill the rest of the profile

    Add years of experience in insurance, your highest qualification and III qualification, affiliation, credentials, comma-separated languages, and your PAN and bank payout details.

    Years of Experience in Insurance /expert
  7. 7
    Submit for review

    Send the profile to the admin. Your status becomes 'under review'.

    Submit for review /expert

    Status shows 'under review'

Empanelment review
StartOpen empty profile
Input / outputUpload credentials
Fill name, areas, PAN, bank
Submit for review
DecisionAdmin decision
  • reject / suspend: go to Rejected — revise & resubmit
DoneEmpanelled — calls unlock
Rejected — revise & resubmit
  • resubmit: go to Submit for review
Diagram source (mermaid)
flowchart TB
  s(["Open empty profile"])
  u[/"Upload credentials"/]
  f["Fill name, areas, PAN, bank"]
  sub["Submit for review"]
  d{"Admin decision"}
  ok(["Empanelled — calls unlock"])
  back["Rejected — revise & resubmit"]
  s --> u
  u --> f
  f --> sub
  sub --> d
  d -->|"empanel"| ok
  d -->|"reject / suspend"| back
  back -->|"resubmit"| sub
  1. Open empty profile
    • then Upload credentials
  2. Upload credentials
    • then Fill name, areas, PAN, bank
  3. Fill name, areas, PAN, bank
    • then Submit for review
  4. Submit for review
    • then Admin decision
  5. Admin decision
    • empanel: Empanelled — calls unlock
    • reject / suspend: Rejected — revise & resubmit
  6. Empanelled — calls unlock
  7. Rejected — revise & resubmit
    • resubmit: Submit for review
Watch out: If you submit with a blank full name, you get the toast "Your full name is required." and the submit is blocked.
Note: Once a profile exists, the button reads "Update & resubmit" and a status badge shows under review / empanelled / rejected / suspended, plus any reviewer note.
Compliance: Panel membership is a human-approved gate: an admin reviews every application on /admin/experts and decides to empanel, reject or suspend. Submitting only sends your profile for admin review.

4. Claim or receive a call

Once you are empanelled, your workspace shows the calls you have been assigned and a pool of unassigned calls from Claim Review + Expert Call (₹1,499) bookings you can self-claim. Claimed or ops-assigned calls move into your Assigned calls.

  1. 1
    Review your assigned calls

    The calls area loads your calls and the claimable pool.

    Assigned calls /expert
  2. 2
    Scan the unassigned pool

    Look through policy type, issue summary and SLA for calls no one has taken yet.

    Unassigned calls you can claim /expert
  3. 3
    Claim a call

    Take ownership of a pooled call; it moves into your Assigned calls.

    Claim /expert

    The call appears under Assigned calls

Getting a call
StartOpen /expert (empanelled)
Input / outputAssigned calls + pool load
DecisionAlready assigned to you?
  • yes — work it: go to Call sits in Assigned calls
Scan the claimable pool
Claim a call
DoneCall sits in Assigned calls
Diagram source (mermaid)
flowchart TB
  open(["Open /expert empanelled"])
  load[/"Assigned calls + pool load"/]
  has{"Already assigned to you?"}
  scan["Scan the claimable pool"]
  claim["Claim a call"]
  work(["Call sits in Assigned calls"])
  open --> load
  load --> has
  has -->|"yes — work it"| work
  has -->|"no — check the pool"| scan
  scan --> claim
  claim --> work
  1. Open /expert (empanelled)
    • then Assigned calls + pool load
  2. Assigned calls + pool load
    • then Already assigned to you?
  3. Already assigned to you?
    • yes — work it: Call sits in Assigned calls
    • no — check the pool: Scan the claimable pool
  4. Scan the claimable pool
    • then Claim a call
  5. Claim a call
    • then Call sits in Assigned calls
  6. Call sits in Assigned calls
Watch out: Not yet empanelled? The pool is hidden and, with no assigned calls, the entire calls area renders nothing — you see only the empanelment profile.
Note: With no calls assigned but items in the pool, you see "No calls assigned to you yet." above the claimable list. If a claim fails because someone already took it, you get "Couldn't claim this call."
Tip: The "Accepting new calls" checkbox only appears once your status is 'empanelled' — untick it when you are unavailable so ops routes fresh calls elsewhere.

5. Run the call from the assigned-call card

You work each call entirely from its card. The card surfaces the customer name, policy type, issue summary, contact phone and email, and the SLA. There is no in-app dialer and no copilot — you place the call yourself, outside the app.

  1. 1
    Open an assigned call card

    Find the call under Assigned calls. The card shows the customer name, a policy-type chip and a stage chip ('to call' / 'draft submitted' / 'completed').

    Assigned calls /expert
  2. 2
    Read the issue and contact details

    Note the issue summary, phone, email and SLA label, then place the call outside the app.

    Issue /expert
Watch out: There is no copilot and no in-app dialer on the expert path. The call happens outside the app using the phone/email shown on the card.
Note: Once a call is completed, the card reads "Recap delivered to the customer." and the recap editor is hidden.

6. Write the recap for ops approval

After the call you hand-write the recap yourself — explicitly no AI. You may optionally add a claim strategy and a non-binding estimated payable, then submit the draft. It goes to ops to review and deliver; the customer only ever receives the approved recap.

  1. 1
    Write the call recap

    Type what was discussed, where the claim stands, and the key facts — at least a couple of lines (about 20 characters minimum).

    Your call recap (you write this — no AI) /expert
  2. 2
    Add strategy and estimate (optional)

    Optionally note recommended next steps and a non-binding payable estimate.

    Estimated payable /expert
  3. 3
    Submit the draft

    Send it to ops for review. The stage becomes 'drafted'.

    Submit draft /expert

    Your draft is queued for ops review

Recap to delivery
StartHand-write recap (no AI)
Optional strategy + estimate
DecisionRecap long enough?
  • too short — write more: go to Hand-write recap (no AI)
Submit draft
DecisionOps approves?
  • approve & deliver: go to Approved recap delivered
Revise the draft
  • update draft: go to Submit draft
DoneApproved recap delivered
Diagram source (mermaid)
flowchart TB
  w(["Hand-write recap no AI"])
  opt["Optional strategy + estimate"]
  len{"Recap long enough?"}
  sub["Submit draft"]
  ops{"Ops approves?"}
  rev["Revise the draft"]
  done(["Approved recap delivered"])
  w --> opt
  opt --> len
  len -->|"yes"| sub
  len -->|"too short — write more"| w
  sub --> ops
  ops -->|"approve & deliver"| done
  ops -->|"sent back"| rev
  rev -->|"update draft"| sub
  1. Hand-write recap (no AI)
    • then Optional strategy + estimate
  2. Optional strategy + estimate
    • then Recap long enough?
  3. Recap long enough?
    • yes: Submit draft
    • too short — write more: Hand-write recap (no AI)
  4. Submit draft
    • then Ops approves?
  5. Ops approves?
    • approve & deliver: Approved recap delivered
    • sent back: Revise the draft
  6. Revise the draft
    • update draft: Submit draft
  7. Approved recap delivered
Compliance: Your recap is human-written and goes to our team to review and deliver — the customer receives the approved recap. It is claims guidance, not legal advice, and no outcome is promised. The system never auto-sends it and never issues a claim verdict.
Watch out: If the recap is under about 20 characters, you get the toast "Write your call recap (at least a couple of lines)." and the submit is blocked.
Watch out: Any payable figure is a NON-BINDING estimate, subject to policy terms — never state it as a guaranteed amount.
Note: After you submit, the editor stays open pre-filled and the button reads "Update draft" so you can revise if ops sends it back.

7. Privacy & the rules you work under

You handle customer claim details and contact information. A few binding rules keep the panel compliant.

  • Claims guidance only — you give claims guidance, never legal advice.
  • No AI on your path — the recap is yours to write; the label says so explicitly.
  • Human-approval gate — ops reviews and delivers every recap; nothing auto-sends to the customer.
  • No outcome promises — never guarantee that a claim will be paid or that a payable figure is final.
  • Non-binding estimates — any payable estimate is subject to policy terms.
  • Panel is vetted — an admin empanels, rejects or suspends every expert.
Compliance: Fees are fixed platform fees — never a percentage of the claim, a success fee, or any fee-sharing arrangement. You do not represent customers before Consumer Commissions.
Note: Use customer contact details only to place the assigned call and write the recap. Do not reuse or share them for any other purpose.

Questions people ask

Can I take calls before I'm empanelled?
No. Until an admin empanels you, the pool is hidden and the calls area shows nothing — you see only your empanelment profile. Empanelment is a human-reviewed gate on /admin/experts.
Is there a dialer or a copilot in the workspace?
No. There is no in-app dialer and no copilot on the expert path. You work from the assigned-call card and place the call yourself, outside the app, using the phone or email shown.
Does AI write my recap?
No. The recap is explicitly human-written — the field is even labelled "you write this — no AI". Your draft then goes to ops to review and deliver.
Does the customer see my draft right away?
No. Your draft is queued for ops review. The customer only ever receives the recap after ops approves and delivers it — nothing auto-sends.
Can I tell the customer exactly how much they'll be paid?
No. Any payable you note is a non-binding estimate, subject to policy terms. You give claims guidance, not a guaranteed outcome, and never a claim verdict.
Stuck on something this guide didn't cover?

Reach the platform team through your workspace, or open a ticket in the support queue.

This guide explains how to use the BimaHaq platform. It is general information, not legal or financial advice, and describes a process — not a guaranteed outcome.