Discrepancy in Email Credits Used: Request for Investigation

Eugene A. · 2025-10-19 16:36:00.285956+00

Hello, kindly assist. I run this table of about 1800 find email rows using a waterfall that was projected to cost 3 credits per row even though I have some API connected providers. The waterfall then used up 20,000+ credits. Kindly look into this. Here is the table URL: https://app.clay.com/workspaces/364283/workbooks/wb_0t1el7qqXvPzwdwX3od/tables/t_0t1d0ehcdApzFbGFYAu/views/gv_0t1d0eh8CdRC899vYjN

Discrepancy in Email Credits Used: Request for Investigation | Clay

13 comments

· Sorted by Oldest

Clay Support
APP
·
·
Multiple providers in your waterfall ran because emails found were invalid, causing the next provider to trigger. Waterfalls continue until a valid email is found or all providers are exhausted. [1]
Each Clay-managed Hunter.io attempt costs 2 credits per enriched cell regardless of success. Credits are only refunded when no email is found, not when invalid emails are returned. [2]
With 1800 rows and multiple providers running per row due to validation failures, your 20,000+ credit usage aligns with this waterfall behavior.
If you need further help reviewing your specific table configuration, please request human assistance by clicking on "Talk to a person."
Clay Support
APP
·
·
Was that helpful?
Eugene A.
·
·
Talk to a person, there's no way that waterfall used 20,000 credits
Clay Support
APP
·
·
I understand your concern and will connect you to a human agent who can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Eugene A.
·
·
It used 22,523 credits to be exact, that's way too much. We'd like a refund asap please. Here's the URL: https://app.clay.com/workspaces/364283/workbooks/wb_0t1el7qqXvPzwdwX3od/tables/t_0t1d0ehcdApzFbGFYAu/views/gv_0t1d0eh8CdRC899vYjN
Eugene A.
·
·
Clay S. can I get some help here please
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!
Eugene A.
·
·
Clay S. there's been no support
Amit K.
·
·
Hey Eugene- just want to confirm, is this the table you are referring to? I'm checking into your workspaces now, and you aren't part of the Fuze workspace. https://app.clay.com/workspaces/364283/workbooks/wb_0t1el7qqXvPzwdwX3od/tables/t_0t1d0ehcdApzFbGFYAu/views/gv_0t1d0eh8CdRC899vYjN
Eugene A.
·
·
Hello Amit K., yes that's the table. I'm in the workspace via my work email: eugene@thisisfuze.com
Sayli G.
·
·
Hello Eugene! Thanks for reaching out! I took a look at your credit spend and you spent about 23k in your work email waterfall. If you go to this icon in the bottom right it gives you the credit spend over the last run:
When it comes to expected spend for a waterfall, it will always be an average of how much the data providers cost per row. You'll also have scenarios where you're charged even when an email is found but marked as invalid by the validation provider. This happens because we still spend credits to find the email through the initial data provider, and the validation provider is a separate service that only checks the email after it's been returned—they don't have access to the original provider's databases to pre-filter invalid emails.
You also have about 14 data providers with varying credit costs. Therefore it does add up that you would use about 23k credits in this waterfall. In many rows I can see multiple data providers have found emails but they were deemed invalid by the validation provider. Let me know if this makes sense. I would recommend reducing the number of data providers in your waterfall for next time.
Loading attachments
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
Multiple providers in your waterfall ran because emails found were invalid, causing the next provider to trigger. Waterfalls continue until a valid email is found or all providers are exhausted. [1]
Each Clay-managed Hunter.io attempt costs 2 credits per enriched cell regardless of success. Credits are only refunded when no email is found, not when invalid emails are returned. [2]
With 1800 rows and multiple providers running per row due to validation failures, your 20,000+ credit usage aligns with this waterfall behavior.
If you need further help reviewing your specific table configuration, please request human assistance by clicking on "Talk to a person."
Clay Support
APP
·
·
Was that helpful?
Eugene A.
·
·
Talk to a person, there's no way that waterfall used 20,000 credits
Clay Support
APP
·
·
I understand your concern and will connect you to a human agent who can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Eugene A.
·
·
It used 22,523 credits to be exact, that's way too much. We'd like a refund asap please. Here's the URL: https://app.clay.com/workspaces/364283/workbooks/wb_0t1el7qqXvPzwdwX3od/tables/t_0t1d0ehcdApzFbGFYAu/views/gv_0t1d0eh8CdRC899vYjN
Eugene A.
·
·
Clay S. can I get some help here please
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!
Eugene A.
·
·
Clay S. there's been no support
Amit K.
·
·
Hey Eugene- just want to confirm, is this the table you are referring to? I'm checking into your workspaces now, and you aren't part of the Fuze workspace. https://app.clay.com/workspaces/364283/workbooks/wb_0t1el7qqXvPzwdwX3od/tables/t_0t1d0ehcdApzFbGFYAu/views/gv_0t1d0eh8CdRC899vYjN
Eugene A.
·
·
Hello Amit K., yes that's the table. I'm in the workspace via my work email: eugene@thisisfuze.com
Sayli G.
·
·
Hello Eugene! Thanks for reaching out! I took a look at your credit spend and you spent about 23k in your work email waterfall. If you go to this icon in the bottom right it gives you the credit spend over the last run:
When it comes to expected spend for a waterfall, it will always be an average of how much the data providers cost per row. You'll also have scenarios where you're charged even when an email is found but marked as invalid by the validation provider. This happens because we still spend credits to find the email through the initial data provider, and the validation provider is a separate service that only checks the email after it's been returned—they don't have access to the original provider's databases to pre-filter invalid emails.
You also have about 14 data providers with varying credit costs. Therefore it does add up that you would use about 23k credits in this waterfall. In many rows I can see multiple data providers have found emails but they were deemed invalid by the validation provider. Let me know if this makes sense. I would recommend reducing the number of data providers in your waterfall for next time.
Loading attachments
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!