What LeadRefinery is

LeadRefinery calls a broker's inactive leads, at a controlled rate and within the law. An AI agent holds each conversation. The platform writes each outcome into one permanent record. A person receives each live transfer.

The whole process in six steps

Our clients are commercial-finance brokers. Each broker has a list of merchants who asked about capital in the past and then stopped contact. These steps occur for such a list, in this order:

LeadRefinery imports the list. It rejects each faulty row and gives the reason.
Each lead gets up to fifteen calls, spread across weeks in a calling programme — quick and concentrated, or gentle and distributed.
An AI voice agent holds each conversation. It calls from the client's own phone numbers.
A call starts only after it passes the fifteen safety checks.
When a merchant shows interest, a person takes over. The three paths are an immediate transfer of the live call, a callback, or an emailed application link.
The platform writes each outcome into the record exactly once.

A specialist provider holds the conversation itself: it listens, speaks, and takes turns. This platform does the work around the conversation:

It continues each lead's calling programme after a crash or a restart.
It checks compliance at the moment of each dial.
It controls the rate of the calls.
It keeps each client's data separate from the data of all other clients.

The diagram shows eight numbered steps from an uploaded list to a transfer to the client's team. The steps are: the uploaded list, the daily queue, each lead's multi-week journey, the fifteen safety checks, the AI call, the permanent record, the transfer to a person, and the control room. Two notes sit below the steps: the platform keeps each client's data and numbers separate, and a rehearsal mode runs the full sequence with no real call. — This diagram shows the whole platform. Follow the numbered steps from an uploaded list to a transfer to a person. Then note the two functions below the steps. The **separation between clients** applies to each step. The **rehearsal mode** runs the full sequence with no real call.

Three ways to read this site

New readers: start with the six specialists behind every call. Then read one call from start to finish. Then read one lead's calling journey.
Compliance reviewers: read the seventeen checks before each dial. Then read phone numbers and caller identity. Then read the separation between clients.
Platform operators: start with importing your leads. Then read running a campaign and the control room. Then read rehearsals with no real calls.

Every page on this site

The people and the machine

The six specialists behind every call — the job of each system, and the reason the jobs are separate.
Why these technologies — each product named on this site, and the reason the platform uses it.
Many clients, one platform — the database itself enforces the separation of each client's data.
How a new client joins the platform — the signed agreement, the five setup steps, and how the signed copy is kept and opened.
How the platform keeps client data separate and safe — the database's own rules, request checks, and signed webhook messages.
Where a lead's details travel — one phone number, followed from an upload to the screen, through every check on the way.
The control room — the screens that a client's team uses to follow results, and the screens that LeadRefinery staff use to run campaigns.

The calls

How a call happens — one call attempt, from the safety checks to the recorded outcome.
What the agent can do mid-call — the nine actions, which include a callback booking, a do-not-call entry, and a transfer to a specialist.
The seventeen checks before each dial — automatic checks enforce compliance before each dial.
Phone numbers and caller identity — each phone number has a reputation and a managed life cycle.
Who decides a call is spam — the far network makes that decision, and the score follows the business, not the number.
How the platform keeps its numbers trusted — what the platform does today, what a person does by hand, and what it proposes next.
How the platform brings a new number into service — a new number's score rises from answered calls, not from calling more.
How the platform rotates its numbers — the five states of a number, the triggers that move it, and how one call claims a number.

The programme

Getting your leads into the system — five stages, and a reason for each rejected row.
A lead's calling journey — up to fifteen calls, in one of two calling styles, and exits that apply immediately.
Running a calling campaign — a release plan solved once against the day's real capacity, and the controls that stop calls immediately.

Trust, tested

Tests that make no real calls — a simulated phone network, and simulated campaign time.
How the platform proves the agent's quality — a test with thirty-three callers, one rule that permits zero failures, and an audit of each running campaign every 15 minutes that reviews each answered call.
What a call costs, and what controls the cost — billing for each second, the machine calls that carry most of the cost, and a daily ceiling the platform now enforces for each client.
Billing each client — the three Telnyx objects every client owns, why the minutes and the rent land on one invoice line, and what the platform sets up by itself.
What a lead costs — a lead is twelve to fifteen calls, most of them to a machine; the measured rates and the sums for 10,000, 50,000 and 100,000 leads.
The machines that run it — the hosts the platform runs on, what each one does, and what each one costs.
Shipping a change — how a new release is rehearsed and approved before it ever reaches a real client.
Getting back after a loss — what happens if a server or the data is lost, the two copies kept away from the running machines, and the road back.

What changes next

What changed to reach today's engine — the rebuild that replaced a fixed twelve-call, three-wave pattern with the fifteen-call, two-calling-style engine this site now describes, and what is still being finished.
The settings that decide how a campaign calls — the named calling styles behind every campaign, and three things a setting can never do.

The technical bit, translated

These are the six main products:

Retell holds the live voice conversation: speech recognition, speech generation, and turn-taking. Thus the platform does not have to process real-time audio itself.
NestJS is the decision desk. It answers in milliseconds while a caller speaks.
Temporal keeps the state of each long task and continues the task after a crash. Thus a lead's multi-week calling programme continues after a failure. Temporal runs in a separate worker program, and no call starts without it.
PostgreSQL is the single system of record. Its own security rules enforce the separation between clients.
Telnyx supplies each client's phone numbers. It signs each call cryptographically as proof that the call is genuine.
An evaluation toolkit grades the agent before a change reaches live callers. The toolkit includes Coval, a service that calls the agent with scripted personas.