Mobile Phone Validation: Charge Only for Different Numbers | Clay

Mobile Phone Validation: Charge Only for Different Numbers

Find Mobile Phone feature, or you could call it, "Find Additional Numbers," where we input the phone number (possibly wrong number or the prospect doesn't want us calling their mobile number and told us to call their desk number) and only receive an output if the new phone number is different than the input. Use case: I get a wrong phone number from Wiza after an SDR calls....I send that phone property to a Clay table and input the wrong number along with the identifying criteria such as LI, Email where I select another phone provider to check. The phone provider (Forager, LeadMagic etc) checks to see if their phone number is different from the wrong number. If it is different, I am charged credits and the new/different phone number appears. If it is the same number, I am not charged credits.

5 comments

Channeled
APP
·
·
We don't have a specific feature that automatically compares phone numbers and charges credits only for different numbers. However, you can use our ClearoutPhone integration to validate phone numbers. Here's a workaround: 1. Set up a table with your input phone numbers. 2. Use the "Check Phone Line Type & Status" action from ClearoutPhone. 3. Compare the results manually or use a formula to identify differences. Note that each ClearoutPhone enrichment uses one credit, regardless of the outcome. You can't avoid being charged for identical numbers. If you need more credits, you can purchase credit top-ups at 50% more than your plan's typical cost per credit. For a more tailored solution, you may want to request human assistance by clicking on "Talk to a person".
Sources: ClearoutPhone integration overview | Documentation | Clay University ClearoutPhone integration overview | Documentation | Clay University
Daniela D.
·
·
Hey John! Thanks for sharing. This is really helpful feedback. One limitation when configuring enrichments is that we can’t view a provider’s available data fields until a successful API call is made. This is because each integration works by sending a request to the provider for a specific data point. The provider then returns a response based on whether or not that data exists. However, a comparison can't be made with a value in your table while the request is still being processed. We'll pass this over to the product team to evaluate potential workarounds. A way to get navigate this would be using a phone validator for any number found by a provider. Ex: Trestle is able to help determine if a number is associated to the right person. SureConnect is also able to verify if a number will connect. Let me know if that helps.
(17 kB)
(34 kB)
John M.
·
·
That is past the point of Sureconnect. This would be handled at the data provider level where they would have to take the input, check their data, and then decide if the number being requested = the input data or if its new data. This would save billions of Clay credits and make everyone happier.
Daniela D.
·
·
Hey John! Thanks for the reply. Totally hear you✨. We've escalated this to the product team to evaluate.
Laxman P.
·
·
John M. Lax here, founder at SureConnect. No data provider will offer a free API to check their data against another source — not now, not ever. They sell data, so giving away comparisons doesn’t align with their business model. Sure, it would save sales teams time and money, but they want to monetize every record. I’ve tried pitching a model where SureConnect flags bad numbers so providers can update or remove them without charging customers — but so far, no one’s been open to it.