A small sales team could log deals in a shared CRM app, then let an authorized agent update the matching record from incoming email while a weekly workflow sends the pipeline summary. Another team might route leave approvals or low-stock alerts through the same kind of app. Botchi Apps are now available in every business workspace, linking those records to the people, agents, workflows and external AI clients that need to use them.
Four examples for small and medium businesses
Sales CRM. The team logs deals in the app, giving everyone one pipeline record to work from. An agent can read incoming emails and update the matching deal, while a weekly workflow sends a pipeline summary to the team.
Time off. Employees submit leave requests in a Time off app, and managers approve them through the roles assigned to them. A workflow can notify the team calendar after approval, keeping the request and its follow-up tied to the same record.
Inventory. Stock levels and movements live in an Inventory app. An agent can answer a question such as "How many units of X do we have?" from chat, while a scheduled workflow flags items below a chosen threshold; where WhatsApp is connected through a configured workflow, a message can trigger an app lookup.
Operations tasks. A team shares a task app, and an agent can turn meeting notes into tasks with owners and due dates. A connected ChatGPT or Claude client can query authorized records through the workspace's Botchi MCP connection, subject to the connected member's permissions.
These are examples of ways to configure an app, agent and workflow together, not prebuilt customer results. The templates include Task manager, CRM, Time off and Inventory, and a team can also start from a blank app.
One set of records, used in four ways
A Botchi App combines an interface with a database for information such as deals, tasks, leave requests or stock. Members work with the records through the app. Agents use the app's operations as tools, workflows call its functions as steps, and external AI clients reach the app through the workspace's Botchi MCP connection. Each route reaches the same records under its own access rules, rather than requiring a separate copy for every Botchi surface.
That is the difference between adding another isolated tool and building an app inside the workspace where the team's AI work already happens. A published app can be opened from My apps in web chat or from the dashboard. The app runs on the web; mobile interfaces, public hosting and standalone sign-in are not available.
Build, check and publish
To begin, describe the app in builder chat. Start from a blank app or choose a template, then describe the records, screens and actions the team needs. The builder writes the app, checks it and updates a live preview with sample data so the team can try its key actions before publishing.
Publishing makes the checked version available to authorized members and agents. Later changes stay in preview until they are published. History tracks releases and supports rollback to a compatible version; a rollback restores the app code while keeping its current records. When Botchi platform updates are available, one-click updating keeps the app's data, features and access in place.
Access follows roles and operations
Each app defines roles for its own work, such as Reader, Sales or Manager. Those app roles are assigned to business roles, never directly to individual people, so a member gets app access through the business role they hold. The workspace owner or editor can decide which agents receive app roles as well.
For agents, app operations become tools within the roles they have been given. Each tool can follow an Auto, Ask or Off policy. Workflows use the app functions included in their steps. External MCP clients follow the connected member's current permissions, and an agent request made on a member's behalf must be allowed for both the member and the agent.
Plans and continuity
Each published app has a monthly plan in one of three sizes, S, M or L, paid in Sparks from the workspace's shared pool. Every size supports unlimited users. Autoscale is optional, and a workspace can have up to five apps, including drafts and active apps.
Every published app is backed up hourly, with 30 days of restore points. The workspace owner can also export a zip containing the published source and the app data as of the last hourly backup. The export gives the owner a copy of both, but the source depends on Botchi's app kit and does not run outside Botchi as-is, so it should not be mistaken for a turnkey migration to another platform.
How to start
Open Apps → New app, then choose a blank app or one of the templates. Describe what the team needs in builder chat, review the checked preview and its sample data, and set app roles before publishing. For the complete steps, see the Botchi Apps documentation, including the guides to building an app, app access and roles, publishing and rollback and plans and limits.
The practical starting point is one record set the team already needs to share. Put its interface and data in an app, decide which roles can act on it, then connect only the agent and workflow steps that make that work easier to repeat.