Home health + hospiceWellSky is widely used across home-based and post-acute care
Auth-gated visitshome health visits and episodes depend on timely payer authorization
Forward deployedagents are built around your WellSky setup and referral sources

Home health runs on referrals coming in fast and authorizations that have to clear before visits can bill. WellSky, whose home health platform was formerly Kinnser, carries that workload across home health, hospice, personal care, and therapy agencies. Flexbone deploys voice and browser agents inside WellSky so Medicare and Medicare Advantage eligibility checks, plan authorizations, physician order follow-up, and referral intake read and write the same records your intake and billing teams already use.

Which agencies use WellSky?

WellSky is a leading platform for home-based and post-acute care. Its products span home health (formerly Kinnser), hospice and palliative care, personal care for private duty agencies, and therapy and rehab, covering referral intake, scheduling, and the revenue cycle. Home-based care has a specific pressure: referrals arrive from hospitals and physicians and need fast turnaround, and visits and episodes depend on payer authorization that has to be in place before care is delivered, or the visits do not bill. Flexbone operates inside WellSky so this work is written where your intake and authorization teams already work.

Complimentary Flexbone audit

Get an outside read on your WellSky workflow

In 30 minutes we map your current volume, the payers and systems involved, where staff time goes, and the highest-ROI calls and follow-ups Flexbone can take off your team first, scoped to the work you actually run.

Book an audit →

Which front and back office workflows does Flexbone run?

Flexbone handles inbound referral intake and the outreach to confirm details and schedule the start of care, verifies eligibility, and submits and tracks home health and hospice authorizations so episodes are covered before visits happen. It works denials and the reauthorization cadence that longer episodes require. The post-acute prior authorization page covers the authorization detail, and the referral management page covers intake.

Can AI process home health referrals inside WellSky?

Yes. Voice agents answer referral calls from hospital discharge planners, case managers, and physician offices, confirm demographics, insurance, and orders, and write the referral to WellSky. Browser agents monitor referral portals where hospital systems use them. The intake team receives a complete referral instead of a callback list, which shortens the time from referral to start of care.

Can AI verify eligibility and benefits inside WellSky?

Yes. Flexbone verifies coverage at referral, before the start of care, and again during long episodes. The agents identify whether the patient holds Original Medicare, a Medicare Advantage plan, or Medicaid, because that decides whether an authorization gates the episode. They read payer responses and portals, call the plan when benefit detail is missing, and write the verified result to the WellSky record. A coverage change mid-episode is caught by the recheck rather than by a denied claim.

How does AI handle authorization and reauthorization in WellSky?

Many Medicare Advantage and Medicaid managed care plans authorize a set number of visits or a set span. Flexbone submits the initial authorization with the order and assessment detail from WellSky, tracks it to a decision, and submits reauthorization before the approved visits run out. Authorization numbers and spans are written back to WellSky. The agents also track unsigned physician orders and place the follow-up calls to the ordering practice, because Medicare home health claims need signed orders before the institutional 837 claim can go out. The post-acute EHR authorization page has the per-system detail.

Complimentary pilot

Have Flexbone run your WellSky workflow on real cases

A complimentary six-week pilot once the BAA is signed, with a weekly review of what the agents handled, which results were written back to your system, and the hours your team got back.

Start a pilot →

How does Flexbone deploy inside WellSky?

Flexbone is forward-deployed: we build the agents around your WellSky configuration, referral sources, and payer mix, validate them against your real intake and authorization patterns, and keep refining them. The agents work in the WellSky web interface the way staff do, and use interfaces where the vendor offers them. Flexbone is not a certified WellSky integration and not a WellSky partner. Results write back to WellSky, and exceptions go to staff with context. We scope the rollout to the workflows that protect the most billable visits first.

How Does a Flexbone Deployment Work?

Every deployment starts from the work as your team does it today, not from a product demo. The steps below are the same whether the first agent answers phones, checks eligibility, or files incoming documents.

  1. Audit first, then automate. We listen to a sample of your calls and read the work queues, then agree with your team on which work to automate first. The audit is complimentary.
  2. Forward-deployed engineers map your SOPs. An engineer sits with the staff who do the work and turns your written and unwritten rules into agent logic.
  3. Agents act on your rules, and exceptions go to a person. Each step follows logic built from your SOPs. A case outside those rules, or one the agent is not confident about, goes to your team with the context attached.
  4. Every action leaves a record. A check in a web application saves a screenshot, a call saves a transcript, and results are written back where your team already looks.
  5. Start with one or two agents on the systems you already run. The agents work in your EHR, practice management system, phone system, and the web applications your staff use, as they are configured today, so nothing is migrated or rebuilt.
  6. The same team stays after go-live. We monitor results, tune the agents as payers and workflows change, and add agents as new work is found.

The engagement model is described in more detail in forward-deployed engineering for healthcare contact centers.