Skip to content
Book a demo
KEEP CAMPAIGN INTENT INTACT

A social enquiry.
A real opportunity.

Turn authorised social lead forms and messages into a consistent lead workflow. Keep campaign context, contact permission and response ownership together.

Book a demo Explore the workspace
Human-first. AI optional.
SOCIAL MEDIA TO LEADVERA

Keep the original context.

SOURCESocial media
ENQUIRYWebsite viewing campaign
DESTINATIONShared lead workspace
OWNERSHIPHuman agent or monitored queue
Clear source. Clear owner. Clear next step.

Integration design. Live connection required.

FROM SOURCE TO NEXT STEP

An intake path
your team can follow.

01

Choose the source

Select the authorised page, form or supported message inbox to connect.

02

Map the submitted data

Align contact answers and campaign identifiers with the CRM fields.

03

Assign the conversation

Apply deterministic rules, then follow up through a permitted channel.

TRY THE MAPPING DESIGN

Source fields, with a clear destination.

Sample only
Social media fieldCRM field
Full name
Lead form email
Lead form phone
Campaign / form ID
Customer question
Mapping example only.
BEFORE YOU CONNECT

The right access.
The right foundations.

Confirm provider support and organisation approval before implementation. A setup screen alone does not grant access to the service.

Review the implementation controls
  • An authorised business account, page and relevant platform application access.
  • Supported lead-form or messaging endpoints with the necessary permissions.
  • A channel-specific consent, response-window and deletion policy.
The CRM does not wait for an integration.

Social leads can be added manually or imported from an authorised export while direct integration is being configured. Core follow-up and pipeline tools work with AI off.

Open lead workspace
A FEW PRACTICAL DETAILS

Know what happens
behind the connection.

How do I connect social media?

Create a lead source in your workspace, choose the channel and send events to its intake address with the source’s API key. Each event is checked, deduplicated and assigned by your rules.

How are duplicates and repeated events handled?

The production design separates contact matching from event idempotency. Normalised contact identifiers help associate the person; provider event IDs prevent repeated processing.

Can we choose the human owner?

Yes. Manual assignment and deterministic routing remain available. AI is optional, with human fallback when it is disabled or unavailable.

BRING THE OTHER CHANNELS TOGETHER

One relationship, wherever it begins.

PUT THE PICTURE TOGETHER

Give your next enquiry a clear path.

Map the source, agree the workflow and put the team in control.