Two channels, one prospect
Email and a phone call can land on the same person the same morning. We agree the order first — call after a reply, or after a set number of emails — so the sequence and the dialer are not competing.
Integration · Orum to lemlist
Orum and lemlist integration
Your sequences run in lemlist and your reps dial in Orum, but the two rarely know about each other. We connect them so leads reaching the call step land in the right rep’s Orum list, and what happened on the phone is written back to the lead. It is a one-time setup by our team, not a monthly middleware subscription.
- From $100, one-time setup
- No monthly fees from us
- Tested on your own calls before go-live
Orum
lemlist
One call ends in Orum. In lemlist:
- Lead reaches the call stepAdded to the rep’s Orum list
- A real person answersOrum bridges the rep in
- Outcome updates the leadAnd the sequence follows it
- One-time setup
- From $100
- Monthly fee from us
- $0
- Working days to a written scope
- 2
- Working days to build and test
- 5–10
Got it, thank you.
Check your inbox for a confirmation. We will reply within 2 working days with what we would do and what it would cost.
Why outbound teams run Orum alongside lemlist
lemlist sends the email. Orum is how the same list gets called: it dials several prospects at once and uses answer detection to tell a person from a screener, a voicemail and a phone tree, so a rep only hears a live answer. Both do their job well, and neither can see the other. Reps work a dialer queue built from yesterday’s CSV while the sequence keeps emailing, and nobody can say which touch produced the meeting.
Connecting them turns the call into a step in the sequence rather than a separate motion. Leads flow into Orum when they reach that step, the conversation is logged on the lead in lemlist, and the sequence reacts to what happened — a booked meeting stops the emails, a no answer leaves them running.
- Agencies running email and calls on one listThe same prospect is not emailed and dialed by two people who cannot see each other.
- SDR teams with a daily call blockCall lists are built from the sequence instead of exported by hand every morning.
- Teams that report on touchesCalls and emails sit on one lead, so a booked meeting can be traced to what caused it.
What we connect between Orum and lemlist
A typical setup. We adjust each line to how your team uses Orum and lemlist.
When this happensThis is what you get
A lead reaches the call step in lemlistAdded to the Orum list for the rep who owns it
A call connects to a live personA call activity on the lemlist lead, with the rep and the outcome
The call outcomeThe lead status you choose, such as interested or not interested
A conversation that books a meetingThe sequence stops for that lead, and your team is notified
No answer, voicemail or a phone treeLogged on the lead as an attempt, with the sequence left running
A number Orum never reachesFlagged on the lead, so the list can be cleaned rather than redialed
Field mapping, event by event
Each Orum event and exactly what it writes in lemlist. Pick an event to see its fields.
1. Trigger · Orum
When a call ends
Every call made or received in Orum
2. Action · lemlist
Log the lead update
In lemlist, on the lead — Where your team already works
lemlist field
Mapped from
What happens
Activity date
Call time15 Sep, 4:00 pm
Shown in your time zone
Call time15 Sep, 4:00 pm
Shown in your time zone
Call length
Call length3 min 04 s
Stored the way lemlist expects
Call length3 min 04 s
Stored the way lemlist expects
Call outcome
Call outcomeInterested
Matched to your own list of outcomes
Call outcomeInterested
Matched to your own list of outcomes
Recording
Call recordingPlayable audio
Added once the file is ready
Call recordingPlayable audio
Added once the file is ready
Call notes
Call notesAsked for pricing
Saved as note text
Call notesAsked for pricing
Saved as note text
Owner
Rep nameMaria Lopez
Matched to the same person in lemlist
Rep nameMaria Lopez
Matched to the same person in lemlist
Lead
Matched by phone number+1 415 555 0142
A new lead is created only if none match
1. Trigger · Orum
When an outcome is set
A rep marks how the call went
2. Action · lemlist
Update the lead status
In lemlist — Moves one record, not all of them
lemlist field
Mapped from
What happens
Which lead status
Most recent open lead statusNorthwind — 12 seats
On the matching lead, owned by the rep on the call
Stage
Call outcomeInterested
Looked up in the outcome-to-stage list we agree with you
Call outcomeInterested
Looked up in the outcome-to-stage list we agree with you
1. Trigger · Orum
When a voicemail is left
Nobody picked up in time
2. Action · lemlist
Create a follow-up
In lemlist, for the lead owner — A call-back nobody forgets
lemlist field
Mapped from
What happens
Title
Caller number+1 415 555 0142
“Call back” plus the lead name, or the number if unknown
Caller number+1 415 555 0142
“Call back” plus the lead name, or the number if unknown
Due
Your follow-up windowWithin 1 hour
Set to how fast your team calls back
Assigned to
Lead ownerMaria Lopez
Falls back to the rep who was on the line
Lead ownerMaria Lopez
Falls back to the rep who was on the line
Sample values are made up. The exact fields are agreed with you in your scope.
A one-time setup, not a monthly middleware bill
We are not a middleware. We plan the connection, set it up, test it on your calls and hand it over.
Web Repay integration setup
Middleware subscription
What you pay
One-time setup, from $100 (one-off)
A monthly plan, often priced by tasks or operations
As call volume grows
The same price, no per-task charges
Costs rise with every call that syncs
Who builds and tests it
We do, on your own Orum calls
Your team builds and maintains every step
Where it runs
In your own Orum and lemlist accounts, documented
Inside the middleware vendor’s platform
When something changes
Additional support as needed, when you request it
Your team fixes the broken steps
Where a small connector layer is the most reliable route, we say so in your written scope, set it up in your own account and choose the option with the lowest running cost.
Where Orum and lemlist setups usually go wrong
Sequences that keep sending
Someone who has just spoken to a rep should not get tomorrow’s cold email. Outcomes that mean stop, stop the sequence, and we test that before go-live.
A voicemail is not a conversation
Orum’s detection separates a person from a screener, a voicemail and a phone tree. Only a real conversation changes the lead status; everything else is logged as an attempt.
The two-second rule
On telemarketing calls, a live answer not connected to a rep within two seconds counts as abandoned. We keep the connection clean and log every attempt; the dial settings themselves stay with you and your counsel.
How we set it up
- 1
Agree what connects
Which campaigns feed the dialer, which step triggers a call, and what each outcome changes in lemlist. You get a written scope with a fixed one-time price.
- 2
Access for the setup
Team access to lemlist and admin access to Orum. Nothing for your reps to install.
- 3
We connect and test
We push test leads through the call step, take the calls ourselves and check every status, note and stopped sequence.
- 4
Handover
A short document of what is connected. It runs in your own accounts, with no monthly fee from us.
Test call passedEvery field in the table checked
LiveWatched for the first week
What it costs
From
$100 one-time setup
Starting price for connecting Orum and lemlist, built and tested. Larger mappings get a fixed quote in writing before we start.
No monthly fee from us. Additional support is available as needed, whenever you request it.
Free download
The integration health check
10 checks to make sure your website, CRM and dialer really are passing information between them.
From the blog
Further reading
Integrations
How to log every call from your dialer in your CRM
Every call on the right contact, with the outcome, the rep and the recording, and nobody typing notes afterwards. What to connect, how to match callers, and what to test.
CRM
Why your CRM is full of duplicates, and how to stop new ones
Duplicates come in through forms, imports, integrations and manual entry. Here is how to clean up what is there, and close the doors so they do not come back.
Dialers
Why fewer people answer your calls: spam labels and caller ID
When answer rates drop, the cause is often a warning label on your caller ID. How US carriers check and label calls, and what you can do about it.
Questions about Orum and lemlist
Can Orum dial leads straight from a lemlist campaign?
Yes. When a lead reaches the call step in the sequence, it is added to the right rep’s Orum list, so nobody exports a spreadsheet every morning.
Does the lemlist sequence stop after a call?
When the outcome says it should. A booked meeting or a clear no stops the sequence for that lead; a no answer leaves it running.
Do voicemails and phone trees update the lead?
No. Orum’s answer detection tells a real person from a voicemail, a screener or a phone tree, and only a conversation changes the lead status. The rest are logged as attempts.
Is there a monthly fee?
No. You pay once for the setup. Unlike Zapier, Make and similar middleware subscriptions, there is no monthly or per-task charge from us. Your lemlist and Orum plans are unchanged.
Rather talk it through?
Thirty minutes on how your team uses Orum and lemlist. You leave knowing what we would build and what it would cost.
Call ended03:04 · inbound
Lead status updatedMeeting booked
Call-back taskAssigned to the contact owner