Business Brain
A shared knowledge and execution layer for an organization. It can include approved knowledge, tone, workflows, decision rules, guardrails, and escalation logic.
View full pagePlain-language definitions for the terms that show up most often in Business Brain-powered AI documentation.
A shared knowledge and execution layer for an organization. It can include approved knowledge, tone, workflows, decision rules, guardrails, and escalation logic.
View full pageA role-specific AI workflow designed to prepare a particular kind of output, such as sales follow-up, support notes, operations summaries, or training material.
View full pageRules that limit what an AI system should do without review. Guardrails can define allowed topics, restricted claims, escalation triggers, and approval requirements.
View full pageA workflow where humans review, approve, or take over when the output is sensitive, risky, external-facing, or unclear.
View full pageThe conditions that cause an AI workflow to pause, route, or flag an item for human attention.
View full pageThe use of AI to help capture, structure, summarize, and prepare records from conversations, meetings, calls, or operational work.
View full pageAn AI-generated response or draft that is based on approved source material rather than unsupported assumptions.
View full pageA tracking number issued for a resident or service request so it can be looked up, followed up on, or escalated later without re-explaining the original conversation.
View full pageA structured record of a donor, volunteer, beneficiary, sponsor, or partner conversation — capturing who was involved, their stated interests or needs, and what was discussed or committed to.
View full pageKeeping each participant's account of a conversation — such as a student's, a family's, and staff's — separate and clearly attributed, rather than merging them into a single flattened summary.
View full pageA marker on a record showing that a detail expected for that conversation type — such as a callback number or a stated need — was not captured, so it can be followed up on rather than assumed.
View full pageAn assessment of how well a conversation was handled — whether questions were answered, concerns addressed, and next steps made clear — separate from whether the underlying request was resolved.
View full pageA live conversation is the fastest way to map these terms onto your team's workflow.