Pros and cons of composing emails in clay vs. smart lead with custom field imports

Anybody know if it's better to compose your emails in clay, ready for smart lead, or compose the emails in smart lead based on custom fields being imported from clay? I assume one of the cons is that once the email copy is exported from clay to smart lead you can't change it, and may have to reupload/update leads if you want to make changes, but I'm sure there are cons to the limitations of what you can and can't do with if statements in smartlead vs inside clay (I'm already coming up against some roadblocks)

✅1

7 comments

Clay T.
APP
·
·
Hi Nick! I would create the first lines with AI and also some enrichments like finding competitors, etc... And also normalizing company names. All in Clay. Then import it to the sending tool and compose the email there, if you do this you will have more control over the Spintax as well.
Nick S.
·
·
{Hi|Hello|Hey} <-- if that was in a custom field exported from clay, I assume it would work too for the spintax functionality inside smartlead?
Nick S.
·
·
seems like smartlead doesn't support nested if statements right now (which is my issue)
Ruadhán Ó.
·
·
I'm no expert now, but pretty sure the spintax won't work if it's being imported as a variable
😰1
Ruadhán Ó.
·
·
It's based on previous emails that have been sent out, but Smartlead can't track which emails used what version within the spintax because it's individual to each email. I dunno if that makes any sense 😅
Clay T.
APP
·
·
Yes, I would do it in the sending tool
Nick S.
·
·
Makes total sense thanks
🎉1