Phone numbers written two ways
Twilio and lemlist often store numbers in different formats. Left alone, a caller who already exists becomes a second lead. We match on a cleaned-up number before anything is created.
Integration · Twilio to lemlist
lemlist and Twilio integration
We connect Twilio to lemlist so every call, outcome and follow-up lands on the right 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
Twilio
lemlist
One call ends in Twilio. In lemlist:
- Call logged on the leadLength, direction and the rep who took it
- Recording attachedLinked from the lead update
- Outcome moves the lead statusThe stage or field you choose
- 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
What we connect between Twilio and lemlist
A typical setup. We adjust each line to how your team uses Twilio and lemlist.
When this happensThis is what you get
A call endsA lead update on the matching lead, owned by the right lemlist user
The call recordingAttached to that lead update
The transcript and summaryA note on the lead
A text messageA note on the lead
A caller who is not in lemlist yetA new lead, checked against existing records first
Field mapping, event by event
Each Twilio event and exactly what it writes in lemlist. Pick an event to see its fields.
1. Trigger · Twilio
When a call ends
Every call made or received in Twilio
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
Date created15 Sep, 4:00 pm
Shown in your time zone
Date created15 Sep, 4:00 pm
Shown in your time zone
Call length
Call duration3 min 04 s
Stored the way lemlist expects
Call duration3 min 04 s
Stored the way lemlist expects
Direction
DirectionInbound
Inbound or outbound
DirectionInbound
Inbound or outbound
Recording
Recording urlPlayable audio
Added once the file is ready
Recording urlPlayable audio
Added once the file is ready
Call notes
Transcription textAsked for pricing
Saved as note text
Transcription textAsked for pricing
Saved as note text
Lead
Matched by phone number+1 415 555 0142
A new lead is created only if none match
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 Twilio calls
Your team builds and maintains every step
Where it runs
In your own Twilio 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 Twilio and lemlist setups usually go wrong
Reps matched to lemlist users
If a Twilio user is not matched to a lemlist user, calls log without an owner. We match every rep before go-live.
Updating the right lead status
An outcome has to change one lead status, not every lead status on the record. We agree the rule with you before we build.
Recordings that are not ready yet
A recording can finish processing after the call ends. We attach it once it is ready, so no call in lemlist is left without audio.
How we set it up
- 1
Tell us what should connect
Which calls, outcomes and follow-ups should reach lemlist. You get a written scope with a fixed one-time price.
- 2
Give us access
Admin access to Twilio and lemlist for the setup. Nothing for you to install, and no new subscription to start.
- 3
We build and test
We connect the two tools, map every detail and test it with real calls before your team relies on it.
- 4
Handover
You get a short document of what is connected and how it behaves. 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 Twilio 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.
Questions about Twilio and lemlist
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, so the cost does not grow as your team makes more calls.
Is Web Repay a middleware?
No. We are an integration team: we plan the connection between Twilio and lemlist, set it up, test it on your calls and hand it over. Where a small connector layer is the most reliable route, we say so in your written scope and choose the option with the lowest running cost.
What can you connect between Twilio and lemlist?
A call ends, the call recording, the transcript and summary, a text message, each mapped to the right lead and lead status in lemlist. We confirm the exact list in your scope.
How long does it take?
You get a written scope and a fixed price within 2 working days. Most setups are built and tested within 5 to 10 working days of getting access.
What do you need from us?
Admin access to Twilio and lemlist during the setup, and a short call to agree what should happen. You can remove our access once it is handed over.
Rather talk it through?
Thirty minutes on how your team uses Twilio and lemlist. You leave knowing what we would build and what it would cost.
Call ended03:04 · inbound
Lead status updatedStage set from the call outcome
Call-back taskAssigned to the contact owner