Five prompts beat fifty
You now have more prompts than you will realistically use. That is normal and it is not a problem, as long as you finish this course with a routine rather than a folder.
The people who get real value out of AI in sales and support are not the ones with the biggest prompt library. They are the ones who run the same four or five moves every day until they stop thinking about them.
This lesson builds that. Everything you make here lives outside this site, in a note on your own machine, because LearnAI has no accounts and stores nothing you type. Nothing you write here is saved anywhere. That is deliberate, and it means the artifact is yours to keep and edit.
In plain English
- Workflow:
- The fixed order you do things in, so you stop deciding what to do next and just do it.
- Prompt pack:
- A small set of prompts you have tested and saved, ready to paste with your own details filled in.
- Human review:
- A person reading and approving output before it reaches a customer. Not optional.
- Template:
- A reusable structure. Useful for your own working notes, dangerous when it becomes the message a customer receives.
The daily routine
Here is the shape. Adapt the times, keep the order, and note that every single stage ends with you reading it.
MORNING, 15 MINUTES
[ ] List today's calls and messages that need a real answer
[ ] For each first call: run the ten minute brief prompt
[ ] VERIFY every name, number and date on the company's own website
[ ] For the call you are least confident about: 6 minutes of roleplay
DURING THE DAY
[ ] Draft support replies from documentation, never from memory
[ ] Read every draft in full before sending. Every one.
[ ] If a thread hits four messages with no convergence, pick up the phone
[ ] Voice-note 90 seconds after each call while it is fresh
END OF DAY, 15 MINUTES
[ ] Turn each voice note into a structured summary
[ ] Send recap emails with actions, owners and dates
[ ] Add one line of your own judgement to each summary
[ ] List anyone who has gone quiet for more than 10 days
WEEKLY, 20 MINUTES
[ ] Write follow-ups to the quiet list, each carrying something new
[ ] Run the generic detector over any outreach before it goes
[ ] Delete one prompt you never use. Improve one you use daily.
NEVER
[ ] Send a price, date or capability you have not personally checked
[ ] Paste customer names, account numbers or contract values
[ ] Send the same near-identical message to hundreds of people
This site has no accounts and saves nothing you type, so paste that checklist into your own notes app, your CRM or a pinned document. The version that helps you is the one you can reach on a Tuesday morning without opening a browser tab.
Your prompt pack
Five prompts. Fill in the square brackets once with your own product and buyer, and save the filled-in versions rather than the blanks.
-
THE BRIEF
I have a call with [name], [title] at [company], site [url].
We sell [product]. Give me: what they do, what changed in 12 months,
industry pressures, what this role worries about, three good questions.
Mark every company-specific claim CONFIRMED or UNVERIFIED.
-
THE DIFFICULT BUYER
Roleplay. You are [title] at [company type], busy and unconvinced,
happy enough with a competitor. One or two sentences at a time.
Do not be helpful. Push back on anything vague. Stay in character
until I type DEBRIEF.
-
THE REPLY FROM DOCUMENTATION
Below is a customer message and our documentation. Reply using ONLY
the documentation. Anything it does not cover goes under GAPS.
Warm, under 150 words, no padding.
MESSAGE: [paste, identifiers removed]
DOCS: [paste]
-
THE CALL SUMMARY
Turn these rough notes into SUMMARY, WHAT THEY CARE ABOUT,
ACTIONS with owners and dates, OPEN QUESTIONS, and MISSING.
Use only what is in my notes.
NOTES: [paste]
-
THE HONEST READ
Here is a message I am about to send: [paste].
Could this go to 500 other companies with only the name changed?
Quote the lines that give it away. What would a busy person feel in
the first four seconds? Then cut it to its shortest useful version.
Do not be encouraging.
Checkpoint
Save five filled-in prompts and one daily checklist outside this site, because a routine you can reach beats a library you never open.
Where the human review has to sit
Automation is tempting, and there are tools that will draft, send and follow up without you touching anything. Resist it in exactly three places.
Anything containing a commitment. A price, a date, a capability, a refund. AI states these with the same confidence whether they are true or invented, and the customer will hold you to whichever one they received.
Anything going to someone upset. Tone in a support reply to an angry customer is a judgement call, and judgement is the thing that does not come in the box.
Anything that claims personal knowledge. If the message implies you read something, met someone or noticed something, you had better have done. This is the line the whole course keeps returning to, and it is worth saying once more plainly: using AI to prepare better and reply faster is good, and using it to fake personal knowledge you do not have or to blast hundreds of near-identical messages damages your reputation and does not work.
If you only keep one rule from this course, keep this one. Never send a number, a date or a promise that you have not personally checked. It is the failure that costs the most and takes the least time to prevent.
Making it stick
Do not try to adopt all of it. Pick the two stages where your week actually hurts, run those for a fortnight, and add a third only when the first two are automatic.
Most people find the two are the morning brief and the end-of-day summary, because those are the ones that quietly cost you deals rather than time. But your week is yours, and the fastest way to find out which two matter is to ask.
I work in [sales / customer service] and my week looks like this:
[roughly what you do, how many calls, how many messages, what slips].
Here are the five stages I could add AI to: prospect research,
outreach drafting, call rehearsal, answering customers from our docs,
and call summaries with follow-ups.
Pick the two that would save me the most and tell me why, based on
what I described rather than what is generally true. Then tell me what
could go wrong in each, and what I should be checking before I send.
Improve one prompt a week rather than adding one. Take the prompt you use most, look at what you always end up editing in the output, and put that instruction into the prompt itself. After a month yours will be far better than anything you could copy from someone else.
You are done
That is the course. You can research a company in ten minutes and know which parts to distrust, write outreach that survives a real inbox, rehearse the objection you always fumble, answer customers from your own documentation rather than from an AI's imagination, and turn a messy call into something your future self can use.
Finish the quiz and the Conversation Pro badge is yours.
๐ Quiz
Question 1 of 4Why does the workflow checklist live in your own notes rather than on this site?