When a client hands a calling shop a badly sourced list, who should own the fallout
Take a cold calling shop that receives a 9,000 record list from a client, runs it through scrubbing, and finds roughly 6 percent flagged against do-not-call registries, while the client insists the data provider already certified it clean. Re-scrubbing at the vendor's own cost and dropping flagged records is the safer operational call regardless of whose fault the bad data was, even though it delays the campaign and frustrates the client. This exposes a real gap in most calling vendor contracts, and there are three common positions in this business. One, the vendor scrubs every time with no exceptions and eats the cost, treating it as a fixed cost of doing business priced into the rate, on the logic that the vendor's callers are the ones actually dialing. Two, it's the client's list, the client's brand on the call, and the client's chosen data provider, so the client carries responsibility and the vendor dials what it's given after a written warranty that the list is clean. Three, it's negotiated per contract, with cost and responsibility named in a specific clause before the first dial. Compliance obligations here depend on federal and state rules that differ and keep changing, and the actual allocation of legal exposure between an investor and a calling vendor is a question for a lawyer who has read the specific agreement, not a general answer. Commercially, the shops that hold up well over time tend to gravitate toward option three, a named clause up front, since it avoids exactly the kind of dispute a badly sourced list creates after the fact.
Client hands the calling vendor a list that turns out badly sourced. Commercially, who carries it?
11 votes