Create Accountor Login
Docs

The Bot Builder

Part of the MountDev Ops Bots documentation. Updated November 20, 2026

MountDev Ops Bots documentation | Updated November 20, 2026

One page holds a bot's ten sections. Open a bot from the list (action bots.get), change what you need, and choose Save (actions bots.save and bots.catalog). Every save is a version. You can only give a bot what you could do yourself.

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

1. Who It Is

The bot's name (up to 40 characters, different from your other bots), a picture, its AI provider (Claude or OpenAI), its model, and its instructions (up to 4,000 characters). A key typed into the instructions is refused.

2. Where You Can Talk to It

Team Chat, Project Chat, Helpdesk tickets, a website chat, Workflows, and the API and MCP. Each is a switch and each starts off. The Phone app is later (Planned). A bot refuses a place that is off. How a bot is run and checked is on Asking a Bot, and asking in each place arrives in later updates (Planned).

3. Who Can Talk to It

Everyone in your company, chosen roles, chosen teams, or chosen people. A person asking a bot only ever gets what that person could see.

4. Communication Limits

Choose whether the bot may talk to people outside your company (clients and visitors) at all. For each place that does, choose a draft for a person or a live reply. Live replies are offered only in chat places, never for email, which is always a draft for a person. Choose the allowed recipients: the client's own company, or chosen domains. A bot never sends email on its own.

5. What It Can See

The apps, modules, saved views, and fields it may read, always under your field rules. What it learns from is on its own page.

6. What It Can Do

Pick actions from the list of actions you could do yourself. Each is Allowed, Needs approval, or Never. Spending and deleting can never be Allowed: they always need a person, every time. Changing people, access, or billing, sending email, and approving a proposal are never offered.

7. When It Acts

When asked by name, on a new ticket, on an event, on a schedule (every 15 minutes to every week), and from a Workflow. Each starts off.

8. Handoff and Escalation

When the bot hands the question to a person or a team (it is unsure, it is asked for a person, a price or legal question, its limit is reached), who it hands to, and what it says.

9. Voice and Label

A tone, a language, and the label the bot always shows: Bot, Automated, or Virtual Assistant. The label cannot be blank.

10. Spending

The monthly limit and the limit for one run (in dollars) and the step limit are figures you type in. They start empty, and the bot cannot be turned on until all three are set. Owners and admins are told at 80 percent of the monthly limit and the bot stops at 100 percent. See Spending Limits.

Try the bot in Test at the bottom of its page before you turn it on (see Test).

Once all three are set, Turn On (action bots.turn_on) makes the bot available, and Turn Off (action bots.turn_off) stops it at any time. Both are on the bot's page and in the list.

Remove (action bots.remove) takes a bot out of the list. The bot's versions and its log stay in its history.

Ask Us Anything

We’d love to hear from you!