Teams bot and Slack bot development for internal requests
A Teams bot is an app inside Microsoft Teams that employees message to raise IT and HR requests, approve items, look up records in ERP or CRM and receive alerts. Goldenroz builds custom bots for Teams and Slack that sign users in with your identity provider, respect each person's permissions and act in your systems through their APIs. Projects start at $25,000, fixed price per phase.
From $25,000, fixed price per phase
Updated 2026-11-14. By Shai Goldenberg
What usually goes wrong
- Requests scattered across channelsPassword resets, laptop orders and leave questions arrive as direct messages to whoever is online. Nothing is tracked and the same person answers the same question every week.
- Approvals stuck in emailA purchase order waits two days because the approver has to open the ERP on a laptop. The decision itself takes ten seconds.
- Five systems to answer one questionSales staff open CRM, ERP and a spreadsheet to tell a customer where an order stands. Each lookup needs a different login.
- A pilot bot that sees too muchA quick internal bot runs on one service account and returns the same data to every user, including salaries and customer records they should not see.
What is included
- Request and intent designThe requests the bot handles, the data each one needs, who may ask and where each request lands: a ticket, a workflow or a person.
- Sign-in and permissionsSingle sign-on through Microsoft Entra ID for Teams, and Slack OAuth with the narrowest scopes that work. The bot acts as the user, so it returns only what that user may see.
- Cards, buttons and formsAdaptive Cards in Teams and Block Kit in Slack for approvals, forms and results, so most tasks finish in two taps without leaving the chat.
- System connectionsLookups and actions in ERP, CRM, HR, ticketing and internal databases through their APIs. Reads come first, and writes need a confirmation step.
- AI answers from internal contentPolicy and how-to answers from approved documents, with the source linked. When the content does not cover a question, the bot says so and opens a request.
- Admin packaging and audit logAn app package and permission list your IT admin can review and approve, plus a log of every question, tool call and model cost.
Microsoft Teams bot development: identity, permissions and admin approval
A Teams bot is registered as an application in Microsoft Entra ID and delivered as an app package that your Teams administrator approves and publishes to the organization. The work therefore starts with your IT team, not with the model. We give them the manifest, the list of Microsoft Graph permissions requested and the reason for each one.
The safest design passes the user's identity through to every system. With single sign-on, the bot receives a token for the person who is typing and calls your APIs on their behalf. An employee who cannot open a record in the ERP cannot get it from the bot either.
Goldenroz is an independent engineering firm and not a Microsoft partner. The bot runs in your tenant and your cloud subscription, and you own the code.
Custom Slack bot or a workflow tool
Slack's Workflow Builder and Microsoft's Power Automate cover simple cases well: a form, an approval, a message to a channel. If that is all you need, use them. A custom bot earns its cost when requests arrive as free text, when the answer needs data from several systems, or when the logic must be tested and versioned like other software.
The two often work together. The bot understands the request and collects the details. A flow you already run carries out the steps. Power Automate consulting covers the flows themselves.
A Teams chatbot that answers from company data
Staff ask which customers have overdue invoices or how many units of a part are in stock. The bot can answer if it is connected to the systems that hold the data, with controls that hold up under review.
We connect company data to Claude through MCP. The model chooses from approved queries and never writes SQL. Access is read-only by default, personal data can be masked and every request is logged with the user's name. The approach is described under MCP server development, and wider actions across systems fall under the parent AI chatbot development service.
How the work runs
Scoping call
Before the projectWe review real transcripts, pick the intents worth automating and agree what the bot must never do. You get a fixed price.
Prototype
About 1 to 2 weeksA working bot on the top few intents, tested against your past conversations in a private channel.
Production build
Roughly 4 to 8 weeksSystem integrations, fallbacks, handoff, logging and channel setup. The range depends on integrations and on WhatsApp account approval.
Limited launch
At launchThe bot handles a share of conversations or selected hours first. Your team reviews transcripts daily.
Widen
After launchNew intents are added in order of volume, each tested against the conversation set.
What it costs
Each phase has a fixed price agreed before work starts. Model usage and WhatsApp messaging are billed by the providers to your own accounts.
- Support or ordering botFixed price per phaseFrom $25,000
- Multi-channel or multi-brand platformsScoped per project$100,000 and up
- Scoping callEnds with a written scope and a price$0
- Model and WhatsApp usageBilled to your own accountsPaid to the providers
Who it is not for
- Budgets under $25,000. Workflow Builder, Power Automate or Copilot Studio is the better first step.
- Bots that monitor employee conversations or score staff. We do not build surveillance tools.
Who does the work
Shai leads the technology side: business software, SaaS and mobile apps, payments and escrow systems, Postgres security, AI agents built with Claude Code and MCP, and IT and infrastructure projects with senior infrastructure engineers.
Questions buyers ask
How much does a Teams bot cost to build?
Projects start at $25,000 at a fixed price per phase, set after a free one-hour scoping call. Model usage and cloud hosting are billed to your own accounts.
Can one bot run in both Teams and Slack?
Yes. The request logic, permissions and system connections are built once. Each platform gets its own thin layer for sign-in, cards and message formats.
Does the bot see all our Teams or Slack messages?
No. It receives messages sent to it directly and messages where it is mentioned, plus anything covered by scopes you approve.
Should we use Copilot Studio instead of a custom bot?
Use a packaged tool when your requests are standard and your data sits in systems it already connects to. Build custom when you need your own permission rules, systems with no ready connector, a choice of model, or tests that run before each release.
How long does it take?
A working prototype on the top few requests typically takes one to two weeks. Production takes roughly four to eight weeks. Admin approval of the app and access to internal APIs often set the timeline more than the build does.
Guides on this topic
- Nine steps to build a WhatsApp chatbot on the official Cloud API: account, number, webhook, AI layer, handoff, templates and launch. See the full checklist.
- Compare Telegram, Microsoft Teams, Slack and Instagram as chatbot channels: who you can reach, who may start a conversation, approvals and platform rules.
- How the WhatsApp Business API works: Cloud API, templates, the 24-hour customer service window, per-message pricing and the setup steps. See what to plan for.
Chatbots by channel and use case
- AI chatbots
- Appointment booking bots
- Chatbots for banking and insurance
- Customer service chatbot development
- Chatbots for ecommerce
- Enterprise chatbot development
- Chatbots for healthcare
- Instagram and Messenger chatbots
- RAG and knowledge base chatbots
- Chatbots for real estate
- Telegram bot development
- Website chatbot development
- WhatsApp Business API integration
- WhatsApp chatbot development
- Chatbots
Talk to the person who will do the work
One hour, no sales team. You talk to Shai Goldenberg, the CTO, about your systems or your product, and you leave with a clear next step and a price range.