The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
What are your thoughts on using Co-Agent intakes?
I feel like as efficient as it is to make up for the time it takes me to reply (which is around 1-2 hours), it's also off-putting by being inauthentic. Idk, I just feel like if I were reaching out to a freelancer, I wouldn't want to be talking to an AI agent. I've lost clients because of not replying earlier and also lost them using Co-Agent... welp.
⭐I'd love to hear your take on this!
I would use the intake to collect the project basics, then make the first substantive reply personal. One specific judgment about their project would show that you read it and give them a real person to respond to.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
The email felt like it was written just for one person. It sort of was.
A subscriber replied asking how the team knew exactly what they needed the honest answer was that their own past behavior wrote the email, automatically, along with a few hundred others.
→ Personalization at scale still has to feel personal, not just automated.
Seeing the email pull directly from a subscriber's own history makes the message feel like a one on one note, even when it's part of a batch.
One quarterly number almost got double-counted across two reports.
Two dashboards were quietly tracking overlapping data. Caught before it went out now there's one source of truth the reports pull from, not two that can disagree.
→ A good number is only as good as the one place it actually comes from
Great catch before it shipped. I like the “one source of truth” framing - pulling reports from one validated source makes it much harder for a duplicate dashboard to quietly skew the number again.
One segment got the wrong product recommendation block.
A tagging mismatch sent one segment content meant for another. Caught it fast, fixed the mapping logic between segment tags and content blocks to be far stricter.
→ More personalization means more places a small mapping error can hide.
The mapping problem compounds as segmentation gets more granular. At 50 segments and 200 content blocks, no one's manually reviewing every combination. The approach that scales: treat segment-content assignments as a typed contract. Define what each content block expects —...