How to Manage Client Revisions Without Slack Turning Into Chaos

Somewhere around message 40 in the client's Slack Connect channel, someone asks "did we ever fix the thing with the pricing table?" and nobody can say for sure. It's in there somewhere. Maybe. You scroll. You search "pricing." You find three unrelated mentions and one screenshot with no caption.

This is the normal end-state of using Slack to manage revisions, and it's not a Slack problem — Slack is doing exactly what it's for, which is conversation. The issue is that a revision list isn't a conversation. It's a list of discrete items that each need a status, and a scrolling feed is structurally the worst possible place to keep one.

Why Revisions Specifically Break Down in Slack

A support question or a quick "looks great, thanks!" works fine in a chat feed — it doesn't need tracking, it's resolved the moment it's answered. Revisions are different: each one is a task with a lifecycle. Requested, in progress, done, confirmed. Slack has no concept of any of that natively.

What actually happens instead:

Revisions get requested inline, mixed in with everything else. A "can we make the header bigger" sits between a scheduling question and someone sharing a meme. It's easy to genuinely miss.
There's no single source of truth for what's outstanding. Ask three people on the project "what's left to fix" and you'll get three different half-remembered lists.
Reactions become a fake status system. A ✅ emoji on a message is doing the job of a status field, badly — it disappears into scroll-back the same as everything else, and there's no way to filter "show me everything still open."
Clients re-ask because they can't verify anything themselves. If a client can't independently check whether something's been actioned, the only tool they have is asking again, which is where a lot of Slack noise actually comes from.

None of this is really about Slack being a bad tool. It's a great tool for the thing it's for. Revisions need a list, not a feed.

See how a real ticket queue sits next to your existing channel →

The Fix Isn't "Stop Using Slack"

For a lot of small agencies, the client relationship genuinely lives in Slack — quick questions, a fast "yes that works," general back-and-forth. Ripping that away and forcing everything into a formal system usually fails, because clients like the low-friction chat and won't willingly give it up.

The fix that actually holds is narrower: keep Slack for conversation, and give revisions specifically somewhere else to live — a place with a status, that both of you can check without scrolling, and that doesn't depend on anyone's memory of message 40.

That's the whole shift. Not "stop talking to clients in Slack." Just: "the revision list isn't the chat log anymore."

What That Looks Like With Lantern

Lantern gives each client a private portal for exactly this — separate from wherever you're chatting day to day. When a revision comes up in Slack, the move is simple: "good one, pop that in your portal so it doesn't get lost" — a 20-second detour that turns a message that would've scrolled away into a tracked item with a status.

Each request gets logged with a description (or a short screen recording, which is often faster for showing "move this" or "make this bigger" than typing it out), and it shows up in your dashboard alongside every other open item across all your clients — not just this one. You update the status as you work through it; your client can check "In Progress" or "Fixed" themselves, without a Slack message asking for an update.

Nothing about this requires leaving Slack behind. It just means the actual list of what's outstanding lives somewhere built to hold a list, while Slack keeps doing what it's good at.

Rolling This Out Without a Big Announcement

You don't need a kickoff call to change how this works. The rollout that actually sticks is small:

Next time a revision comes up in your Slack channel, reply with the portal link instead of just acknowledging it: "logged — you can track it here."
Update the status when you start and finish the work, so the client sees the payoff of checking the portal instead of asking in chat.
After two or three of these, most clients start submitting new revisions directly through the portal, because it's genuinely less friction than typing it into Slack and hoping it doesn't get lost.

Slack stays exactly as useful as it was for actual conversation. The list of what's outstanding just stops living inside a feed that scrolls away.

Pricing, Briefly

The Individual plan is £12.50/month for up to 5 clients with unlimited requests, 14-day free trial, no card required. The Team plan is £30/month flat for unlimited clients — useful if you're running more than a handful of Slack Connect channels already.

Try Lantern free for 14 days — no card required →

Set up your first client portal in about five minutes, and drop the next Slack revision request straight into it.