What is an AI assistant for an independent consultant that drafts Slack replies to clients for approval?

What the job actually is

An AI assistant for an independent consultant that drafts Slack replies to clients for approval is a teammate in each client Slack that writes the reply, then holds it until the consultant taps send. Human-in-the-loop for that job is the send gate: the outbound text is frozen on a card, and Send, Edit, or Skip is a person's tap. Copy-paste into ChatGPT writes a draft you still send yourself.

Independent consultants run this job as a guest in the client's workspace, or through a Slack Connect channel from their own. Shared channels sit on paid Slack plans on both sides. The Free plan only allows one-to-one external DMs. Pro is $7.25 per user per month billed annually, or $8.75 billed monthly, as of 23 October 2026.

Write a reply target into the engagement. Amy Sept, writing for Upwork on 13 March 2026, tells freelancers to reply within 24 hours, and to urgent requests within 4 to 6 hours or as soon as they are back online. Mursa publishes 4 business hours for standard client Slack, 1 business hour for urgent, and the next business day after hours. Its July 2026 workspace audit logged about 3,100 client-side messages across 14 client channels over 27 weeks.

Keeping the ask out of a buried thread is a neighboring job, on how consultants keep client requests from getting buried. The later chase until the work went out is on the follow-up teammate page. The send gate itself, written for a shop that shares client channels, is on the approval-before-send page.

Which tool wins which job

Fund the row that matches the leak. A sidebar draft, a tagged teammate, and a send gate in the client channel are neighboring jobs.

Guest accounts, Slack Connect, and who can install an app

Most independent consultants land in a client's Slack as a guest, or they share a channel through Slack Connect from their own workspace. Those two setups are different installs.

Guests cannot install or remove apps. They cannot authorize a Slack account to use apps. They cannot use Slackbot. They cannot set reminders for channels or members. Single-Channel Guests cannot use shortcuts. Multi-Channel Guests can use shortcuts only if a Workspace Owner turns that on. Conversation summaries still work for guests on paid plans.

Slack Connect is different. Each side stays in its own workspace. Apps added by the other organization show that organization's Slack icon, and people in the channel can see messages from bots and apps. A shortcut from an app is available to you only if that app is installed to your workspace. Adding an app to a client's workspace can need that client's admin. Ask them, rather than promising a one-click install in a workspace you do not own.

@ChatGPT does not respond to single-channel or multi-channel guests, even when connecting a ChatGPT account is optional. It is not supported in Slack Connect channels. Claude Tag cannot post into a Slack Connect channel. Lindy's Slack install needs a paid Slack plan. If you are the guest, copy-paste into ChatGPT and Slack's own summaries are the paths that still work without an install.

A prompt is not a send gate

Human-in-the-loop only holds if the send path cannot run until a person records a decision on the frozen text. Slack's own agent guidance puts approval gates before an agent creates, sends, or deletes anything, and wants the payload visible, not narrated. It then names progressive trust: start with confirmations, then Always allow.

Copy-paste into ChatGPT is the consultant's default: paste the client's message, get a draft, tweak, send. You still hit send, which is the right last step. The leak is quieter: the model never saw the rest of the thread, and nothing in Slack records that a person approved the exact text.

Lindy's pricing FAQ states that anything with outside impact waits for approval: sending an email, updating a ticket, posting to another channel, publishing a doc. Read-only lookups do not. Guardrails then give each integration Always allow, Require approval, or Don't offer. Guardrails apply in shared Slack threads only. Personal DMs, the web app, and iMessage are unguarded. Always allow turns the gate off for later writes.

Slackbot drafts in your Slackbot chat. Canvas edits wait for Confirm. That Confirm is not a send gate on every outbound in a client channel. The assistant this prompt names drafts the reply the client is waiting on, in that channel, and still waits for a tap.

The caveat that should decide the setup

The failure mode consultants name first is an unsupervised reply in the client's channel. One wrong send can cost the account. The draft is a starting point. The voice is still yours.

A second failure is public drafting. People in a Slack Connect channel can see messages from bots and apps. Keep the unsent draft off the thread the client can read. The recap the client sees still waits for a person to send. Safety of putting an agent in that channel is on the shared-channel page.

A third caveat is one inbox. Slack workspaces do not share apps. A guest cannot add ChatGPT, Claude Tag, Lindy, or Concrete to the client's workspace. If you work through Slack Connect from your own paid workspace, you can install on your side. Concrete is an AI employee that works in existing Slack channels. Every incoming message gets a receipt mark. Drafts land as Send / Edit / Skip cards. There is no auto-send mode. After downtime it sweeps channel history, thread replies included. Follow-ups survive reboots. Each morning it nudges the owner of every open ask. Install is one button per Slack channel, and each workspace gets its own private machine. It does not give one inbox across every client Slack. It is in design-partner preview; the longer thesis is on the vision page.

Step by step: draft the reply, then you send

This is the boring version that holds when you are a guest in several client Slacks. Pin it for yourself. Do not wait for the first unsupervised reply.

• Step 1: Name the gate. Send is a tap on the exact text. Edit rewrites it. Skip drops it. A prompt, a confidence score, or Always allow is a different setup.
• Step 2: Keep client-facing send on the gate. Lookups, summaries, and internal notes can run. Anything the client will see waits. If the vendor offers Auto or Always allow, leave it off on the send action in Slack Connect.
• Step 3: Ask before you install. A guest cannot add an app. If you need a teammate in the client's workspace, ask their admin. If you work through Slack Connect from your own paid workspace, install on your side.
• Step 4: Keep the draft off the shared thread. A bot message in Slack Connect is visible to the client. Draft in Slackbot, ChatGPT, or a private card. The reply the client sees still waits for a person to send.
• Step 5: Write the reply window into the engagement. 24 hours standard, 4 to 6 hours urgent, or 4 business hours standard and 1 business hour urgent, next business day after hours. An acknowledgment the same day is a reply. Silence until Thursday is how the thread dies.
• Step 6: Sweep each workspace in the morning. Open Threads and Activity, including workspaces that only show a badge on the icon. Channel history hides thread replies unless you open them. One AI does not watch every client Slack you are in.