Consultancy Clients Lounge

A small consultancy server: booking through tickets, a clients lounge, a resource shelf and private retainer threads.

  • 5 categories
  • 18 channels
  • 6 roles
  • Small
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

FRONT OFFICE

  • practice-overview

    What the practice does, who it is for and how an engagement starts. Book through #book-a-session.

  • engagement-terms

    Rates, response times, cancellation terms and confidentiality. Read before booking.

  • book-a-session

    Press the button to request a session. You will get a private ticket to agree dates and scope.

  • practice-bulletin

    Workshop dates, office-hours changes and new resources on the shelf.

CLIENTS LOUNGE

  • clients-lounge

    Clients talking to clients. Peer advice, introductions, what is working.

  • ask-the-consultant

    Questions whose answer helps everyone. Anything specific to your engagement goes in your private thread or a session.

  • client-wins

    Results, milestones and what changed. Post the outcome, not the confidential detail.

  • resource-shelfHidden from @everyone

    Frameworks, templates and reading, posted by the consultants.

  • workshop-recordingsHidden from @everyone

    Replays of group sessions and office hours, one message per session with the date.

RETAINER DESK

  • engagement-desk

    One private thread per retainer client, opened by the consultant. You see your thread only; do not post in the channel itself.

  • deliverables-drop

    Reports, decks and recordings for retainer clients, posted into your thread and linked here by date.

OFFICE HOURS

  • Office Hours
  • One-on-One
  • Waiting Room

BACK ROOM

  • practice-chat

    The consultants, out of client view.

  • client-pipeline

    Prospects, booking tickets in progress and renewals due. One message per prospect.

  • session-prep

    Notes before each session and what to follow up after it.

  • Practice Call

Roles

  • Principal ConsultantAdministrator
  • Associate ConsultantModerator
  • Retainer Client
  • Client
  • Prospect

Overview

For a consultant or a two-person practice whose clients should meet each other without meeting each other's problems. The front office is read-only: #practice-overview says what the practice does, #engagement-terms is the rules channel, #book-a-session holds a ticket panel that turns a booking request into a private conversation, and #practice-bulletin carries announcements. Prospects see only that. Once someone becomes a Client they get the Clients Lounge: #clients-lounge for peer conversation, #ask-the-consultant for questions the whole group benefits from, #client-wins for results, and two read-only channels, #resource-shelf and #workshop-recordings, where the consultant posts frameworks and session replays. Retainer clients get one more category. #engagement-desk is where the consultant opens a private thread per client, so a retainer client sees their own thread and nobody else's, and #deliverables-drop is where reports and decks land. Office hours run in a stage channel with a two-seat One-on-One room and a Waiting Room beside it. The Back Room, with #client-pipeline and #session-prep, is visible to the consultants and to no client at any tier.

When to use it

Clients email questions that half your other clients have already asked, retainer work is scattered across DMs, and prospects have no way to book without a back-and-forth. This layout gives every client a lounge and a shelf of resources, retainer clients a private thread each, and prospects one button that opens a booking conversation.

What makes it different

  • Prospects see the front office and the booking panel only; the lounge opens with the Client role.
  • Retainer clients get a private thread each in the engagement desk, invisible to other clients.
  • The resource shelf and workshop recordings are read-only, so they stay a library, not a chat.
  • Office hours run on a stage with a two-seat One-on-One room and a Waiting Room next to it.
  • The Back Room with the client pipeline is hidden from every client tier.

Recommended Vetox setup

  • Tickets

    Post the booking panel in #book-a-session so a prospect's request becomes a private ticket where dates and scope are agreed.

  • Reminders

    Schedule a Reminder in #clients-lounge an hour before office hours open on the Office Hours stage.

  • Auto Roles

    Give Prospect on join so new arrivals land in the front office; promote to Client and Retainer Client by hand after a booking.

  • Embed Messages

    Pin an embed in #engagement-terms with rates, response times and cancellation terms so the rules channel answers the questions before they are asked.

Questions

How do private retainer threads work?

The consultant opens a private thread in #engagement-desk for each retainer client and adds them to it. A private thread is visible only to the people added, so two retainer clients in the same channel never see each other's work.

What does a prospect see?

The Front Office category only: the practice overview, the engagement terms, the booking panel and the bulletin. The Clients Lounge and the Retainer Desk deny ViewChannel to @everyone and are granted back to the client roles.

Do I need the stage channel for office hours?

A stage lets you speak to every client at once while they raise a hand to ask. Use the One-on-One voice room, capped at two, when a question turns private, and the Waiting Room to hold the next person.

Common mistakes

  • Answering a retainer client's question in #ask-the-consultant, which exposes their situation to every other client in the lounge.
  • Giving prospects the Client role on arrival so the lounge fills with people who have not booked anything.

Consider instead

  • Agency Client Portal You run a team with parallel projects and each client needs a full private category, not a thread.

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages