When an SMS lead comes in warm, who owns the follow-up speed problem, the vendor or you?

The vendor is right that the service worked by the terms of the contract. The investor is right that the outcome was a failure. Both things are true because the contract measured the wrong thing.

A "warm lead" in this context means a seller who responded to an outbound text and indicated some willingness to talk. That response has a short shelf life. Research on inbound sales contact consistently shows conversion drops sharply after the first hour, and in a competitive market where multiple buyers are prospecting the same lists, the drop can be that fast.

The core problem here is that the service agreement defined delivery as the response, full stop. The vendor hit that mark. Nothing in the agreement created any obligation around what happened next, and so nobody on the investor side owned the job of being first to call. Four sellers found another buyer in that window.

A few things worth building into any agreement before the next campaign:

The definition of a "qualified lead" should include a response-time commitment on your end, written as a number of hours, not a vague intention. If your team cannot staff that window, that belongs in the conversation with the vendor before you sign.

The fee structure matters here. Paying per response means the vendor's incentive ends at the response. Paying per appointment, or even per contract, moves some of that incentive forward, though vendors with good contact rates will price accordingly.

The handoff itself needs an owner by name on your team. A three-person operation with no written handoff protocol is the internal version of the same problem.

I am not certain how different state laws treat response-time disclosures in lead-gen agreements, so a contracts attorney would be worth a short call before you redline anything.

What does your current team structure look like for inbound follow-up? That changes what a realistic response-time commitment actually is.

The vendor is right on the technical definition and wrong on the economics. Response rate is the deliverable the contract names. Conversion is the thing the investor actually bought the service to produce. That gap is the deal.

The assumption doing the most work here is that "motivated" is a stable state. It is not. A seller who texts back at 9am on a Tuesday is in a window, and that window compresses fast when they have also responded to three other outbound sequences from competing buyers. Nineteen to thirty-one hours is not a slow response, it is a different conversation with a different buyer.

The risk this thread does not name: even if you fix the internal handoff tomorrow, the fee structure you described still rewards the vendor for volume over quality. A vendor paid on contact rate has no economic reason to stagger sends, throttle volume to what your team can actually work, or flag which responses carry the most intent signals. They benefit from flooding your pipeline. You benefit from a pipeline you can actually close. Those are not the same thing.

Two structural places to apply pressure. First, the service agreement needs an SLA tied to notification latency, specifically how fast the lead reaches a live person on your end, not just how fast the vendor flags it. Second, the fee structure itself. Paying per response when your team has a capacity ceiling is a mismatch. A per-appointment or per-contract model aligns incentive differently, though vendors who actually convert will price that premium in, and you need to confirm what terms your vendor will actually sign.

A licensed contract attorney should review the service agreement before you try to renegotiate the performance language, particularly around definitions of "motivated" and any limitation-of-liability clauses the vendor is likely carrying.

What is the current definition of "motivated" in your vendor contract, and does it include any minimum qualification criteria before the lead is handed to you?