Why Agencies Should Not Send Client Outbound From Invented Sender Personas

There is a shortcut that shows up in some agency setups. The client does not want their own name on cold email, and the agency does not want its staff on it either. So someone invents a sender. "Sarah, Partnerships at [Client]." A first name, a plausible title, sometimes a stock or AI-generated headshot and a LinkedIn profile to match.

Our view is simple: don't. Send from a real person who works with or for the client and who will actually take the meeting or hand it off. Here is why, and what to do instead.

What the rules actually say

It is worth being precise, because this is not as simple as "fake names are illegal."

The FTC's CAN-SPAM guide says the "From," "To," "Reply-To," and routing information must be accurate and identify the person or business who initiated the message. The statute itself says a From line that "accurately identifies any person who initiated the message" is not materially false or misleading. In its rulemaking, the FTC added that the From line does not need a full legal name, but it has to give the recipient enough information to know who is sending the message.

So a made-up first name in front of the client's real domain may not, on its own, break CAN-SPAM. The business is still identified. Your client's lawyer can tell you where their line is.

LinkedIn is less forgiving. Its User Agreement says each member gets one account, in their real name, and that creating an account with false information violates its terms, including accounts registered on behalf of others. Its Professional Community Policies say: "Do not create a fake profile or falsify information about yourself," and "We don't allow fake profiles or entities." A persona that exists on email but not on LinkedIn falls apart the moment a prospect looks it up. A persona that does exist on LinkedIn is a policy violation waiting to be found.

Why it is a bad trade even where it is allowed

The meeting exposes it. Outbound is supposed to end with a conversation. When "Sarah" books a call and someone named Mark shows up, the first thing the prospect learns about your client is that the email was staged. That is a poor start to a sales process.

Replies have nowhere honest to go. Prospects reply to people. They ask follow-ups, mention the sender on their own team's call, look the sender up. Every one of those moments now needs a cover story, and cover stories are what make reply handling slow and inconsistent across a team.

It compounds with AI writing. If an AI writer is drafting in the voice of a person who does not exist, nobody owns what the email says. When a prospect asks a direct question, like whether the email was written by a bot, the honest answer gets harder. We wrote about answering "is this AI?" replies honestly.

It hides the account from the client. When a persona's LinkedIn seat gets restricted, or its email gets flagged, there is no real employee to verify identity or recover access. The client's outbound stalls on an account nobody can legitimately claim.

What to do instead

Pick a real sender for every client during onboarding, and write it into the workspace:

1. Name a real person. A founder, a sales lead, an AE, or a named member of the client's team who agrees to have outbound go out under their name. If nobody at the client will put their name on it, that is worth discussing before launch, because it can be a sign the client is not sure about the message either.
2. Make sure that person takes or hands off the meeting. The sender does not have to run every call, but the booking should introduce whoever does, by name, with no story to keep straight.
3. Use their real profile. On LinkedIn, the seat belongs to the actual person. Tidy the profile, don't invent one. Our LinkedIn profile checklist for client sender seats covers the basics.
4. Keep the signature true. Real name, real title, the client's business identity, and the postal address CAN-SPAM requires.
5. If an agency rep sends, say so. Some agencies send under their own staff's names, on the client's behalf. That works, as long as the email is clear about who the person is and who they represent.

Where GTM fits

GTM connects each client's real email domains and LinkedIn seats inside an isolated workspace, and writes in the client's voice from prospect evidence. Sends go through a compliance gate that requires a verdict and an unsubscribe URL before anything goes out, and LinkedIn passwords are passed to the connection vendor and never stored. The setup assumes a real sender behind every seat.

If you run outbound for several clients and want real senders, clean identities, and one workspace per client, join the waitlist.

Sources

• FTC, "CAN-SPAM Act: A Compliance Guide for Business": https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
• 15 U.S.C. § 7704, "Other protections for users of commercial electronic mail": https://uscode.house.gov/view.xhtml?req=granuleid%3AUSC-prelim-title15-section7704&num=0&edition=prelim
• FTC, "Definitions and Implementation Under the CAN-SPAM Act," 16 CFR Part 316 (2008): https://www.ftc.gov/sites/default/files/documents/federal_register_notices/definitions-and-implementation-under-can-spam-act-16-cfr-part-316/080521canspamact.pdf
• LinkedIn, "User Agreement": https://www.linkedin.com/legal/user-agreement
• LinkedIn, "Professional Community Policies": https://www.linkedin.com/legal/professional-community-policies