Claude Tag lives inside Slack. You do not ask it a question, you give it a task with an outcome and the context, then keep working. Setup in 4 steps and 5 whole-job prompts for a business of one.
You type a question, it types an answer, you copy it somewhere and do the rest yourself. That is the chatbot habit, and it is why Claude keeps disappointing you.
Claude Tag lives inside Slack. The difference is that you do not ask it a question. You hand it a job: the whole task, what "done" looks like, and what it needs to know. Then you keep working. It comes back with the thing. You read it, fix what you would fix, and send it.
If you use Slack with clients or contractors, this is where it earns its keep. Setup takes 4 steps. Then 5 whole-job prompts written for a business of one.
Each one has the 3 parts a coworker needs: the outcome, the context, and the shape of the finished thing. Type @Claude first in Slack, then paste.
Reads the week in the channel and writes the update you can send as is.
@Claude Read this week's messages in this channel. Pull out what got done, what is still open, and any decisions we made.
Write a client update under 150 words I can send as is. Plain English, written to [client's first name], and end with the one thing I need from them this week.
Turns your notes from a call into a record and a message confirming it.
@Claude Here are my notes from today's call with [client]: [paste your notes, or point at the thread]. Write a recap in 3 parts: decisions, who does what by when, and open questions. Then draft a 4 line message to [client's first name] confirming it, ending with "reply if I got anything wrong."
Finds every promise in the last 2 weeks that nobody has closed.
@Claude Go through the last 2 weeks in this channel and list every promise made to a client or by a client that has no reply yet. Group them by person. For each one, one line on what is owed and by whom, and a 2 line nudge I can send.
The week in 5 bullets, so Monday starts with a list instead of a scroll.
@Claude It is Friday. Summarize this week in this channel for me in 5 bullets: won, finished, stuck, waiting on, and next week. Under 120 words. Name the people. Skip anything that was resolved in the same day.
Answers the message you have been avoiding, in your register, with one clear next step.
@Claude [Name] sent this: [paste their message]. Draft my reply. Context they need: [2 facts, e.g. the invoice was sent Tuesday, the revised date is Fri 5 Sep]. Warm and direct, under 100 words, end with one clear next step. Do not promise anything I have not said here.
When a prompt comes back thin, one of these 4 parts was missing. Add it and send the job again.
Same shape, bigger jobs. Both take it a few minutes and take you an afternoon.
Notes in, first draft of the proposal out, in your structure.
@Claude Here are my notes from a discovery call with [prospect]: [paste]. Draft a proposal with these parts, in this order: 1) the problem, in their words 2) what I would do about it in 3 steps 3) what is included 4) the price of [your package] at [price] 5) the next step. Under 400 words, written to them, no jargon. Flag anything they said that I did not answer.
A long back-and-forth becomes a list of what has to happen.
@Claude Turn this thread into a checklist: [link to the thread, or paste it].
One line per task, an owner for each, and a date if one was mentioned. Put anything with no owner at the bottom under "unassigned". Nothing else.