Independent Dots-Bot guide
The First Week With Dots in Slack: Five Small Tasks to Try
Five reviewable Slack tasks that help a team learn what a dot can do and where it needs clearer instructions.
In this article6 sections
The first week with a new agent should produce useful work, not a sprawling automation nobody can check. In Slack, start with five small tasks tied to real conversations. Keep each result in draft form until a teammate has compared it with the source.
Day 1: summarize one thread
Pick a short project thread. Ask for the decision, supporting evidence, and unanswered question, each with a link to its source message. If there was no decision, the dot should say so. Our Slack workflow guide has a reusable decision-brief format.
Day 2: list action items
Choose a handoff with several people. Request the action, explicitly assigned owner, deadline if stated, and missing information. Do not let a mention of someone’s name turn into an assignment. Review the list with the channel owner.
Day 3: draft a status update
Ask for three short sections: completed, in progress, blocked. Name the intended audience and limit the sources. Read the draft against the project board before publishing it. If the dot cannot open a linked document, use our permissions checklist to diagnose why.
A useful test is to remove a known detail from the thread and see how the draft responds. It should flag the gap, not silently invent the missing date. If it does guess, correct that behavior in the same task so the next attempt has a clearer boundary.
Day 4: prepare questions for a meeting
Give the dot the current goal and ask for questions that would change the next decision. This is more helpful than asking it for a generic meeting agenda. Remove questions already settled in the channel.
Day 5: improve the instructions
Compare the five results. Which mistake repeated? Add one clear instruction to future briefs, such as “separate approved decisions from proposals” or “link every number to its source.” The goal is a dependable review habit, not a longer prompt for its own sake.
Keep the team in the loop
Pick one person to own each output before the experiment begins. Teammates should know whether a summary is a working draft, an approved decision, or a message ready to share. When a dot asks for access or approval, the owner can decide whether that step belongs in the task instead of assuming the person who first mentioned the dot will handle it.
At the end of the week, save the two task formats that consistently helped. Record the source scope and review step with them. Retire the prompts that produced noise. A smaller playbook is easier for a new teammate to follow than a long list of clever examples nobody has checked.
OpenAI says dots can be reached in Slack and can keep working between conversations, subject to connected access and controls. Check the current setup guidance, then use our Slack integration page for related guides. If you have not written a first request yet, try this first-task guide.
You have reached the end of this guide. Check the sources and linked guides for the latest details.