Evari integrates with the core systems used by insurance brokers and MGAs. The specific integrations required for your operation are confirmed during the Week 1 discovery phase and built as part of the sprint.
Policy administration systems
- Socotra
- Vertafore (AMS360, Sagitta)
- Applied Epic
- Guidewire (read access)
- Custom or in-house PAS systems (via API)
Communication and email
- Microsoft 365 (Exchange/Outlook)
- Google Workspace (Gmail)
- Shared inboxes and distribution lists
CRM and workflow
- Salesforce
- HubSpot
- Microsoft Dynamics
Broker portals and platforms
- Custom broker portals (via API or scraping where API is unavailable)
- Market platforms (on a case-by-case basis)
Document and file storage
- SharePoint and OneDrive
- Google Drive
- Network file shares (via secure connector)
- Email attachments of all common formats (PDF, Word, Excel, images, scanned documents)
What if my system is not listed?
If your system is not listed, it does not mean we cannot integrate with it. Most modern systems expose an API that we can connect to. Contact us and we will assess the integration as part of the discovery phase. Bespoke integrations are included in the sprint cost.
All integrations are built and tested during the sprint. You do not need technical expertise to get integrations working — we handle everything.
What we need from you
During the Week 1 discovery phase, we will identify which systems the assistant needs to connect to and what it needs to do in each. Before the build phase starts, we will ask you to provide:
- API credentials or OAuth access for each connected system
- A test environment or sandbox (where available) for development and testing
- A named IT or operations contact who can help resolve access issues quickly
Most brokers can get this sorted within the first week. The biggest delay is usually waiting for IT to provision API credentials.
How the integration is built
We use the official APIs for each system where they exist. For systems without APIs, we work with you to find the best approach — file exports, email-based handoffs, or custom connectors.
All integration code is built as part of the sprint and runs within your security boundary. We do not use any general-purpose middleware that routes your data through third-party services.
Testing
All integrations are tested against your real data in a staging environment before go-live. You review the output and approve before the assistant is activated in production.
Ongoing maintenance
Once live, integrations are maintained as part of your platform subscription. If a system upgrade changes an API and breaks an integration, we fix it under your support agreement. You do not need to raise separate change requests or pay for integration maintenance.
Yes. Evari can integrate with custom and in-house systems, provided there is a mechanism to exchange data. This is one of the more common questions we get from brokers and MGAs who have built proprietary tools over the years.
What we need to integrate
If your system exposes an API (REST, SOAP, GraphQL), we can connect to it. During the Week 1 discovery phase, we will review your API documentation or work with your development team to understand the available endpoints.
If your system does not have an API, there are other options:
- File-based exchange — the assistant can read from and write to a shared folder, network drive, or SFTP location
- Email-based exchange — the assistant can parse structured emails or attachments that your system generates
- Database access — for internal systems, we can connect directly to the database with read or read/write permissions (requires your IT team's involvement)
What this costs
Custom integrations are included in the sprint cost. There is no separate integration fee. If a custom integration is unusually complex or requires significant back-and-forth with your development team, we will flag this during discovery and discuss whether it affects the sprint scope.
Long-term maintenance
Once the integration is live, it is maintained under your platform subscription. If your internal system changes and breaks the integration, we will work with you to update the connector. Depending on the change, this may be covered under standard support or may require a small follow-on engagement.
What if we are building a new system?
If your organisation is mid-way through building or migrating to a new system, let us know during discovery. We can design the integration with the new system as the target rather than the current one, or build a temporary bridge to the current system that can be replaced when the new one goes live.