Skip to content

Autonomous agents that own multi-week workflows from first trigger to closed outcome.

Weeks of calls, emails, portals, and approvals — handled end to end, with one agent accountable the whole way.

The agent lifecycle, repeating: trigger, policy, queue, contact.TRIGGERPOLICYQUEUECONTACTTRIGGERsomething starts the job
How it works

Four steps, on a loop, until the job closes.

01TRIGGER

Something opens or advances the job: an API call, a reply, a portal change, a deadline coming into range.

02POLICY

The next move is chosen against the full history of the job, by rules you can inspect.

03QUEUE

Work is committed forward with a time on it: a callback Thursday, an escalation by day nine.

04CONTACT

The agent makes the call, sends the message, updates the system — then feeds the result back in.

What an agent owns
Rowan · renewal outreachDay 1 · 7m 41s
Rowan

Your $1.85M property policy (POL-2211-C) renews November 3. I can pull loss runs and get three carrier quotes back to you before the deadline.

Dana

Go ahead. I'll need the schedule of values updated first.

Rowan · submission follow-upDay 6 · 9m 12s
Rowan

Hi Dana, two carriers came back. One is 6% under expiring with the same limits. I can walk you through the differences now or send a comparison.

Dana

Send the comparison, then let's talk Thursday.

Bound before expiryDay 11
Commercial insurance

The renewal closes without anyone chasing it.

HorizonStack agents open the renewal window on time, collect loss runs and updated exposures, chase carrier submissions through portals, and put a clean comparison in front of the broker before the policy lapses.

(816) 555·0142“This line is for eligibility only.”
attempt 1
(816) 555·0177 · appeals deskconnected · 31m 00s
attempt 2

Agent Appealing the denial on claim CLM-90144-R, an outpatient procedure denied because documentation was not received.

Rep Records received. Reprocessing at the allowed rate, expect remit in 12 days.

POST /webhook200
▌
Revenue cycle

Denied claims get worked, not written off.

HorizonStack agents call the payer, sit through the queue, find the right desk, supply the missing documentation, and report the disposition back to your billing system with the codes intact.

SMS · Day 4 · 11:02 amlive
HorizonStack

Hi Priya — your account (ACC-58203) has been paused since February and you're one document away from reactivating. Want me to send the link?

Priya

yes, and does the old rate still apply

SMS · Day 4 · 11:06 amSol
HorizonStack

It does through the end of the quarter. Link's sent — it's a single upload, and I'll confirm the moment it lands.

Account reactivatedDay 5 · rate held
Account reactivation

Dormant accounts come back on their own schedule.

HorizonStack agents watch for accounts that went quiet, reach out on the channel the customer answers, and stay with the one blocker until the account is live again.

Deployments

Five patterns we run today.

Each of these is a job that used to sit in a queue waiting for a person with time. Named references and outcome data are available under NDA.

Commercial insurance

11 days

The renewal that closes before it lapses

Ninety days out, the agent opens the renewal, pulls loss runs, chases exposures, and pushes carrier submissions. The broker's first involvement is the decision, not the paperwork.

Owns
renewal window through bind
Systems
AMS · carrier portals · email · voice
Closes when
coverage is bound before expiry

Revenue cycle

19 days

Denials that get worked instead of written off

The agent calls the payer, waits out the queue, finds the desk that can reopen the claim, and writes back a disposition detailed enough that the biller need not re-litigate it.

Owns
denial through disposition
Systems
billing system · payer lines · fax · webhooks
Closes when
the claim reprocesses or is formally exhausted

Enterprise IT

under 4 hours

Access requests that resolve without a ticket queue

The agent reads the request, finds the right approver, provisions through the identity platform, and verifies the user can get in. Anything it cannot resolve is escalated with the full history attached.

Owns
request through verified access
Systems
ITSM · identity provider · directory · chat
Closes when
the requester confirms they are in

People operations

34 days

Onboarding that finishes across every system it touches

From offer acceptance to day thirty, the agent runs the whole sequence — background check, equipment, payroll, approvals — and flags a start date at risk early enough to fix.

Owns
offer acceptance through day 30
Systems
HRIS · payroll · asset management · vendor portals
Closes when
every task is complete and the hire is fully enabled

Customer operations

6 days

Billing disputes that end in a posted credit

A disputed charge needs terms read, usage checked, an approval obtained, and a credit posted — four steps across three systems. The agent runs all four and keeps the case open until the credit appears.

Owns
dispute through posted credit
Systems
billing · CRM · entitlement records · email
Closes when
the credit is visible to the customer

5

deployment patterns live

34 days

longest job run end to end

0

seats sold — priced on outcomes

Inside a single job

Eleven days, forty touches, one owner.

A single job, plotted across every contact the agent made to close it.

Goal: Bind Dana's $2.4M property renewal before October 14.

Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
TRIGGERDay 1 · 09:41 am

Inbound · broker portal

sourcebroker.portal
eventrenewal.window_opened
policy_refPOL-2211-C
policy_typecommercial property
expiring_premium$1.85M
renews2026-11-03
incumbent_carrierdeclined to quote

Full workflow timelines

Insurance renewal

Goal: Bind Dana's $2.4M property renewal before October 14.

Day 1, 09:41 am
TRIGGER — Renewal window opened. Source: Inbound · broker portal.
Day 1, 09:41 am
POLICY — Plan the renewal. Source: Policy engine.
Day 1, 10:02 am
QUEUE — Request loss runs & SOV. Source: Scheduled work.
Day 1, 10:05 am
CONTACT — Outreach call to broker. Source: Voice · Rowan.
Day 3, 02:14 pm
TRIGGER — Documents received. Source: Inbound · email attachment.
Day 3, 02:15 pm
POLICY — Select carriers. Source: Policy engine.
Day 3, 03:40 pm
QUEUE — Build & send submissions. Source: Scheduled work.
Day 4, 11:20 am
CONTACT — Portal submission filed. Source: Portal · carrier A.
Day 6, 09:50 am
TRIGGER — Carrier quote returned. Source: Inbound · carrier portal.
Day 6, 09:52 am
POLICY — Compare quotes. Source: Policy engine.
Day 6, 10:15 am
QUEUE — Draft comparison for broker. Source: Scheduled work.
Day 7, 02:30 pm
CONTACT — Comparison review call. Source: Voice · Rowan.
Day 11, 08:30 am
TRIGGER — Bind confirmed. Source: Inbound · carrier portal.

Claim denial appeal

Goal: Overturn the documentation denial on claim CLM-90144-R.

Day 1, 08:05 am
TRIGGER — Denial posted. Source: Inbound · 835 remit.
Day 1, 08:06 am
POLICY — Classify denial. Source: Policy engine.
Day 1, 08:30 am
QUEUE — Pull chart notes. Source: Scheduled work.
Day 2, 10:12 am
CONTACT — Records retrieved. Source: System · EHR.
Day 2, 10:15 am
TRIGGER — Records ready. Source: Inbound · records service.
Day 2, 10:16 am
POLICY — Choose appeal path. Source: Policy engine.
Day 3, 09:00 am
QUEUE — Queue payer call. Source: Scheduled work.
Day 3, 09:05 am
CONTACT — Wrong department. Source: Voice subagent.
Day 4, 10:40 am
QUEUE — Retry appeals desk. Source: Scheduled work.
Day 4, 11:11 am
CONTACT — Appeal submitted on call. Source: Voice subagent.
Day 4, 11:42 am
TRIGGER — Reprocessing confirmed. Source: Voice result.
Day 4, 11:43 am
POLICY — Schedule remit watch. Source: Policy engine.
Day 11, 03:20 pm
TRIGGER — Remit posted. Source: Inbound · 835 remit.

Account reactivation

Goal: Get Priya's paused account back to active.

Day 1, 07:30 am
TRIGGER — Dormancy flag raised. Source: Inbound · billing system.
Day 1, 07:31 am
POLICY — Pick outreach channel. Source: Policy engine.
Day 1, 08:00 am
QUEUE — Schedule SMS outreach. Source: Scheduled work.
Day 4, 11:02 am
CONTACT — Outbound SMS + reply. Source: SMS · Sol.
Day 4, 11:03 am
TRIGGER — Reply received. Source: Inbound · SMS.
Day 4, 11:04 am
POLICY — Answer & send link. Source: Policy engine.
Day 4, 11:05 am
QUEUE — Send upload link. Source: Scheduled work.
Day 4, 11:06 am
CONTACT — Confirm & guide. Source: SMS · Sol.
Day 5, 09:20 am
TRIGGER — Document uploaded. Source: Inbound · upload event.
Day 5, 09:21 am
QUEUE — Verify document. Source: API call.
Day 5, 09:23 am
POLICY — Clear to reactivate. Source: Policy engine.
Day 5, 09:25 am
CONTACT — Account reactivated. Source: SMS · Sol.

Install scheduling

Goal: Get the replacement unit installed at the Tulsa site.

Day 1, 10:00 am
TRIGGER — Replacement approved. Source: Inbound · service ticket.
Day 1, 10:01 am
POLICY — Plan the install. Source: Policy engine.
Day 1, 10:20 am
QUEUE — Order unit & parts. Source: API call.
Day 2, 09:30 am
CONTACT — Confirm site access. Source: Voice subagent.
Day 6, 08:15 am
TRIGGER — Parts delivered. Source: Inbound · supplier webhook.
Day 6, 08:16 am
POLICY — Schedule the crew. Source: Policy engine.
Day 6, 09:00 am
QUEUE — Book install crew. Source: Scheduled work.
Day 7, 01:10 pm
CONTACT — Confirm with site. Source: SMS subagent.
Day 8, 07:50 am
TRIGGER — Crew on site. Source: Inbound · dispatch app.
Day 8, 02:40 pm
CONTACT — Install completed. Source: Voice subagent.
Day 8, 02:45 pm
POLICY — Verify & close. Source: Policy engine.
Day 9, 09:00 am
QUEUE — Register warranty & invoice. Source: API call.
Day 9, 09:05 am
TRIGGER — Ticket closed. Source: Inbound · CMMS.

Put an agent on the work that keeps slipping.