Sign in Start helping customers

Integrations

What connects, and where it stops.

18 connections, and every one states what data crosses the boundary in each direction, what permissions are requested, and what it will not do.

One architectural rule governs this catalogue: Resolivo owns service context and resolution, and does not duplicate customer, finance, email or workforce data owned elsewhere. Almost every connection below is therefore a read connection, and the pages say so rather than implying a sync you would have to reconcile later.

Communication

Gmail

The shared mailbox your customers already write to.

Outlook

The same connection for a Microsoft estate.

Communications inbox

Our own messaging layer — one message, several meanings.

Slack

Alerts and approvals where the team already is.

Microsoft Teams

The same alerts and approvals, in a Microsoft estate.

Customer data

Customer record

Our own customer system — it owns who the customer is.

HubSpot

Read customer identity from the CRM you already run.

Salesforce

The same read-first connection for a Salesforce estate.

Billing & payments

Finance ledger

Our own accounting layer — so "was this paid?" has a real answer.

Stripe

Payment and subscription status, read-only.

Xero

Invoices and payment status for invoice-based businesses.

Website & product

Website platform

Our own website product — widget, help centre, portal and status page.

Behaviour analytics

What the customer did just before they asked for help — where consent allows.

Content graph

Our own content system — turn a knowledge gap into published content.

Workforce

Workforce platform

Our own people system — route by responsibility, skill and availability.

Governance & consent

Governance register

Our own governance layer — for the cases that must follow a procedure.

Consent engine

Our own consent layer — read, never recreated.

Developer

API & webhooks

A scoped API and events, for the system nobody has integrated.

Not on the list?

A documented read API and a handful of lifecycle events cover the system every software business has and nobody has integrated.

Start helping customers Connect my inbox

Keep the mailbox you already use · The AI is never metered · [email protected]