HorizonStack runs autonomous agents that carry regulated, multi-step work from first trigger to closed outcome — across voice, SMS, email, and the systems you already run on.
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.
Go ahead. I'll need the schedule of values updated first.
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.
Send the comparison, then let's talk Thursday.
Illustrative. Names, numbers, and transcripts are synthetic.
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.
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.
▌Illustrative. Names, numbers, and transcripts are synthetic.
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.
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?
yes, and does the old rate still apply
It does through the end of the quarter. Link's sent — it's a single upload, and I'll confirm the moment it lands.
Illustrative. Names, numbers, and transcripts are synthetic.
HorizonStack agents watch for the accounts that went quiet, reach out on the channel the customer actually answers, resolve the one blocker holding things up, and stay with it until the account is live again.
This is not a chatbot handling a question. It is a single unit of work that runs for weeks — across phone calls, texts, emails, portals, and your APIs — with one agent accountable for the outcome the whole way through.
Goal: Bind Dana's $2.4M property renewal before October 14.
Inbound · broker portal
Goal: Bind Dana's $2.4M property renewal before October 14.
Goal: Overturn the documentation denial on claim CLM-90144-R.
Goal: Get Priya's paused account back to active.
Goal: Get the replacement unit installed at the Tulsa site.
Meridian holds the job together: durable memory that survives weeks of contact, a policy engine that makes the next move predictable, and compliance controls that apply on every channel an agent touches.
Anything that opens or advances a job. An API call from your system, an inbound conversation, a portal changing state, a deadline coming into range, or the recorded result of the agent’s own last move.
Every trigger is read against the full history of the job, and the next move is chosen by rules you can inspect. The same situation produces the same decision, which is what makes the agent auditable.
Committed future work, each item with a time attached. A callback at 4pm, a document chase on Thursday, an escalation if nothing has landed by day nine.
The agent doing the work — on the phone, over SMS, by email, or inside a system of record. Each contact is transcribed, scored, and written back as the next trigger.
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
Ninety days out, the agent opens the renewal, pulls loss runs, chases updated exposure schedules from the insured, pushes submissions to carriers, and puts a like-for-like comparison in front of the broker with time left to negotiate. The broker's first involvement is the decision, not the paperwork.
Revenue cycle
19 days
Low-dollar denials get abandoned because the recovery costs more than the claim. The agent calls the payer, waits out the queue, finds the desk that can actually reopen the claim, supplies what was missing, and writes the disposition back with enough detail that the biller does not have to re-litigate it.
Enterprise IT
under 4 hours
Requests for system access stall because approval, provisioning, and confirmation live in three different places. The agent reads the request, identifies the correct approver, follows up until approval lands, provisions through the identity platform, verifies the user can actually get in, and closes the ticket. Anything it cannot resolve is escalated with the full history attached rather than handed over cold.
People operations
34 days
A start date depends on a background check vendor, an equipment shipment, payroll enrollment, and half a dozen approvals that no single team tracks. The agent runs the whole sequence from offer acceptance to day thirty, chasing whichever thread is blocking, and flags the start date as at risk early enough for someone to do something about it.
Customer operations
6 days
A disputed charge needs contract terms read, usage checked, an approval obtained, and a credit actually posted — four steps across three systems, which is why disputes age. The agent runs all four, keeps the customer informed at each one, and does not close the case until the credit appears on the account.
5
deployment patterns live
34 days
longest job run end to end
0
seats sold — priced on outcomes