Skip to content
Book a demo
GIVE EVERY THREAD A HOME

From incoming email
to connected follow-up.

Bring enquiries into a shared queue without losing the original thread. Associate the contact, preserve context and keep replies under clear ownership.

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

Keep the original context.

SOURCEEmail
ENQUIRYolivia@example.com
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

Connect the mailbox

Authorise the specific mailbox and choose which folders or addresses feed enquiries.

02

Match the sender

Use contact identifiers and thread IDs to avoid duplicating the same conversation.

03

Reply & record

Assign an owner and keep replies, delivery events and follow-up tasks with the lead.

TRY THE MAPPING DESIGN

Source fields, with a clear destination.

Sample only
Email fieldCRM field
Sender address
Sender display name
Subject line
Message body
Message / thread ID
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 shared mailbox or approved inbound email route.
  • Minimum required read/send scopes and a revocation process.
  • A defined approach to attachments, retention and spam handling.
The CRM does not wait for an integration.

Agents can enter an email enquiry manually and preserve its context while the mailbox integration is being set up. 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 email?

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.