YAA\IF
Chat & collaboration
Microsoft Teams, Slack, and Google Chat, plus web chat and embedded widgets inside your own internal applications. The tools your people already use.
Channels
Where work comes in
Same governance, same audit, same approval posture, regardless of how the request arrived. Channels are abstracted behind a common ingress contract, so adding a new one is a configuration change rather than a re-platforming exercise.
Email & ticket queues
Shared mailboxes, helpdesk inboxes, and service management queues (ITSM, CRM cases) trigger workflows automatically, under the same policy and approval controls. The original message is preserved in the audit trail.
Voice & telephony
Contact center and IVR integration for agent-assisted call handling and post-call automation. The call transcript becomes structured input to the same workflows every other channel feeds.
APIs & webhooks
Programmatic invocation from your existing applications, middleware, and partner systems. Standard REST and webhook patterns, authenticated through your IdP.
Event streams
Kafka, AWS EventBridge, Azure Service Bus, MQ, and webhook firehoses. Always-on triggers feed the Ambient Agent pattern, catching events before they become escalations.
Schedules & timers
Cron expressions, business calendars, and SLA timers for recurring governed work, end-of-period reconciliations, and proactive checks that run on their own.
Plus
MCP Hosts: bring YAAIF into the AI clients your people already use
YAAIF exposes its governed skills and tools through the open Model Context Protocol (MCP). External AI clients can invoke YAAIF workflows directly, under the same approval gates, policy enforcement, and audit trail as every other channel.
Out of the box
Claude Desktop
One-click connect via standards-based OAuth (PKCE). Active sessions are tracked per user, and admins can disable a host with a single switch in the Manage Agents console.
Out of the box
ChatGPT desktop app
Same MCP host flow as Claude Desktop. Matching session controls, audit events, and approval gates, so users keep their preferred client without losing governance.
Open protocol
Any MCP-compatible client
Custom internal copilots, IDE plugins, and partner clients connect through the same protocol. No bespoke integration work per host.
The benefit: power users keep their preferred AI client. The platform keeps governance, approvals, and audit.
The channel is configurable. Governance is not. The same policy gates, approvals, and audit trail apply to every request: a chat message in Teams, an inbound email, a partner webhook, an overnight Kafka event, or a user typing into Claude Desktop.
More on the platform
Continue exploring how YAAIF runs
Patterns
Chat, Desktop, and Ambient agents under one governance.
How it works
The five-layer architecture every request flows through.
Trust
The control posture that holds up to internal audit and regulators.
Next step
Connect a channel to the workflow that matters this quarter
A 30-minute briefing maps the right inbound channel (or MCP host) onto your first pilot workflow, with identity and approval gates configured.