Skip to content
MEET YOUR LEADS WHERE THEY ARE

Four ways in.
One connected journey.

Bring authorised calls, emails, social enquiries and website submissions into a consistent lead workflow. Keep channel permissions and failure handling part of the plan.

Each channel connects through a lead source in your workspace, with its own API key and signed webhook, so you choose exactly which channels feed the CRM.

ONE RELIABLE INTAKE PATTERN

Different origins.
The same thoughtful process.

01

Validate the event

Check the source, permissions and payload before accepting a record. Keep repeated events from creating duplicate actions.

02

Map the context

Align contact details, source identifiers and enquiry content with the CRM schema. Preserve communication permission.

03

Assign & monitor

Route to a person or monitored queue. Make retries, failures and human fallback visible to the operations team.

START BEFORE YOUR INTEGRATIONS ARE READY

Manual entry and CSV
keep the work moving.

Create leads directly or review a permitted CSV export. Validate names and contact fields, inspect row errors and skip duplicate contacts before importing.

Explore lead import
CONNECT WITH CONFIDENCE

Permissions first.
Progress always.

Will every social network or mailbox work immediately?

No. Each provider needs its own supported API, account authorisation, scopes and implementation. The channel pages describe that preparation without claiming live connections.

What happens if a provider is unavailable?

The production design preserves accepted events and uses monitored retries or a failure queue. Manual entry and internal CRM workflows remain available.

Do integrations require AI?

No. Channel intake, mapping, duplicate matching and deterministic assignment are independent of an AI provider.

PUT THE PICTURE TOGETHER

Your next chapter starts with a clear view.

Explore the workspace, then shape it around the way your team sells.