Selected work / insurance knowledge

Make trusted answers easier to create and find.

An insurance company needed a clearer path from internal knowledge authoring and review to organized, discoverable guidance. Halo supported the business analysis connecting those workflows, stakeholders, and validation needs.

  • Knowledge management
  • Salesforce
  • BA & QA readiness
See Halo’s role ↓

The operating problem

What made the work difficult?

Authors, reviewers, approvers, and readers need different things from the same knowledge system. Ownership, review steps, categories, and search behavior must work together.

  • Article handoffs and approval expectations needed clarification.

  • Internal content and approved public guidance required distinct boundaries.

  • Topics, categories, and search needed a reader-centered validation path.

What Halo did

Connect the people, rules, and system.

Halo contributed Salesforce business analysis across internal Knowledge and an external knowledge experience, organizing stakeholder questions into user stories, acceptance criteria, process guidance, and QA/UAT scenarios.

  • Define authoring, review, approval, and publication questions.
  • Connect topics, categories, notifications, and visibility to user needs.
  • Keep business decisions and QA evidence traceable across teams.

Watch it, then try it

Watch an answer move through review

A short narrated model of knowledge authoring and improvement. This is not a deployed client system. AI-generated narration; captions and transcript provided. No information is collected or sent.

Read the video transcript
Insurance knowledge — an answer with a path to trust

AI-generated narration. All visuals are illustrative, fictional records.

00:00:00.000  An author begins with the reader's question, audience, and accountable owner. This is a fictional model, not a client screenshot.

00:00:08.887  A reviewer checks accuracy and publication conditions. Unresolved policy wording stays an open item until a person validates it.

00:00:18.371  Clear titles and categories help readers find approved guidance. This sequence does not demonstrate a live search or AI answer engine.

00:00:28.153  When readers ask about an exception, the knowledge owner can open a policy review or flag uncertainty. No unreviewed answer is published.

Explore the handoff / knowledge work

An answer needs a path to trust.

Follow an illustrative article from a reader question to review, discovery, and improvement. Each role needs a useful view of the same guidance.

Illustrative workflow model informed by business-analysis work for an anonymous insurance company. Not a deployed client system, client screenshot, measured result, or live AI answer engine. No information is collected or sent.

ILLUSTRATIVE / K-018Four-stage illustration

01 / DRAFT

Begin with the reader’s question.

An author organizes guidance around a task, with audience, scope, and owner clear from the start.

The answer has a purpose and an accountable author.

KNOWLEDGE RECORDDraft
Reader questionHow do I prepare for a coverage review?
AudienceMember services team
OwnerKnowledge author

Fictional example · no record is created.

02 / REVIEW

Separate writing from approval.

A reviewer checks accuracy and publication conditions. Unresolved wording remains visible.

Trust is designed into the handoff.

KNOWLEDGE RECORDPending review
Ready checkAudience and owner identified
Open itemPolicy wording to confirm
Next ownerPolicy reviewer

Fictional example · no record is created.

03 / FIND

Put the answer where search begins.

Plain-language titles and categories help a reader recognize approved guidance. This is not a live search service.

The right answer is easier to locate and identify.

KNOWLEDGE RECORDApproved
Reader asksCoverage review preparation
Illustrative resultPrepare for a coverage review
SourceReviewed guidance

Fictional example · no record is created.

04 / IMPROVE

Keep guidance useful after launch.

Reader questions and stale wording start a new review cycle rather than silently changing approved content.

Feedback has a responsible path back to the source.

KNOWLEDGE RECORDReview due
SignalReaders ask about one exception
Proposed actionClarify, validate, then republish
Next ownerKnowledge owner

Fictional example · no record is created.

Watch it, then try it

See how guidance becomes a service answer.

Follow the full fictional path in a chaptered, silent screen sequence captured from the working demo. It shows real interface states, not a continuous cursor recording. Captions are on by default, with a readable transcript and two shorter cuts below. No client, member, or live insurance data is shown.

Watch it, then try it

Watch the insurance operations overview

A short narrated orientation to the fictional simulation. The detailed silent walkthrough remains available below. AI-generated narration; captions and transcript provided. No information is collected or sent.

Read the video transcript
Insurance operations — from guidance to follow-through

AI-generated narration. All visuals are illustrative, fictional records.

00:00:00.000  The insurance operations demo begins with a fictional knowledge article. Draft text and reviewer comments stay separate from published consumer guidance.

00:00:10.465  A correction moves through accountable review. Approval alone does not publish it; a separate authorized step changes what service staff may cite.

00:00:20.419  In a fictional inquiry, service staff check the caller and use the published revision. If a required check fails, the safe path is escalation.

00:00:30.031  An unresolved question becomes an owned case with a next action. The interactive simulation lets you explore these states without touching real client records.
Full walkthrough / from revision to resolution2 minutes 40 seconds

A timed sequence of captured interface states from the fictional, in-memory demonstration; no voiceover or client footage.

Jump to a chapter

Read the full walkthrough transcript
  1. The fictional Lumenbrook Mutual scenario connects trusted guidance, an inquiry and an accountable follow-up. It is not a client system.
  2. Article K-101 version 2 is the published consumer answer. Search does not expose internal draft text or review comments.
  3. The knowledge author creates an internal version 3. Version 2 remains published and usable.
  4. The author submits the revision for review, which creates work for a reviewer but does not release it.
  5. The reviewer inspects the instruction and responsible group.
  6. The reviewer requests a clearer owner for the effective-date exception.
  7. The author saves the clarified instruction and resubmits it. Approval applies to this revised draft.
  8. The knowledge reviewer approves the submitted version.
  9. The knowledge manager supplies the second approval required for a moderate change.
  10. The draft is approved but is still not published. The publisher has a separate release action.
  11. The publisher releases K-101 version 3. Its new consumer text is now available and a future review date is set.
  12. A new, fictional enrollment-date inquiry appears in the service workspace.
  13. The service representative accepts the call; acceptance alone does not verify the caller.
  14. The member lookup finds a subject record. Caller verification is still pending.
  15. A distinct sample check verifies the caller. Source cards remain read-only illustrations.
  16. The representative cites the newly published K-101 version 3, not an internal draft.
  17. The unresolved discrepancy becomes DEMO-CASE-011 with an owner, next action, due date and cited article version.
  18. The call ends with follow-up required, but case resolution remains separate.
  19. A service supervisor resolves the fictional case as its own action; the case retains the cited guidance and work history.
  20. Halo’s role is to design the people, decisions, requirements, tests and stewardship behind these handoffs.
Prefer a quick look? Watch two short clips
01 / The connected workflow45 seconds

From governed answer to accountable follow-up

A revision stays separate from published guidance; the inquiry uses the current answer, and an unresolved discrepancy gets an owner.

Read overview transcript
  1. A fictional insurance workflow connects reviewed guidance, a service inquiry and accountable follow-up.
  2. Knowledge search exposes the published version, while a new draft stays internal.
  3. Submitting a draft creates review work, not a public update.
  4. A representative accepts a sample inquiry, looks up the subject, completes a separate verification check and cites the published version.
  5. The discrepancy becomes a pending case with an owner, next action, due date and article version.
  6. Halo connects these decisions to roles, requirements, acceptance tests and stewardship.
02 / The service handoff30 seconds

Keep the inquiry, answer and next action together

See how a fictional representative verifies before citing guidance, then routes an unresolved question without closing it by accident.

Read service handoff transcript
  1. Published K-101 version 3 is ready in the fictional service workspace.
  2. The representative accepts a sample enrollment-date inquiry; acceptance does not verify the caller.
  3. Lookup and verification happen separately before K-101 version 3 is cited.
  4. Case DEMO-CASE-011 records the owner, next action, due date and cited article.
  5. A supervisor resolves the case separately from the call.
Explore the interactive demo →Illustrative demonstration · fictional data · no live transaction

Supported outcome

Make the next step clearer.

A clearer, reviewable operating model and validation path. The available evidence does not independently establish production deployment, UAT signoff, or measured adoption.

Start with the workflow

What work needs a clearer path?

Bring Halo the participants, friction, decisions, and desired outcome. We can help shape the process and the system together.