Pontus, literally no provider is able to distinguish between private and corporate mobile numbers. Compliance element should be stitched into your internal process and the way your team communicates with prospects. If you are concerned about the legal aspect of a specific provider, you can trace the origin in Clay. Please keep in mind that Clay is not a data provider - it’s an aggregate of various data sources, hence the onus of compliant data acquisition lies directly with the source.
Upset… understand it’s unpleasant for both parties, but “upset” doesn’t mean what your team is doing is against the law. Developing a diplomatic script to fall back on for your team helps a great deal. I’ve lead global SDR teams and we had this come up daily across various regions.
For Clay partnership team: I’m sure you do this already, but just in case - upon signing a data provider, perhaps enquire about what is their GDPR compliance opt out policy. Maybe even stitch the unsubscribe link directly into the waterfall. This way if someone is disgruntled, the Clay customer’s rep can offer them the opt out link straight away. (Opt out should be done both in the internal CRM and the original data provider). Pontus Bäckman Arpit (Clay Community Cop) Stephanie Holland
.png){kind=logo}
