AI helps a Salesforce marketing team most with first drafts and pattern-spotting: copy variants, subject lines, audiences described in plain English, send-time and engagement predictions, campaign briefs and performance summaries. It helps least where every claim in the copy must be exact, where consent records are unreliable, or where nobody owns the final read. Treat each output as a draft. Start with one use case you can test against a control group, and have a named person approve everything before it sends.
Which marketing jobs is AI actually good at?
The strongest uses turn a blank page into a reviewable draft, or turn a pile of engagement data into a ranked suggestion. The weakest are the ones where a confident mistake reaches thousands of inboxes before anyone notices.
Here is how the common candidates compare. Product names are left out on purpose. The same job may live in a different Salesforce feature depending on your marketing product and edition.
| Use case | Data it needs | Human check before use | How to measure it |
|---|---|---|---|
| Email and landing page copy drafts | Brand voice guidance, approved product claims, the offer and audience | Marketer edits; legal or compliance reads anything with claims | Edit effort per draft, production time, errors caught in review |
| Subject line variants | Past subject lines with open and click results | Marketer shortlists variants and removes misleading ones | Split test against a human-written control |
| Segments from a plain-language prompt | Unified profiles, consent status, engagement and purchase fields | Ops checks the generated filter logic and audience count | Agreement with a hand-built segment; unsubscribe and complaint rates |
| Send-time and engagement scoring | Enough history of sends, opens and clicks per contact | Ops confirms exclusions and frequency caps still apply | Holdout group sent at your standard time |
| Content and campaign summaries | Campaign results, asset text, connected campaign data | Owner checks figures against the source report | Time saved preparing reviews; corrections needed |
| Campaign brief generation | Goals, audience, budget owner, past campaign results | Campaign owner rewrites objectives and success measures | Briefs accepted with light edits versus rewritten |
| Lead qualification agents | Fit and engagement data, agreed qualification rules | Sales and marketing review handoffs and disqualifications | Randomized comparison with the existing process |
| Analytics questions in plain English | Clean campaign, lead source and opportunity links | Analyst spot-checks answers against saved reports | Share of answers that match the governed report |
Lead qualification sits at the border with sales, and it deserves its own design work. Our guide to AI lead qualification covers that handoff, so here we stay with the marketing side.
What does Salesforce offer marketers today?
Each Salesforce marketing product has its own set of AI features, and the newest ones run on Agentforce and Data 360. Names, editions and usage limits change often, so treat the list below as a starting point for a conversation with your account team.
In Account Engagement, formerly Pardot, Salesforce documents Einstein features for content creation, behavior scoring, campaign insights and send time optimization. The content features draft forms, landing pages, subject lines and email copy inside the editor. Help documentation ties them to the Advanced and Premium editions, so check which edition your contract carries.
Marketing Cloud Engagement, the B2C platform, has a longer list of predictive features. Einstein Engagement Scoring predicts how likely each contact is to open or click. Einstein Send Time Optimization picks a send time per contact from engagement history, and Einstein Engagement Frequency suggests how many messages a contact should receive. For generative work, Salesforce documents subject line and body copy generation in Content Builder, with Einstein Copy Insights for testing and comparing drafts. Brand personalities shape the tone, and Salesforce's help pages describe a generation cap per account.
Marketing Cloud Next is the newer platform, built on Data 360 and Agentforce. Salesforce describes Agentforce campaign creation from a single prompt: a brief with objectives and success measures, an audience segment, email and SMS copy, a journey in Flow and a performance summary afterwards. Salesforce says Account Engagement customers can use these capabilities alongside their existing setup, while Engagement customers reach them through a renewed edition. At Dreamforce 2026 Salesforce added Campaign Agent, which assembles audiences, content and channels against a goal you set and adjusts the campaign after launch; Salesforce says it becomes generally available in Marketing Cloud Next Advanced by October 2026, with extra campaigns and content generations at additional cost. Keep the same named approver and holdout for anything it launches. Confirm what your contract includes, and whether consumption credits apply, before you plan around any of it.
What data has to be in place first?
Consent you can trust, one profile per person, and enough engagement history for the models to learn from. Without those, AI simply speeds up the mistakes your current setup already makes.
Consent comes first because AI widens reach. A segment generated from a prompt can pull in contacts a careful marketer would have excluded by habit. Check the basics before any AI touches audience selection:
- Opt-out and unsubscribe status syncs both ways between your marketing product and Sales Cloud, with one field that wins.
- Consent is stored per channel and purpose, so email permission is not mistaken for SMS permission.
- Suppression lists for competitors, customers in dispute and regional restrictions are applied at send, not only in saved segments.
- Every record shows its consent source and capture date, so you can answer a regulator or a complaint.
- Duplicate people are merged, or one person may receive the same campaign twice under different scores.
Unified profiles matter most for segment building and personalization. If web behavior, purchases and service history sit in separate systems, a natural-language segment can only see part of the picture. That is the job Data 360 does, and our Data Cloud use cases guide explains when it is worth adding. Our data privacy guide covers consent objects and deletion requests in more detail.
Predictive scores need volume. A small list with a few sends per quarter gives send-time and engagement models little to learn from. Salesforce documents minimum data requirements for several features. Check them before promising results to leadership.
How do you keep AI copy on brand and approved?
Give the model written guardrails, and put a human approval step between every draft and every send. Brand settings shape tone; only a reviewer can confirm the facts.
Start by writing down what the model should know. A short brand voice guide, approved product claims with sources, banned phrases and required disclaimers will improve drafts more than prompt tinkering. Load the guide into whatever brand settings your tool offers, and keep the master copy where your team can update it.
The biggest risk in marketing copy is a confident, specific claim that is not true. Watch for invented statistics, features your product does not have, prices or offer terms that differ from the real offer, and testimonials nobody gave. Models produce these because they read as persuasive, not because anything in your data supports them.
Build the review into the tools you already use rather than a side channel. An approval step on the email asset or campaign record, with a named approver per content type, leaves an audit trail. Our AI governance guide explains how to set review levels by risk, and the same thinking applies here: a subject line test needs a lighter check than a rate disclosure.
Regulated industries need a firmer gate. Financial services firms have rules on communications with the public, and healthcare marketers must keep protected health information out of prompts and copy. In both cases, the compliance team should approve the use case before launch and sample sent messages afterwards. AI drafting does not change who is accountable for what was sent.
How do you know whether it worked?
Compare AI-assisted sends with a control group on the outcomes you already report, and record what reviewers had to fix. Vendor benchmarks and anecdotes are not evidence for your list.
Marketing has an advantage here, because split testing is already a habit. Run AI-written subject lines against a human-written control in the same send. Hold back a random slice of contacts from send-time optimization and mail them at your usual time. Compare opens and clicks, but also pipeline created, unsubscribes and spam complaints, because a clickbait subject line can win opens and lose trust.
Measure the production side too. Track how long a campaign takes from brief to approved send, how many review rounds each asset needs, and what reviewers changed. If drafts arrive faster but take longer to fix, the time has only moved to a different desk. Keep the comparison running long enough to cover several sends, and note the model, prompt and settings used so results can be traced later.
Can you use Claude or another outside model with your marketing data?
Yes, but decide where each job runs and what data leaves Salesforce. Work inside Agentforce gets Salesforce's trust controls; work in an outside assistant follows that vendor's terms and your own configuration.
Agentforce can use Claude models, so picking Claude does not mean leaving Salesforce's AI. Separately, marketers can use Claude directly for research, brief drafts and analysis, connected to Salesforce data through approved integrations. That direct route suits thinking work, such as testing message angles or summarizing win-loss notes before a campaign. It suits bulk sending poorly, because copy should still pass through your marketing product's approval and consent checks. Our Claude and Salesforce guide compares the connection paths.
Whichever model you use, keep personal data out of prompts unless the use case needs it and your agreements allow it. Give any integration user only the objects and fields its job requires.
What should a first phase include?
One use case, one channel, one owner and a written test plan. Expand only after the results and the review notes support it.
- Pick a low-risk job, such as subject line variants or campaign summaries, rather than autonomous sends.
- List the AI features your edition already includes, and confirm credits or limits with your account team.
- Fix the data that use case reads: consent fields, duplicates and engagement history.
- Write the brand guide, approved claims list and approval rules before the first draft.
- Define the control group and the measures, including unsubscribes and complaints.
- Review results with marketing, sales and compliance before adding a second use case.
If you want help scoping that first phase, our team can review your marketing setup alongside your Salesforce data and AI options.
