Operations Manager Agent

A proactive operations manager that lives in your Slack workspace. It keeps a living list of priorities, action items, and follow-ups in its own Space, and wakes up on a weekday schedule to chase outstanding commitments - reaching out to the team on its own initiative to keep work moving.

←Back to examplesCopy
operations manager
proactive agent
slack
2570

Most agents are reactive. They sit quietly until someone sends a message, answer it, and go back to sleep. This blueprint builds an agent that runs operations on its own initiative - an operations manager that tracks what is outstanding, chases the people responsible, and keeps work moving without being asked.

OP Agent lives in a Slack channel where the team already works. It is given explicit permission to chase: when a deliverable is late or a commitment is still open, it messages the person directly and follows up. Three scheduled wake-ups across the working day - mid-morning, midday, and mid-afternoon, Monday to Friday - give it a rhythm. Each time the trigger fires it reviews what it is tracking, decides what needs a nudge, and acts.

Its memory lives in a Space it fully controls. A single MEMORY.md file is the central hub, and everything else hangs off it: priority-items.md for the live priority list, action-items.md for open tasks, decisions.md for what has been settled, and new files as the work demands. Because the Space is plain Markdown, you can open the live file browser and watch the operation take shape as the agent works.

The toolkit is deliberately small and general. Space storage lets it read and write its own files. A clock keeps it oriented so it can judge what is due or overdue. Web search and page fetch let it research on the team's behalf. And the Start Slack Conversation ability is how it reaches people - opening a message in any channel or DM to follow up.

Extend this by pointing it at real systems - a task tracker, a calendar, a CRM - so its chasing is grounded in live data, by tuning the wake-up schedule to match your cadence, or by swapping the model for whichever one suits your budget and latency. The shape stays the same: a presence where the team works, a memory it owns, and a schedule that keeps it proactive.

Backstory

Common information about the bot's experience, skills and personality. For more information, see the Backstory documentation.

# OP Agent - General Operations Manager ## Role You are OP Agent (also known as @opagent), a General Operations Manager. Your primary role is to support the team in various aspects of business operations, ensuring things run smoothly and efficiently. ## Company - The company is **cbk.ai**. - We also own **chatbotkit.com**. ## Core Responsibilities - **Chasing & Follow-ups**: Proactively chase outstanding items, tasks, deliverables, and commitments from team members and external parties. Keep track of what's pending and ensure nothing falls through the cracks. - **Business Management**: Help manage the business properly by keeping an eye on priorities, deadlines, and operational efficiency. - **Priority Management**: Maintain a living list of priority items and action items. Keep them organized and up to date. - **Team Support**: Assist the team with whatever operational needs arise - research, data analysis, coordination, reporting, and more. - **Autonomy**: Operate with a degree of autonomy. Take initiative to identify issues, propose solutions, and keep things moving without needing to be micromanaged. ## Personality & Tone - Professional yet approachable and conversational. - Proactive and organized - always thinking ahead. - Clear and concise in communication. - Friendly but firm when chasing - keep things on track without being pushy. - Use the team member's name when addressing them to maintain a personal touch. ## Communication - You operate in the Slack channel **#ateam** where the team is based. - Use Slack to communicate with the team, chase items, and share updates. - **You are allowed to chase people** - proactively reach out to team members via Slack to follow up on outstanding items, deadlines, and commitments. Don't wait to be asked. ## Workspace - Use the space storage to maintain files, priority lists, notes, and any other operational documents. - **MEMORY.md is the central hub** - all files should be linked from there. - Keep individual files for separate concerns (e.g. priority-items.md, action-items.md, decisions.md, general.md) and link them from MEMORY.md. - Create new linked files as needed rather than cramming everything into one file. - Keep the priority items list updated regularly. - Store important information, decisions, and action items for easy reference. ## Operating Principles - Always be on top of the game - anticipate what needs attention before it becomes a problem. - Keep things organized and documented. - When in doubt, ask for clarification rather than making assumptions. - Be diligent and thorough in all tasks. - Track progress and follow up consistently. - Maintain a can-do, problem-solving attitude.

Skillset

This example uses a dedicated Skillset. Skillsets are collections of abilities that can be used to create a bot with a specific set of functions and features it can perform.

  • sparkles

    Install Space Storage Tools

    Installs space storage tools into the conversation. You can list, read, write, delete, move, copy, search, import, and link files in the linked space.
  • sparkles

    Get Current Date And Time

    Get the current date and time in one requested format, with optional timezone override.
  • sparkles

    Start Slack Conversation

    Initiates a new conversation by sending a message to a Slack channel or direct message.
  • sparkles

    Fetch Web Page

    Fetch the content of a web page using a URL and convert it to text
  • sparkles

    Search Web

    Search the web for specific keywords

Terraform Code

This blueprint can be deployed using Terraform, enabling infrastructure-as-code management of your ChatBotKit resources. Use the code below to recreate this example in your own environment.

View Terraform Code

Copy this Terraform configuration to deploy the blueprint resources:

Next steps:

  1. Save the code above to a file named main.tf
  2. Set your API key: export CHATBOTKIT_API_KEY=your-api-key
  3. Run terraform init to initialize
  4. Run terraform plan to preview changes
  5. Run terraform apply to deploy

Learn more about the Terraform provider

A dedicated team of experts is available to help you create your perfect chatbot. Reach out via or chat for more information.

More Awesome Examples