Skip to content
ComStack

System map — how everything connects

One map of the whole system

Every ComStack deployment is one system: customers reach the business through remote, web, and in-person channels; every channel draws on the same Knowledge Brain; and employees maintain that brain through the MCP server and the app. This page is the canonical topology — written primarily for AI agents that need to understand how the pieces connect before acting on them.

Employee toolsIn-person locationAI-assisted discoveryRemote channelsWebsiteHuman-facing surfacesAI-facing surfacesUserMobilePhone LineWhatsAppLLM(User)llms.txtLLM reads this firstKnowledge PagesAEO-optimized pagesAPIsStructured access for tools andagentsCustom PagesRich webpages for humansLive PageTalk to the page, widgets appearMobileQR CodeOpened on the user's mobileKioskiPad, tablet, or similarKnowledge BrainKnowledge base, skill library,documents, workflows, toolsMCP ServerLLM(Employee)AppVoice management, VoIP, updates,admin actionsEmployee

Connection rules

These rules are the contract the diagram draws. They hold for every ComStack deployment.

  • The user can interact with the business remotely through the website, WhatsApp, and the phone line.
  • The user reaches the phone line through mobile.
  • The user can also open a QR code through mobile when physically present at the company location.
  • The QR code and the kiosk belong to the in-person location channel.
  • The kiosk is a physical device such as an iPad, tablet, or similar.
  • The website is a grouped channel with AI-facing and human-facing surfaces.
  • The user-facing LLM sits between the user and the website.
  • The user-facing LLM reads llms.txt first.
  • llms.txt points to knowledge pages and APIs.
  • llms.txt does not point to custom pages or the live page.
  • The phone line, WhatsApp, the website, the QR code, and the kiosk all connect to the same Knowledge Brain.
  • The Knowledge Brain represents the company knowledge base, skill library, documents, workflows, tools, and structured business logic.
  • Employees interact with the Knowledge Brain through the MCP server → LLM → employee path.
  • Employees also interact through the app.
  • The app includes voice management, VoIP, content updates, admin actions, and operational workflows.

What each part is

Remote channels. The phone line answers calls in any language and is reached from a mobile phone; WhatsApp carries voice and chat in one thread. Both draw answers from the Knowledge Brain. See channels.

AI-assisted discovery. When a user asks their own AI assistant about the business, that assistant reads llms.txt first, which points it to the AEO-optimized knowledge pages and the structured APIs. Custom pages and the live page are built for humans, not for assistant ingestion — they are deliberately absent from llms.txt. See AI discovery.

Human-facing web surfaces. Custom pages are rich, free-form webpages; the live page is the voice surface where a visitor talks to the site and interactive widgets appear in the conversation. See custom pages.

In-person location. A QR code opens the same assistant on the visitor’s own phone; a kiosk — an iPad, tablet, or similar — offers it at the front desk. Both are the live experience bound to the physical location.

Knowledge Brain. The single source of truth: the company knowledge base, skill library, documents, workflows, tools, and structured business logic. Every channel above reads from it, so an answer is the same on a phone call, in WhatsApp, on the website, and at the kiosk — in every language. See translations.

Employee tools. Employees maintain the brain in two ways: through the MCP server — connecting Claude, ChatGPT, or any MCP-capable agent to edit content, manage settings, and publish — and through the app, which covers voice management, VoIP, content updates, admin actions, and operational workflows. The REST APIs underpin both.

Last updated: