LIVE SYSTEMS
Build around the Mercury Nexus workflow
- Client Centre fact-find
- Compliance Centre
- Lender Approval Dashboard
- Mercury Nexus Analytics and Connective AI
Mercury NexusFinancial advice and mortgage broking AI integration
AI automation across Mercury Nexus and the rest of your software.
Connect approved Mercury Nexus client and deal context with fact-find, lender, and lodgement workflow.
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 Mercury Nexus. Horizon checks the agreed information alongside Client Centre, Financial Passport, ApplyOnline, Loanapp and returns one useful result for review.
Microsoft Teams
JH
@Horizon a client email just landed. Work it through Mercury Nexus and get the follow-up ready.
H
On it. Reading it now.
Client email read in Outlook✓Lead triage with broker assignment drafts✓Application file completeness checks✓Reply drafted back to the client✓Reply drafted in Outlook, held for your sign-off
Mercury NexusDoneOutlookDone
SalestrekkerConnected
BrokerEngineConnected
ApplyOnlineConnected
LoanappConnected
Keep Mercury Nexus
Mercury Nexus stays in place. Horizon connects the work around it.
The connector extends the software your team already knows. It does not replace Mercury Nexus or present native product features as Horizon features.
The rest of your approved stack
- Use approved Mercury Nexus 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 Mercury Nexus without jumping between systems.
Ask in the AI tool your team already uses. Horizon checks only the approved Mercury Nexus records and connected sources needed for that question.
Can we combine approved Client Centre responses with Financial Passport data and the existing CRM record?
Mercury Nexus + Client CentreCan we prepare a reviewed comparison brief using approved client context and lender workflow information?
Mercury Nexus + Financial PassportCan we check approved application fields and required documents before a person sends the file to ApplyOnline or Loanapp?
Mercury Nexus + ApplyOnlineCan we use approved CRM, compliance, and lodgement status to prepare a client update for broker review?
Mercury Nexus + LoanappWhat is waiting in Mercury Nexus because another system holds the missing context?
Mercury Nexus + Microsoft 365Which next actions can be prepared from approved Mercury Nexus records for a person to review?
Mercury Nexus + your AI tool
Safe first release
Confirm access. Then prove one useful connection.
Mercury Nexus documents an Open API, but the client tenancy, approved applications, record scopes, and write permissions must be confirmed.
- 01 Confirm access. Confirm the approved Mercury Nexus records, users, scopes, and connection path. Mercury Nexus documents an Open API, but the client tenancy, approved applications, record scopes, and write permissions must be confirmed.
- 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 Mercury Nexus workflows alongside.
Common questions
Mercury Nexus AI integration, answered.
Can Horizon connect Mercury Nexus to our AI tools?
Potentially. Mercury Nexus documents an Open API, but the client tenancy, approved applications, record scopes, and write permissions must be confirmed. 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 Mercury Nexus already does?
No. Connective AI and Mercury Nexus native workflow remain in place while Horizon connects approved context across systems. 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.
Mercury Nexus integration session
Show us what you want Mercury Nexus 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.