Yes, “court-smile” is one of the warm-up keywords you can filter for.
2.
The email addresses aren’t random. They’re warm-up or active inboxes used for warm-up traffic, so the messages go between real mailboxes for deliverability purposes. They’re not your leads/prospects.
Right now, the lookup is the only way to do this. Even if the names are already separated as a list in the previous table, there isn’t a direct way to reference them across tables without using a lookup.
Clay itself does not send emails. When inbox warm-up is enabled inside a campaign, the sending provider automatically sends and receives warm-up emails to build sender reputation. These emails are generated by the provider, not by Clay and not by you manually.
What that means in practice:
You may see emails sent from your inbox that you didn’t explicitly trigger.
Those emails are not part of your campaign steps.
They are not sent to your leads or prospects.
They’re only used to warm up the inbox and improve deliverability.
So yes, the email you saw was very likely a warm-up email, not a campaign email and not something you manually sent.
If you want full control, you can disable inbox warm-up for that inbox in the sending settings, and no automated warm-up emails will go out.
It looks like the table was deleted, so I can’t see it anymore.
If your goal is to use Send Table Data to map values coming from a comma-separated field, you can handle it with a regex.
Use this regex to split the comma-separated values into a list:
[^,"]+"?[^,"]+
1.
Extract values from Data > Add the right column with the forward slash
2.
Custom Method > Regex
3.
Add this Regex [^,"]+"?[^,"]+
That will turn the field into a list object. From there, Send Table Data can fan those values out into a new table, creating one row per value, each tied to its individual owner.
Sorry about the frustration here. I want to clear up the context so we’re aligned.
I’m able to access the workbook you shared, so it’s not currently down or inaccessible on our side. We did have a separate bug earlier this week that affected multiple users
That said, the behavior you’re describing still happen when switching between multiple accounts. Using multiple accounts is what can cause access and state issues like this.
If you’d like, I can double-check anything specific in that workbook or confirm whether there’s anything else at risk right now.
Hey - Thanks for this! We're always looking to make the product better and thisfeedbackis super helpful for us. We're going to pass this over to our product team so they can better evaluate things and see if/where this might fit into the roadmap as a future improvement.
