An automation trigger is the event that causes an automation to run. Choosing the right one determines whether a process feels automatic or merely faster to operate manually. Why the trigger matters more than the action The action is usually obvious. The trigger decides whether anyone still has to remember
A service desk is the structured way an organization receives, tracks, and resolves requests. Its defining feature is state: every request has a status, an owner, and a measurable time. Service desk versus shared inbox A mailbox has no concept of ownership or state, which is what a service desk
App versioning keeps a history of an internal app's states, lets you pin which one users see, and allows any earlier version to be restored. Changing a live tool stops being a risk. The problem it solves Without versioning, every edit is immediately visible to everyone using the
A conditional field appears or disappears depending on what was answered elsewhere on the record. The person filling the form sees only what applies to their case. What it fixes Conditionals solve two problems at once: completion rates and data quality. * Long forms that people abandon partway * Fields left blank
A webhook sends a notification to another system the moment something happens. Where an API call means you ask for information, a webhook means you are told. Why the direction matters The two approaches suit opposite situations, and using the wrong one produces either delay or wasted requests. * Polling an
A relational database stores each piece of information once and connects records to each other rather than copying values between them. In operations, that is the difference between data that stays consistent and data that drifts. What copying costs you Duplication rarely announces itself as a problem. It appears as
A cost center is a unit of the company against which expenses are allocated — a department, a project, or a site. It answers whose budget a given cost belongs to. Why it should be a record, not a text field Typing a cost centre name onto each expense looks simpler
An SLA in operations is a commitment about time — how long something should take. Measuring it properly means recording time per stage rather than only from start to finish. Why total time is not enough Understanding what is SLA in operations means seeing why total time falls short: a commitment
A Kanban board displays records as cards in columns, where each column is a phase of a process. It answers one question well: where is each item right now. When a board is the right view Boards suit work that progresses. They suit reference data badly. * Good fit — requests, tickets,
OCR — optical character recognition, often called document reading — extracts data from an uploaded file or image and turns it into structured fields. An invoice becomes a record rather than an attachment. Where it earns its place The value is concentrated in processes where documents arrive constantly and their contents have
An AI agent for business does more than answer. It reads incoming requests, classifies them, fills fields, moves records through phases, and closes them when they are resolved — within boundaries you define. Agent versus chatbot The distinction is what happens after the reply. * A chatbot answers a question and stops
A no-code platform lets you build working software by configuring it visually rather than writing code. The data structure, the interface, the rules, and the integrations are all defined through a builder rather than a programming language. What it replaces No-code sits between two options that both fail