Slack channel system code · the LeadLift OS code

How it works

The channels fall into six groups. Read them in this order. A message to the team ends with [LINK], which opens the record in the app.

1. Client channels. When a new client pays, the server makes a private channel for that client.
   1. The server invites each Active team member who has a Slack id. It also invites the bot and Viktor.
   2. The client gets a Slack Connect invite by email.
   3. Fidel's welcome message comes in, posted as Fidel. It asks the client to fill in the onboarding form and book the call.
   4. The bot bookmarks the client's Raw Footage folder at the top of the channel. Clients put their raw footage there. The team can also keep saved static ads there.
   5. At Client Review, the bot posts "your ads are ready to review" with a link. The client approves, or sends notes back.
   6. From 12 Oct, a script moved to With Client also posts here, with its lead form questions.
2. Onboarding and payments. Three channels follow a new client.
   1. #payments gets one line for each paid Whop payment. It names the person, the company and the billing type, with a link to the client.
   2. #onboarding gets one launch message for each new client. Its thread is the running tally.
   3. In that thread, each finished step adds a ✔ line. A blocked step adds a ✗ line with the reason.
   4. #onboarding-forms gets each submitted onboarding form in full.
   5. If a form matches no client, a "pick the client" menu comes in the thread. One pick links it.
3. Edits and scripts. Each stage move on the boards posts in one channel.
   1. #new-creative: the Raw Footage scan, every 12 hours. Each client with new footage gets one thread reply.
   2. #editor-updates: a card moved to To Edit. It names the creative, the footage, the due date and the editor.
   3. #creative-review: a card at Internal Review. It tags the reviewer.
   4. #amendments: a redo, client changes, or a script that needs changes. Each comment is a thread reply.
   5. #approved-creative: ads at Ready To Launch, and approved scripts. It gives the launch date and the Ads Manager link.
   6. #scripts-to-write tags the writer of a new script. #script-review tags Fidel when a script needs a check.
4. Creative management. #creative-management gets the board digest on Monday, Wednesday, Friday and Sunday at 3pm Central.
   1. The digest is one page with three tabs.
   2. The tabs show what changed, what to do today, and the same list for each client.
5. Tasks, launches and calls. These channels follow the other boards.
   1. #new-tasks gets each new task. It tags the person who has it.
   2. #task-updates gets a task move to Blocked, Amendments, In Review or Complete.
   3. #campaign-launches gets each new launch with its open checks, and each launch that goes Live.
   4. #call-transcripts gets one message for each Fathom call. The summary is in the thread.
6. Failures. Two channels tell a person that something did not work.
   1. #pipeline-errors: a known failure on the editing and scripting line. It tags Fidel.
   2. For example, a review link that did not post in a client channel goes here.
   3. #sentry: every failure that nothing else reports, and every failure that only a person can fix.
   4. Each #sentry post says what failed and where. The steps to fix it are in the thread.
   5. #sentry is for the person who looks after the system. Today, that is Icarus Growth.

The moving parts

One server sends almost every message. Make sends one: Fidel's welcome.

What you can safely change

Green: change it in the app. Amber: ask Claude in the LeadLift code folder, then check the result. Red: do not change it. Call us.

What connects to this

This tab shows what makes the posts, and who reads them.

If something looks wrong