User guide
For BimaHaq staff & partners

The insurer representative workspace

Respond to disputes in the Resolution Room and read your analytics on the data platform.

As an insurer representative you meet policyholders inside a neutral Resolution Room — read the thread, post messages, make or answer settlement proposals, join mediation calls, and e-sign the agreement. Separately, your organisation's claims analytics live on the /data platform, where every upload is anonymised before anything is stored. This guide walks both.

Workspace: /resolutionSign in: You are invited by a BimaHaq admin — open the invitation email, set your password from the link, then sign in at /auth/login. You land on your Insurer Workspace at /resolution.

1. The big picture

Two distinct workspaces sit behind your login. The Resolution Room is where a single disputed case is worked toward settlement; the data platform is where your organisation's aggregate claims data is analysed. You reach /resolution automatically after sign-in and open a specific room from there.

What you do here
StartSign in (admin invite)
Land on the Insurer Workspace (/resolution)
DecisionDispute or analytics?
  • analytics: go to Open the /data analytics platform
Open a Resolution Room
Message, propose, meet, settle
E-sign the agreement
  • go to Case resolved / insight exported
Input / outputOpen the /data analytics platform
DoneCase resolved / insight exported
Diagram source (mermaid)
flowchart TB
  login(["Sign in admin invite"])
  ws["Land on the Insurer Workspace /resolution"]
  pick{"Dispute or analytics?"}
  room["Open a Resolution Room"]
  settle["Message, propose, meet, settle"]
  esign["E-sign the agreement"]
  data[/"Open the /data analytics platform"/]
  done(["Case resolved / insight exported"])
  login --> ws
  ws --> pick
  pick -->|"dispute"| room
  pick -->|"analytics"| data
  room --> settle
  settle --> esign
  esign --> done
  data --> done
  1. Sign in (admin invite)
    • then Land on the Insurer Workspace (/resolution)
  2. Land on the Insurer Workspace (/resolution)
    • then Dispute or analytics?
  3. Dispute or analytics?
    • dispute: Open a Resolution Room
    • analytics: Open the /data analytics platform
  4. Open a Resolution Room
    • then Message, propose, meet, settle
  5. Message, propose, meet, settle
    • then E-sign the agreement
  6. E-sign the agreement
    • then Case resolved / insight exported
  7. Open the /data analytics platform
    • then Case resolved / insight exported
  8. Case resolved / insight exported
Compliance: The Resolution Room is a neutral settlement space. BimaHaq facilitates the discussion and drafts the paperwork; it does not promise any particular outcome, and staff-only close/outcome controls stay with the case manager — you cannot unilaterally close a case or record its result.
Note: There is no in-app menu link to the data platform for your role. Reach /resolution as your login landing, and reach the analytics platform by typing /data directly.

2. Sign in to your workspace

Insurer reps do not self-register. A BimaHaq admin invites you and provisions the insurer_rep role; you set your password from the emailed link, then sign in.

  1. 1
    Set your password from the invite

    Open the invitation email from BimaHaq and follow its link to set your password. If the link has expired, use “Forgot password?” on the sign-in page to get a fresh reset link.

    Forgot password? /auth/login
  2. 2
    Sign in

    Enter your email and password. If two-factor is set up, enter the 6-digit code.

    Sign in /auth/login

    You land on the Insurer Workspace at /resolution

  3. 3
    Read your workspace

    The header shows an “Insurer Workspace” pill and your role badge. A three-card strip counts your active disputes, upcoming meetings and proposals awaiting your review.

    Insurer Workspace /resolution
Watch out: The Insurer Workspace is limited to the insurer_rep and admin roles. The insurance-company governance console at /portal/insurer is a different, customer-role portal — it is not yours, and opening it returns a “This portal isn’t yours” screen.

3. Respond to a dispute in the Resolution Room

From your workspace, open an assigned dispute, read the thread, post messages, and make or answer a settlement proposal. Cards flagged “N proposals to review” are waiting on you.

  1. 1
    Open an assigned dispute

    In the “My rooms” list, click a dispute card. A badge shows how many proposals need your response.

    Open room /resolution
  2. 2
    Read the discussion

    The room opens on the Discussion tab by default; the thread shows the full multi-party conversation.

    Discussion /cases/[caseId]/room
  3. 3
    Post a message

    Type in the message box (up to 5,000 characters) and send. The box appears only while the room is open.

    Send /cases/[caseId]/room
  4. 4
    Open the Settlement tab

    Switch to Settlement to see every proposal and its status.

    Settlement /cases/[caseId]/room
  5. 5
    Make your own offer

    Click “+ Make a proposal”, enter the rupee amount and the terms, then post it. This button shows only when the room is open and no proposal is already pending.

    + Make a proposal /cases/[caseId]/room

    Your offer appears in the Settlement tab

  6. 6
    Answer the other side’s offer

    On a pending proposal that is not yours, Accept it, Reject it (a written reason is required), or Counter with a new figure.

    Counter /cases/[caseId]/room
Working a dispute
StartOpen the room
Read the discussion
Post messages
DecisionWho has an offer on the table?
  • theirs pending: go to Accept / Reject / Counter theirs
Make your own proposal
  • go to Proposal accepted → Resolved
Accept / Reject / Counter theirs
DoneProposal accepted → Resolved
Diagram source (mermaid)
flowchart TB
  open(["Open the room"])
  read["Read the discussion"]
  talk["Post messages"]
  prop{"Who has an offer on the table?"}
  make["Make your own proposal"]
  answer["Accept / Reject / Counter theirs"]
  settled(["Proposal accepted → Resolved"])
  open --> read
  read --> talk
  talk --> prop
  prop -->|"none pending"| make
  prop -->|"theirs pending"| answer
  make --> settled
  answer --> settled
  1. Open the room
    • then Read the discussion
  2. Read the discussion
    • then Post messages
  3. Post messages
    • then Who has an offer on the table?
  4. Who has an offer on the table?
    • none pending: Make your own proposal
    • theirs pending: Accept / Reject / Counter theirs
  5. Make your own proposal
    • then Proposal accepted → Resolved
  6. Accept / Reject / Counter theirs
    • then Proposal accepted → Resolved
  7. Proposal accepted → Resolved
Watch out: The message box and “+ Make a proposal” render only while the room status is open. A resolved or closed room is read-only.
Watch out: Only one proposal can be pending at a time — “+ Make a proposal” stays hidden until the current one is resolved. On your own pending offer you see only “Withdraw”; you cannot Accept, Reject or Counter your own proposal.
Compliance: Rejecting a proposal requires a written reason, and accepting one fires a confirmation dialog before the case moves to Resolved — deliberate, on-the-record steps by design.
Note: If a case has no room yet you’ll see “No Resolution Room exists for this case yet.”; if you lack access you’ll see “You don’t have access to this Resolution Room.”

4. Accept a settlement and e-sign the agreement

Accepting the counterparty’s proposal moves the case to Resolved. The case manager sends the settlement agreement for signature; you sign your own party row in the eSign tab.

  1. 1
    Accept the proposal

    In the Settlement tab, click Accept on the pending proposal and confirm the “Accept ₹…?” dialog.

    Accept /cases/[caseId]/room

    “Proposal accepted — case moved to Resolved.”

  2. 2
    Open the eSign tab

    Switch to eSign to see the settlement-agreement signature envelope.

    eSign /cases/[caseId]/room
  3. 3
    Sign as the insurer party

    On your own invitee row, click “Sign now” to open the provider’s signing page and complete your signature.

    Sign now /cases/[caseId]/room
  4. 4
    Confirm execution

    Once every party has signed, the tab shows “Agreement fully executed”; follow the link to view it in the case documents.

    View it in the case /cases/[caseId]/room

    The executed agreement is filed to the case

Accept and sign
StartAccept proposal (confirm dialog)
Case moves to Resolved
Open eSign tab
DecisioneSign enabled & your row unsigned?
  • no: go to Read-only until enabled / sent
Sign your party row
  • go to Agreement fully executed
Read-only until enabled / sent
DoneAgreement fully executed
Diagram source (mermaid)
flowchart TB
  acc(["Accept proposal confirm dialog"])
  res["Case moves to Resolved"]
  tab["Open eSign tab"]
  avail{"eSign enabled & your row unsigned?"}
  sign["Sign your party row"]
  wait["Read-only until enabled / sent"]
  done(["Agreement fully executed"])
  acc --> res
  res --> tab
  tab --> avail
  avail -->|"yes"| sign
  avail -->|"no"| wait
  sign --> done
  wait --> done
  1. Accept proposal (confirm dialog)
    • then Case moves to Resolved
  2. Case moves to Resolved
    • then Open eSign tab
  3. Open eSign tab
    • then eSign enabled & your row unsigned?
  4. eSign enabled & your row unsigned?
    • yes: Sign your party row
    • no: Read-only until enabled / sent
  5. Sign your party row
    • then Agreement fully executed
  6. Read-only until enabled / sent
    • then Agreement fully executed
  7. Agreement fully executed
Watch out: Only your case manager or an admin sends the envelope for signature — the “Send for eSign” control is not visible to you. You sign your own row only, and only when it has a signing link and the envelope is not in demo mode.
Compliance: E-signing is consent-driven. In demo mode there is no “Sign now” link; a staff-only “Simulate all signatures” control stands in, so one party can never forge both signatures. A completed envelope cannot be re-sent — only rejected, expired or failed ones can be re-issued.
Note: If e-signing isn’t switched on, the tab reads “eSigning of settlement agreements isn’t enabled yet.” and there is nothing to sign.

5. Join a scheduled mediation session

Video mediation sessions are scheduled by the case manager. You join them from your workspace or from inside the room.

  1. 1
    Find upcoming sessions

    Scroll to “Upcoming meetings”. Each row shows the case number, provider, time and duration.

    Upcoming meetings /resolution
  2. 2
    Join the call

    Click Join to open the meeting link in a new tab. Join appears only once a meeting link is set.

    Join /resolution
  3. 3
    Or join from the room

    Inside the room, switch to the Meetings tab and use the join link on a scheduled meeting.

    Meetings /cases/[caseId]/room
Watch out: Scheduling is case-manager and admin only — the “+ Schedule meeting” button and the Complete / Cancel controls are not visible to you. You join sessions; you do not create or close them.
Note: With nothing on the calendar you’ll see “No upcoming meetings.” Once a session is booked, a one-tap join link appears here.

6. Upload a claims dataset with privacy review

On the /data platform your organisation’s claims data becomes analytics. Uploading is a deliberate two-step: the file is analysed first and stored only after you approve how each column is anonymised.

  1. 1
    Open the analytics platform

    Type /data in the address bar (there is no menu link for your role). The header confirms your raw personal data is never stored.

    Data platform /data
  2. 2
    Select or create your organisation

    Pick your insurer/TPA in the selector, or click “Organisation” to create one (it prompts for the name).

    Organisation /data
  3. 3
    Upload a file

    Choose a CSV, XLSX or JSON file. It is analysed immediately but not yet stored.

    CSV, XLSX or JSON /data
  4. 4
    Review the anonymization policy

    For each detected column, inspect its class and disposition (pseudonymize / mask / generalize / drop / keep) and change any you disagree with. Nothing has been stored yet.

    Review before ingest /data
  5. 5
    Confirm ingest

    Click “Confirm & ingest”. Only the transformed rows are written; the dataset shows “Anonymizing & processing…” then “ready”.

    Confirm & ingest /data

    A ready, anonymised dataset appears in your list

Upload with privacy review
StartOpen /data
DecisionHave an organisation?
  • yes: go to Upload CSV / XLSX / JSON (analysed only)
Create your org
Input / outputUpload CSV / XLSX / JSON (analysed only)
Approve per-column anonymization
Confirm & ingest (transformed rows only)
DoneDataset ready
Diagram source (mermaid)
flowchart TB
  open(["Open /data"])
  org{"Have an organisation?"}
  create["Create your org"]
  up[/"Upload CSV / XLSX / JSON analysed only"/]
  review["Approve per-column anonymization"]
  ingest["Confirm & ingest transformed rows only"]
  ready(["Dataset ready"])
  open --> org
  org -->|"yes"| up
  org -->|"no"| create
  create --> up
  up --> review
  review --> ingest
  ingest --> ready
  1. Open /data
    • then Have an organisation?
  2. Have an organisation?
    • yes: Upload CSV / XLSX / JSON (analysed only)
    • no: Create your org
  3. Create your org
    • then Upload CSV / XLSX / JSON (analysed only)
  4. Upload CSV / XLSX / JSON (analysed only)
    • then Approve per-column anonymization
  5. Approve per-column anonymization
    • then Confirm & ingest (transformed rows only)
  6. Confirm & ingest (transformed rows only)
    • then Dataset ready
  7. Dataset ready
Compliance: Uploading stores nothing. Every file is pseudonymized or anonymised the moment it is analysed, and only the transformed rows are written after you confirm. PII detection fails cautious — columns are flagged “Identifies a person / Could help identify / Sensitive”, and setting a PII column to “keep” raises a red “stores raw values” warning.
Watch out: With no organisation membership you’ll see “No data workspace yet”. Insurers and TPAs can create their own org; anyone else must ask a BimaHaq admin to be added. Org membership is the per-tenant boundary, enforced on the server.
Note: A file over the per-dataset row cap ingests only its first rows and is marked “(truncated to the row cap)”. If ingest fails the dataset badge reads “failed” with the error.

7. Explore KPIs, build a report, and ask your data

On a ready dataset you get KPI tiles, a pivot/chart report builder, plain-English questions, anomaly and predictive views, and exports — all over anonymised data.

  1. 1
    Open a ready dataset

    Click a dataset in the left list. The Dashboard tab shows KPI tiles and an “Anonymization applied at ingest” summary.

    Dashboard /data
  2. 2
    Build a pivot report

    In the Report builder pick up to three group-by columns and a measure (count / sum / avg / min / max), then run it to render a bar chart and pivot table.

    Run /data
  3. 3
    Ask your data in plain English

    On the Ask tab, type a question such as “rejection rate by insurer” and ask it.

    Ask /data
  4. 4
    Check anomalies and segments

    Open the Anomaly / fraud and Predictive tabs; they load on first open.

    Predictive /data
  5. 5
    Export the report

    Download the current report as PDF, XLSX or CSV.

    PDF /data

    A shareable report file

Analyse a dataset
StartOpen a ready dataset
Read KPI tiles (Dashboard)
Build a pivot report (Run)
DecisionAI provider configured?
  • no: go to Use the report builder only
Ask in plain English
  • go to Export PDF / XLSX / CSV
Use the report builder only
DoneExport PDF / XLSX / CSV
Diagram source (mermaid)
flowchart TB
  ds(["Open a ready dataset"])
  kpi["Read KPI tiles Dashboard"]
  pivot["Build a pivot report Run"]
  ask{"AI provider configured?"}
  nl["Ask in plain English"]
  builder["Use the report builder only"]
  export(["Export PDF / XLSX / CSV"])
  ds --> kpi
  kpi --> pivot
  pivot --> ask
  ask -->|"yes"| nl
  ask -->|"no"| builder
  nl --> export
  builder --> export
  1. Open a ready dataset
    • then Read KPI tiles (Dashboard)
  2. Read KPI tiles (Dashboard)
    • then Build a pivot report (Run)
  3. Build a pivot report (Run)
    • then AI provider configured?
  4. AI provider configured?
    • yes: Ask in plain English
    • no: Use the report builder only
  5. Ask in plain English
    • then Export PDF / XLSX / CSV
  6. Use the report builder only
    • then Export PDF / XLSX / CSV
  7. Export PDF / XLSX / CSV
Compliance: Groups below the privacy threshold are merged into a suppressed bucket (k-anonymity) — the pivot protects counts at the person level, not just at the row level.
Note: “Ask your data” needs an AI provider configured; without one the Ask tab shows an amber note and you use the report builder instead. The Predictive tab needs a claim-status column, and a large dataset may still show “Anonymizing & processing…” with a “Check again” button.

8. Privacy, boundaries & compliance

A few rules define what this role can and cannot do. They protect the neutrality of the room and the privacy of the data.

  • Raw personal data is never stored on the data platform — files are anonymised on upload and only transformed rows are written after you approve the policy.
  • You cannot close a case or record its outcome — those controls belong to the case manager. The Outcome tab is read-only for you.
  • You cannot send the eSign envelope or schedule/cancel meetings — those are case-manager and admin actions. You sign your own row and join sessions.
  • Settlement steps are on-the-record — rejecting needs a written reason and accepting needs a confirmation before the case moves to Resolved.
  • No outcome is guaranteed — the room facilitates a settlement; it does not promise one, and BimaHaq drafts paperwork without promising any result.
Compliance: BimaHaq’s AI never auto-sends anything customer-facing and never issues a claim verdict. On the data platform, natural-language answers are analytics over your own anonymised data — not advice or a verdict on any individual claim.

Questions people ask

How do I get an account?
A BimaHaq admin invites you and assigns the insurer_rep role. You set your password from the invitation email and sign in at /auth/login — there is no self-signup for staff.
Why can’t I find the data platform in the menu?
There is no in-app link to /data for your role. Reach your Resolution Workspace at /resolution as your login landing, and open the analytics platform by typing /data in the address bar.
Why can’t I accept my own settlement offer?
You can’t — on your own pending proposal only “Withdraw” is shown. Accept, Reject and Counter appear only on the other side’s offer, so neither party can accept its own figure.
Can I close the case once we settle?
No. Accepting a proposal moves the case to Resolved automatically, but recording the final outcome and closing the room are case-manager actions. You sign your row in the eSign tab; the case manager handles the rest.
Is my organisation’s uploaded data safe?
Yes. Uploading analyses the file without storing it; you approve how each column is anonymised, and only transformed rows are written. Small groups are suppressed by k-anonymity, and keeping a PII column raw triggers an explicit warning.
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.