Team Bot Guide

We have three bots in Discord. Each one has ONE job. This guide tells you which bot to use, where, and what happens after.

The 10-second rule

1. You know who should do the work → post in #🖋️task-assign.
2. You want an answer → tag @LeapAnswers in any channel.
3. Something is wrong and you don't know who owns it → post in #🙋bot-inbox.

That is the whole system. Everything below is detail.

The three bots

1. @LeapTasks — your tasks. It keeps every person's task list, adds new tasks, and marks tasks done. It is a tool, not a chat — it answers exact commands (below), not conversation. If you type a sentence at it, it will not understand.
2. @LeapAnswers — answers. It knows our clients, offers, prices, service areas, and guides. Ask it questions.
3. @LeapBuilder — changes. It blocks client calendars and edits client websites. Operations Specialists only. It always shows a plan first and waits for a ✅ — nothing happens without the ✅.

Your task list (@LeapTasks)

These commands are the whole tool:

1. See your open tasks: /whats-on-me anywhere. Only you see the reply. In your own 📋 room you can just type what's on me. This shows ALL your open tasks — including ones from older meetings.
2. Mark tasks done: /done 1, 3 — or just did 1, 3 in your 📋 room. The bot puts a ✅ on your message so you know it heard you.

How the numbers work: every task has its OWN number now — one number means one task, even when tasks come from different meetings. When you finish a task, its number retires; new tasks get the next number up. Every Sunday evening the bot renumbers your open tasks from 1 and posts your fresh list for the week in your 📋 room — the numbers in that post are the ones to use. 3. See what you finished: /whats-done (or show done in your room). Finished tasks never mix into your open list — they live here, and drop off after 7 days (still saved, just not shown). 4. Give someone a task: /task-assign — see the next section. 5. See what you gave others: /i-assigned. Only you see the reply. It lists everything you handed to other people, grouped by person, with each task's status (still open, or done with the date). 6. Hand one of your tasks to someone else: /handoff. Pick the task from the list, pick the person, add an optional note, then press ✅ yourself to send it. It moves off your list onto theirs. You can also pick a new due day for them — leave it empty and the task keeps its old due date. Made a mistake? Either of you can type hand back <number> in your 📋 room within 7 days to undo it.

Also good to know: tasks arrive by themselves after a team call — only people ON the call get tasks from it. If a task lands on your list that was never really a task, Sean can take it off; you will get a note in your room saying "nothing for you to do here." If you think the removal was wrong, reply undo <number> in your room and it comes back. Your list always shows where each task came from — the meeting, a specific call, or the person who assigned it.

Giving someone a task (#🖋️task-assign)

1. Go to #🖋️task-assign. Write the task in plain words — for example: "Sean: send me the loom for the ad library."
2. Or use the command: /task-assign. Tap each box (person, task, due_day) — do not type person:Sean as plain text, it will not work.
3. Every task needs a due day now. In the command, pick the day from the list (it shows real days, like "Mon Jul 27") and, if you want, a time — times show both US and Egypt clocks, like "3 PM ET · 10 PM Egypt". Do not type dates in your own words — the boxes only accept picks from the list.
4. The bot posts the task with ✅ and ❌, plus two small dropdowns for the due day and time. If you wrote the task in plain words and gave no deadline, the bot sets it to tomorrow, end of day — change it with the dropdowns BEFORE you press ✅ if that's wrong.
5. Press ✅ yourself and the task is sent — it lands on that person's list and in their 📋 room. No waiting for anyone. (Press ❌ if you made a typo.)
6. Wrong person? Reply in the thread: assign this to <name> — the bot fixes it.

Asking questions (@LeapAnswers)

1. Tag @LeapAnswers in any channel and ask in plain words: "What is the starting price for Act Right?" The answer appears right there — the bot opens a thread on your message and answers inside it, so the channel stays clean.
2. In your 📋 task room, it answers in the room — no thread.
3. To ask more, just reply in that same thread (or room) — no need to tag it again. It remembers the last couple of turns, so you can say "and for Cold AC?" and it knows what you mean. After two follow-ups it asks you to start fresh with a new tag.
4. It knows what it has been told. If it cannot answer, the information was never given to it — tell Sean, and it gets smarter.
5. One quirk: the word "ads" in a question can get blocked. Say "creatives" or "campaigns" instead.
6. Want the summary of a call you were on? Type /call-summary and pick the call (or leave it empty for your most recent one). Only you see the reply, and you only ever see calls you were on.

Reporting problems (#🙋bot-inbox)

1. Use this channel when something is wrong and you don't know who owns it — a broken page, an outdated guide, stale client info.
2. Write it in your own words. No format, no command. Add one line of words if you attach a screenshot.
3. The bot files it in the right place — a bug report, a guide flag, or a task — and it reaches Sean at his next AI session. It cannot get lost.
4. Nothing changes until it is approved. You cannot break anything by posting there.
5. This channel talks to a bot, not to the team. Do not have conversations there — use the client channels for that.

Changing calendars and websites (@LeapBuilder — Operations Specialists only)

Do this work in #🛠️builder. It is the one room for changing calendars and websites, so the client channels stay quiet for everyone else. One rule there: name the client in every command — pick it in the client box. That room does not know which client you mean, so it will ask if you forget (it never guesses). Blocking or unblocking a calendar counts as this kind of work too — do it in #🛠️builder.

1. Block a client's calendar: go to #🛠️builder and type /block-calendar, then pick the client in the client box. Dates it understands: 2026-07-20, today, tomorrow, weekday names, or a span like 7/20 to 7/25.
2. Open a blocked day back up: /unblock-calendar in #🛠️builder (name the client). Run it with no date to see the client's blocked days, then pick the one to open.
3. Put an image on a client's website: /add-image in #🛠️builder (name the client). The kind box is required (logo / owner-photo / team-photo / review / other). For reviews: attach the screenshot, paste the Google share link in caption, and read the bot's plan before you press ✅ — the ✅ is the proofread.
4. Change one fact on a setters page: /update-setters-page in #🛠️builder (name the client) — price, financing, hours, and more.
5. The client channels still work exactly the same if you prefer them — there the client is filled in for you. #🛠️builder is the tidy way, not the only way.
6. Everything after your command happens in a thread — the room stays clean.
7. Undo: the bot puts an ↩️ on the result inside the thread. An Operations Specialist pressing it within 7 days sees a reversal plan; ✅ runs it. It can only undo what the bot itself did.

Three rules that never change

1. The ✅ is the gate. No bot changes anything real without a human's ✅.
2. Slash commands first. Type / and pick from the list — every command shows its boxes. Plain-words tagging is only for bulk work (like sending many review screenshots at once).
3. When a bot confuses you, tell Sean. That is how the bots get better — every fix this week came from someone reporting friction.