Skip to main content
ioInsureOS
Sign inBook a demo
InsureOS

Docs

Everything you need to wire InsureOS into your brokerage in an afternoon. Each section links to the in-app screen that owns the setting.

1. Create your workspace

Sign up at /signup. The first user becomes the tenant admin. Invite teammates from Settings → Users; roles are tenant_admin, manager, adviser, and sdr.

2. Connect your providers

Go to Settings → Comms providers and add an API key per channel:

  • SMS / voice — Twilio (account SID + auth token + messaging service SID).
  • WhatsApp — Twilio WhatsApp or Meta Cloud API.
  • Email — SendGrid (API key + verified sender + per-tenant event webhook secret).
  • Calendar — Google or Microsoft via OAuth (Settings → My connections).

Each card shows a masked last_four, last test timestamp, and a rotate/disconnect action. The Provider health panel above the cards aggregates the last 24 hours of delivery events.

3. Ingest leads

Five ways to get leads in:

  • Manual — Leads → New lead.
  • CSV import — Leads → Import with column mapping and consent capture.
  • Google Sheets — Leads → Sheets import pulls a tab on demand.
  • CRM sync — Leads → CRM import via the configured CRM connector.
  • Public webhook — POST to /api/public/website/<tenantId> from your marketing site (see below).

4. Public lead-capture API

Embed this on any form on your marketing site. No authentication needed; the tenant id in the URL is the routing key. Consent must be explicit.

POST https://yourdomain.com/api/public/website/<tenantId>
Content-Type: application/json

{
  "full_name": "Jane Doe",
  "email": "jane@example.com",
  "phone": "+447700900000",
  "product_interest": "life",
  "consent": { "email": true, "sms": false },
  "source": "homepage-hero",
  "utm": { "source": "google", "campaign": "brand" }
}

Returns 201 with the lead id, or 400 if validation fails. Rate-limited per IP. Leads land in the new stage and trigger any sequences enrolled on the new lead event.

5. Sequences & automations

Build multi-channel sequences in Sequences (drip steps with delay) and event-driven flows in Automations (lead created, status changed, score crossed threshold). Each send is gated against your plan's channel pool and the lead's consent record.

6. Compliance

Every lead has a Right to be forgotten action under Compliance that redacts the row plus all attached interactions and emails. A daily cron sweeps lost leads past your retention_days setting (defaults to 730 days).

7. Webhooks & cron

External callers hit routes under /api/public/*. The platform exposes:

  • /api/public/webhooks/<provider>/<tenantId> — Meta / Google / LinkedIn / Twilio / WhatsApp inbound.
  • /api/public/webhooks/sendgrid/<tenantId> — SendGrid event webhook (delivered / bounce / open).
  • /api/public/webhooks/stripe — billing events.
  • /api/public/cron/retention-sweep — daily retention scrub.

Need help?

Email your operator or open an issue in the workspace's shared inbox.