SupportBot
Customer supportKnowledge-grounded answers, citations, and a clear path to human help.
Private betaOne platform for a governed AI workforce.
Give specialized AI workers a shared foundation: approved knowledge, permissions, organizational memory, workflows, and human oversight. SupportBot is the first commercial step; the broader workforce is being developed from that foundation.
AI workers
SupportBotWorkspaceBotIntake Agent
AIWF platform core
KnowledgeShared MemoryPermissionsWorkflowsHuman OversightAnalytics
Business systems and context
Documents · Websites · Databases · Conversations · Internal tools · APIs
Platform direction · Worker availability and integrations vary by scope.
Specialized workers. Shared business context.
Each worker has a distinct role, but the same platform governs knowledge boundaries, permissions, memory, workflows, and human review.
WorkspaceBot
Internal operationsA planned assistant for employees, internal knowledge, and operational workflows.
In developmentIntake Agent
Client onboardingA planned worker for turning client information into a structured, reviewable brief.
In developmentIn development
AIWF Desktop
A dedicated platform workspace is part of the product direction. Access and supported workflows will be confirmed separately.
Discuss a pilot →What every worker inherits.
These are the platform building blocks. SupportBot pilots use an agreed subset today; automatic sharing and orchestration across future workers remain under development.
Knowledge
Approved company information defines what each worker can use.
Shared Memory
Approved outcomes can strengthen business context without treating every conversation as trusted memory.
Permissions
Role-aware access limits the information and actions available to each worker.
Workflows
Workers can move requests through defined business processes rather than operating as isolated chats.
Human Oversight
Important, uncertain, or sensitive decisions stop for review.
Analytics & history
Teams can inspect activity, escalations, approvals, and operational patterns.
What is ready, and what comes next.
A platform vision should come with a clear view of current availability. A pilot confirms the features and integrations your business will actually use.
Knowledge-driven support
SupportBot’s existing workflow includes knowledge ingestion, retrieval, citations, verification, conversation review, and ticket escalation. Configuration and quality are evaluated within each pilot.
SupportBot pilots
One defined support workflow, approved sources, and a named escalation owner. Access, limits, and commercial scope are agreed before onboarding.
Additional AI workers
WorkspaceBot, Intake Agent, and broader cross-worker handoffs are being developed. Product pages describe direction rather than generally available services.
Private deployments
HomeHub infrastructure is part of the longer-term deployment model. Self-hosted, local, or private installations are not a standard offering today.
The HomeHub direction.
HomeHub describes the infrastructure and administration layer in the AIWF Company Blueprint. It is distinct from the customer-facing AI workers.
HomeHub Console
A platform administration surface for managing the AIWF environment. Current SupportBot teams work through the product’s business console; broader HomeHub administration is not sold as a separate product here.
HomeHub OS
The longer-term infrastructure direction for private and local deployments. Availability, infrastructure requirements, and operational responsibilities need separate validation.
Start with one AI worker. Build from there.
Deploy SupportBot around one customer-support workflow, then expand the same knowledge, memory, permissions, and oversight system across additional AI workers.