How does the integration process work?
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.