LIVE SYSTEMS
Keep broking records and controls in WinBEAT
- WinBEAT or WinBEAT NEXT workflow
- Sunrise Exchange transactions
- iClose enquiry handling
- Background Funding and trust accounting
WinBEATInsurance broking AI integration
AI automation across WinBEAT and the rest of your software.
Connect approved WinBEAT policy and client context with Sunrise, funding, enquiries, and reviewed communication where supported.
Access confirmed before build. Start with one reviewed workflow.
Connect with
A real request in Teams
Ask once. Get the work ready for review.
This is the kind of request your team could ask after we connect WinBEAT. Horizon checks the agreed information alongside Sunrise Exchange, Premium funding providers, iClose, Trust accounting and returns one useful result for review.
Microsoft Teams
JH
@Horizon a client email just landed. Work it through WinBEAT and get the follow-up ready.
H
On it. Reading it now.
Client email read in Outlook✓Renewal preparation summaries with policy context✓Claims notification triage and missing-info chasing✓Reply drafted back to the client✓Reply drafted in Outlook, held for your sign-off
WinBEATDoneOutlookDone
Sunrise ExchangeConnected
JAVLNConnected
Keep WinBEAT
WinBEAT stays in place. Horizon connects the work around it.
The connector extends the software your team already knows. It does not replace WinBEAT or present native product features as Horizon features.
The rest of your approved stack
- Use approved WinBEAT records from Teams, Copilot, Claude, or ChatGPT
- Combine relevant records with Microsoft 365 and adjacent business systems
- Prepare cited summaries, drafts, and checklists for a person to review
- Keep permissions, audit context, and approval gates around every action
Questions worth asking
Use WinBEAT without jumping between systems.
Ask in the AI tool your team already uses. Horizon checks only the approved WinBEAT records and connected sources needed for that question.
Can we bring approved Sunrise transaction context beside the relevant WinBEAT ledger records for review?
WinBEAT + Sunrise ExchangeCan we use approved funding and client status to prepare a targeted signature or information request?
WinBEAT + Premium funding providersCan we classify approved iClose enquiries and prepare routing suggestions for the broker queue?
WinBEAT + iCloseCan we combine approved policy and client context into a reviewed renewal summary and correspondence draft?
WinBEAT + Trust accountingWhat is waiting in WinBEAT because another system holds the missing context?
WinBEAT + Microsoft 365Which next actions can be prepared from approved WinBEAT records for a person to review?
WinBEAT + your AI tool
Safe first release
Confirm access. Then prove one useful connection.
Current evidence describes WinBEAT NEXT as API-ready with external interfaces planned, but does not establish general public developer access. Scope depends on an approved vendor or partner path.
- 01 Confirm access. Confirm the approved WinBEAT records, users, scopes, and connection path. Current evidence describes WinBEAT NEXT as API-ready with external interfaces planned, but does not establish general public developer access. Scope depends on an approved vendor or partner path.
- 02 Choose one workflow. Select one high-value workflow, its connected systems, success measure, and human review point.
- 03 Build and test. Test with approved sample records, verify permissions and citations, then plan a controlled rollout.
Often paired with
Software we build WinBEAT workflows alongside.
Common questions
WinBEAT AI integration, answered.
Can Horizon connect WinBEAT to our AI tools?
Potentially. Current evidence describes WinBEAT NEXT as API-ready with external interfaces planned, but does not establish general public developer access. Scope depends on an approved vendor or partner path. Horizon first confirms the available records, permissions, and approved connection path.
Which AI tools can the workflow use?
The workflow can be designed for Microsoft Teams, Microsoft Copilot, Claude, ChatGPT, or a custom interface, subject to the client plan and security settings.
Does this replace what WinBEAT already does?
No. WinBEAT remains the broking and trust system of record, with responsible staff reviewing every consequential action. Horizon focuses on approved cross-system work around the product.
What should the first pilot cover?
Start with one repeatable workflow that has clear source records, a named reviewer, and a measurable reduction in manual handling.
How is access controlled?
Use least-privilege access, approved users and scopes, tenant controls, logging, and human approval before any consequential write or external send.
Can it work with our other systems?
That is the purpose of the pilot. Horizon confirms each adjacent system and connection path before defining the final workflow.
WinBEAT integration session
Show us what you want WinBEAT connected to.
We will confirm the access path, the systems in scope and the safest first workflow.
30 min with our Director. No sales rep, no follow-up.