Best AI Use Cases for Sales in 2026

Required

Meetings

Reads the finished transcript with speakers, attendees, and timing.

Recommended

CRM

Reads accounts, contacts, and open deals to match the call.

Writes the call note and tasks, prepared for your review.

Email

Writes draft follow-up emails only - sending stays with you.

Skip the CRM and email connections and the agent still prepares everything - you just paste it in. Optional: a task manager if action items live outside your CRM, or Slack for a ping when drafts land.

Paste this into Claude, ChatGPT, or your automation tool. It interviews you, builds the workflow, and tests it before anything goes live - have a past follow-up email you were happy with, one CRM note in your usual format, and three recent call transcripts ready before you start.

Help me set up an automated meeting follow-up workflow.

After each of my customer calls, it should draft the follow-up email, the CRM
note, and the task list for my review. It must never send anything.

1. Ask me which meeting recorder, CRM, and email tool I use, and confirm they
   are connected.
2. Ask me for one past follow-up email and one CRM note to use as format
   examples.
3. Ask me about preferred length and tone, and anything that should never
   appear in a customer email.
4. Build the workflow as a reusable skill or automation that:
   - matches the external attendees to the right account and open deal;
   - extracts decisions, commitments, owners, dates, and next steps;
   - leaves owners and dates blank when the call did not name them;
   - saves the email as a draft and prepares the CRM note and tasks.
5. If one of my tools is not connected, give me paste-ready output for it
   instead.
6. Test the workflow on my last three calls and show me the results.
7. Give the workflow a clear name so I can find and edit it later.

What good looks like

Across the three test calls the email should need light edits at most, the note should land on the right account, and no owner or date should appear that was not said on the call. If it misses, tell it exactly what went wrong - too long, wrong tone, invented a date - and rerun the same three calls.

Choose your trigger

Trigger it on each new completed transcript if your recorder supports that event; otherwise check every 15–30 minutes. Restrict it to calls with at least one external attendee, or your standups and interviews start producing customer follow-up drafts too. If your recorder cannot filter by attendee, filter by calendar title and exclude anything marked internal.

What runs without you

Review every draft for the first five calls. Once four of five are sendable with light edits, let the CRM note and tasks write automatically and keep reviewing the emails. The customer email stays a draft permanently - that is not a phase you graduate from. Once a week, compare drafts created to calls held; a stopped automation does not announce itself.

Pairs well with automate pipeline hygiene and generate call coaching briefs - both reuse the transcripts you just connected.

Required

CRM

Reads leads, contacts, and lifecycle stage to pick who qualifies.

Writes the outreach activity, logged on the contact.

Recommended

Research

Reads role, company, and recent buying signals for the angle.

Email

Writes draft outreach emails only - sending stays with you.

No enrichment tool? The agent researches from the public web instead - slower and shallower, but enough to test whether the drafts earn replies. Optional: a docs workspace holding your approved positioning and proof points.

Paste this into Claude, ChatGPT, or your automation tool. It interviews you, builds the workflow, and tests it before anything goes live - have two or three approved messages that show your tone, and a list of ten accounts you know well ready before you start.

Help me set up a personalized outreach drafting workflow.

When a lead qualifies or a buying signal appears, it should research the
person and draft one concise, grounded email for my review. It must never
send anything.

1. Ask me who the audience is, which signals justify reaching out, and what
   my daily draft limit should be.
2. Ask me which claims and value propositions I am allowed to use, and for
   two or three approved emails that show my tone and structure.
3. Ask me about preferred length and anything that should never appear in a
   customer email.
4. Build the workflow as a reusable skill or automation that confirms the
   person's role and company, finds one concrete reason to reach out,
   connects it to one approved value proposition, and drafts a short subject
   line and email with a simple next step.
5. Save every message as a draft with the sources used to personalize it, and
   log the activity in my CRM. No invented facts, no fake familiarity.
6. Test it on three prospects I know well and show me the drafts.
7. Give the workflow a clear name so I can find and edit it later.

What good looks like

Every company fact should be verifiable, the reason for reaching out should be specific to that account, and the claim should be one you approved. If a draft could have been sent to anyone, tell it so and rerun the same three prospects.

Choose your trigger

Trigger it when a lead meets your qualification rule, or run a capped daily batch over a saved CRM segment. Cap it - an uncapped outreach workflow is how you end up with a hundred drafts and no time to review them. Exclude existing customers and anyone already in an active conversation.

What runs without you

Review every draft for the first two weeks. Once the research is consistently right, let it log the CRM activity automatically and keep reviewing the messages. Sending always stays with you - outreach is where a wrong fact costs you the account. Once a week, check that drafts are still appearing for qualified leads.

Pairs well with prioritize accounts automatically - same CRM and research connections, and it tells you who to write to.

Required

CRM

Reads the deal, products, amounts, and discovery context.

Writes the proposal link and status back on the deal.

Recommended

Docs

Reads your template, approved product language, and proof points.

Writes the proposal first draft.

No connections? Upload the transcript, template, and approved content by hand - same draft quality, manual trigger. Optional: your meeting assistant for discovery transcripts, or file storage for prior proposals.

Paste this into Claude, ChatGPT, or your automation tool. It interviews you, builds the workflow, and tests it before anything goes live - have your current proposal template, your approved product language and proof points, and two past proposals you were happy with ready before you start.

Help me set up an automated proposal drafting workflow.

When a proposal is requested, it should turn the deal context and my approved
content into a reviewable first draft - and mark every gap instead of
inventing anything.

1. Ask me for my proposal template and where my approved product language,
   proof points, scope options, and pricing live.
2. Ask me who owns pricing, legal, security, and scope approvals.
3. Ask me about preferred length and tone, and anything that should never
   appear in a customer proposal.
4. Build the workflow as a reusable skill or automation that maps the
   customer's stated needs into the template, keeps customer statements
   separate from our inferences, fills every section it can support with an
   approved source, and visibly marks each missing fact or approval.
5. Never invent a commercial term. Create the draft, assign approval tasks to
   their owners, and put the draft link on the deal.
6. Test it by recreating two past proposals and show me both drafts.
7. Give the workflow a clear name so I can find and edit it later.

What good looks like

The recreated drafts should match the structure and claims of what you actually sent, with every missing price, term, or approval visibly marked rather than guessed. If it invented anything, say which line and rerun the same two proposals.

Choose your trigger

Trigger it from a short proposal-request form or from the opportunity stage change that means “we are proposing.” A form is usually better - it captures the scope questions the CRM record does not. Exclude renewals and anything using a standard order form.

What runs without you

Review every draft for the first month - proposals are low-volume and high-stakes, so there is no rush to hand this over. Once the structure is reliable, let it assign the approval tasks and update the CRM link automatically. The draft never goes to the customer without a human read. Check monthly that requests are still producing drafts.

Pairs well with prepare forecast reviews - same CRM connection, and proposals in flight are exactly what the forecast conversation is about.

Required

Calendar

Reads upcoming external meetings with attendees and timing.

Recommended

CRM

Reads the account, contacts, open deals, and recent activity.

Read access is all this needs - it writes nothing anywhere. Optional: email for recent threads, or your meeting assistant for what was said on the last call.

Paste this into Claude, ChatGPT, or your automation tool. It interviews you, builds the workflow, and tests it before anything goes live - have three past meetings you remember well, to test against ready before you start.

Help me set up an automated pre-meeting brief workflow.

Before each of my external customer meetings, it should deliver a one-page
brief I can scan in two minutes.

1. Ask me which calendar and CRM I use, and confirm they are connected.
2. Ask me which meetings count as customer meetings and which to skip
   (internal, personal, cancelled).
3. Ask me how long the brief should be and which sections matter most to me.
4. Build the workflow as a reusable skill or automation that covers, in this
   order: meeting objective and attendees, account and deal status, what
   happened since the last conversation, open commitments, and two or three
   questions worth asking.
5. Link every fact to its source record so I can open it if I need more.
6. Ask me where the brief should arrive, then test it on my three most recent
   customer meetings using only what was known before each one.
7. Give the workflow a clear name so I can find and edit it later.

What good looks like

Each brief should be scannable in two minutes, name the right people and deal stage, and surface something you would have had to dig for. If it padded with history you already knew, say so and rerun the same three meetings.

Choose your trigger

Run it 30–60 minutes before each external meeting, or as one morning digest covering the day - offer both and let each rep pick. Skip internal, personal, and cancelled events, and skip meetings with no external attendee.

What runs without you

This one writes nothing anywhere, so there is little to hand over - the whole workflow is read-only by design. What changes with time is trust: after a week you will stop opening the CRM to double-check it. Once a week, confirm briefs are still arriving for the meetings that have them.

Pairs well with automate meeting follow-ups - you already have the calendar and CRM; adding a meeting assistant covers both ends of the call.

Required

CRM

Reads every open deal with fields, activity, next steps, and notes.

Writes proposed corrections and owner questions, prepared for review.

Start with read access and a separate cleanup queue; grant write access once the checks prove reliable. Optional: your meeting assistant, to catch deals whose recent calls contradict the CRM.

Paste this into Claude, ChatGPT, or your automation tool. It interviews you, builds the workflow, and tests it before anything goes live - have one team’s live pipeline, and a few deals you know are clean and a few you know are stale ready before you start.

Help me set up an automated pipeline hygiene workflow.

On a schedule, it should scan every open deal and produce a cleanup queue
with the issue and a proposed correction for each.

1. Ask me which CRM I use, or accept an export of my open pipeline.
2. Ask me what counts as stale or incomplete for my team - no activity for a
   set number of days, no dated next step, a close date in the past, too long
   in stage, or a missing amount or contact.
3. Ask me which fields the workflow may prepare for review and which changes
   must become questions to the deal owner instead.
4. Build the workflow as a reusable skill or automation that checks every open
   deal against those rules and, for each flagged deal, shows the owner, the
   rule it broke, the supporting evidence, and a proposed fix.
5. Route uncertain changes - a new stage, amount, or close date - as questions
   rather than proposals.
6. Test it on one team's live pipeline and show me the queue.
7. Give the workflow a clear name so I can find and edit it later.

What good looks like

Known-clean deals should stay unflagged and known problems should appear with evidence you can act on. If it flags healthy deals, name the rule that misfired and rerun the same pipeline - noisy rules are the reason these workflows get ignored.

Choose your trigger

Run it nightly after your CRM activity has synced, plus once a couple of hours before the weekly pipeline review. Scope it to open deals owned by the team you are testing with before widening it - a first run across the whole company produces a queue nobody reads.

What runs without you

Start with read access and a separate cleanup queue. Once the rules stop misfiring, let it write the safe corrections - missing next-step dates, stale activity flags - and keep stage, amount, and close-date changes as questions to the owner. Those three always need a human, because they move the forecast. Check weekly that the queue is still being generated.

Pairs well with prepare forecast reviews - a clean pipeline is what makes the forecast brief trustworthy.

Required

CRM

Reads the pipeline with stages, amounts, close dates, forecast categories, and notes.

Two exports work just as well - this week’s pipeline and last week’s are all the comparison needs. Optional: a spreadsheet holding prior snapshots or manager adjustments.

Paste this into Claude, ChatGPT, or your automation tool. It interviews you, builds the workflow, and tests it before anything goes live - have this week’s pipeline and last week’s, and a past forecast call you remember ready before you start.

Help me set up an automated forecast review workflow.

Before each forecast call, it should compare the current pipeline with the
previous snapshot and prepare a brief covering only the deals worth
discussing.

1. Ask me which CRM I use, or accept two pipeline exports - current and
   previous - with owner, stage, amount, close date, forecast category, last
   activity, and notes.
2. Ask me what my team means by commit, upside, and risk, and what size of
   change is material enough to discuss.
3. Ask me how long the brief should be and who reads it.
4. Build the workflow as a reusable skill or automation that flags every
   material change, explains what changed and why it matters using the latest
   deal context, and prepares one manager question per flagged deal.
5. Group the brief by scenario - newly at risk, improved, slipped - and never
   repeat deals that simply stayed on track.
6. Test it by recreating last week's review and show me the brief.
7. Give the workflow a clear name so I can find and edit it later.

What good looks like

The brief should catch the deals you actually discussed last week and skip the routine movement. If it surfaced noise, raise the material-change threshold and recreate the same week again.

Choose your trigger

Run it one or two hours before the weekly forecast call. In the last two weeks of the quarter, add a daily run that reports only what changed since the previous brief. Scope it to the team whose forecast you are reviewing, not the whole company.

What runs without you

This one produces a brief for a human conversation, so there is nothing to hand over completely - the output is the input to a discussion. What you can automate over time is the delivery: once the thresholds are right, let it post to the forecast owner privately without you triggering it. Judgments about commit and risk stay with you. Check weekly that the brief arrived before the call.

Pairs well with automate pipeline hygiene - run the cleanup the night before and the forecast brief has better data to work with.

Required

CRM

Reads accounts, owners, open deals, renewal dates, and recent activity.

A current CRM export works if you would rather not connect it yet. Optional: enrichment sources for buying signals, or Slack to deliver each person’s queue privately.

Paste this into Claude, ChatGPT, or your automation tool. It interviews you, builds the workflow, and tests it before anything goes live - have a live territory with a mix of urgent, healthy, and incomplete accounts ready before you start.

Help me set up an automated account prioritization workflow.

On a schedule, it should rank the accounts I own and tell me which ones need
attention today, why, and what to do about each.

1. Ask me which CRM I use (or accept a CRM export) and which accounts are in
   scope.
2. Ask me for the five to eight signals that actually change where I spend
   time - a new buying event, an approaching renewal, an open deal without a
   next step, a drop in usage, or no meaningful contact for a set number of
   days.
3. Ask me how many accounts the queue should surface each day.
4. Build the workflow as a reusable skill or automation that ranks the
   accounts and, for each one, shows the specific signals it found, why the
   account matters now, and one practical next action.
5. Show missing data as missing - never treat it as a negative signal.
6. Test it on my current book of business and compare your top ten with mine.
7. Give the workflow a clear name so I can find and edit it later.

What good looks like

The top ten should overlap heavily with the accounts you would have picked, and every recommendation should point to a real date or activity. Where you disagree, say why and retune the signals before you move on.

Choose your trigger

Refresh it each morning for active territories, or every Monday for larger books. Replace the previous queue rather than appending, and timestamp it - a stale priority list is worse than none. Scope it to accounts you actually own.

What runs without you

This one only recommends, so it never writes to your CRM unless you decide it should. Once the ranking matches your judgment, let it deliver the queue automatically each morning. The decision about where to spend the day stays with you - the queue is an argument, not an instruction. Check weekly that the queue refreshed.

Pairs well with draft personalized outreach - the queue tells you who to contact, and the outreach workflow drafts the message.

Required

Meetings

Reads call transcripts with speakers and timestamps.

One connection is enough to start - paste individual transcripts if you want to trial the rubric first. Optional: Slack or Teams to deliver each brief privately to you.

Paste this into Claude, ChatGPT, or your automation tool. It interviews you, builds the workflow, and tests it before anything goes live - have three calls a manager has already reviewed - one strong, one weak, one mixed - and your coaching rubric if you have one written down ready before you start.

Help me set up an automated call coaching workflow.

For each selected sales call, it should prepare a short private coaching brief
a manager can use in the next one-to-one.

1. Ask me which call recorder we use and confirm it is connected.
2. Ask me for the observable behaviors we coach on - agenda setting, discovery
   questions, listening ratio, objection handling, next-step clarity - and for
   our written rubric or methodology if we have one.
3. Ask me how long the brief should be and who receives it.
4. Build the workflow as a reusable skill or automation that reviews each call
   against the rubric and produces one or two strengths, one or two
   improvement areas, a timestamped quote as evidence for each, and one
   practice exercise. Short - not a scorecard.
5. Keep every brief private to me. No hidden numeric scores, no
   team-wide rankings.
6. Calibrate it on three calls a manager has already reviewed and compare your
   briefs with their notes.
7. Give the workflow a clear name so I can find and edit it later.

What good looks like

The briefs should pick the same moments you would have picked and quote them accurately. If the advice is generic or the timestamps are wrong, say so and recalibrate on the same three calls before using it on anyone else.

Choose your trigger

Sample about three eligible calls per rep per week and run it before the next one-to-one. Restrict it to external customer calls above a minimum length - internal syncs and two-minute callbacks produce useless briefs and waste the sample.

What runs without you

Every brief lands with you first. Once they are consistently fair, let it run on the weekly sample without anyone triggering it - but a coaching brief never goes straight to a rep without you reading it first. Coaching is a conversation, not a report card. Check weekly that the sample is still being drawn.

Pairs well with automate meeting follow-ups - same transcripts, and one call then produces both the customer follow-up and the coaching evidence.