Menzzo Chatbot UI

Purpose

menzzo-chatbot-ui is the customer-facing chatbot frontend. It wraps the chatbot experience, upload flows, and Dify-backed conversation UX for Menzzo support journeys.

Stack

• Next.js 15, React, and TypeScript.
• Tailwind CSS.
• Cloudflare/OpenNext deployment model.
• Dify-facing frontend integration.

Connected Projects

• Menzzo Chatbot Backend provides business APIs and protected workflows.
• Dify handles conversation orchestration.
• Media upload tooling and SAV workflows support customer service outcomes.
• Chatbot logs provide analytics and diagnostics.

Local Docs Submodule

When this repo consumes global docs, use:

cd docs
npm ci
npm start
npm run build

To Expand

• Cloudflare deployment notes.
• Dify env var map.
• Upload flow contract.
• Frontend troubleshooting checklist.

Dependencies

The documented dependencies are Dify, the Chatbot backend, logs, and media upload support. The exact behavior depends on the request branch; not every chat turn should be assumed to invoke the business backend.

Setup

Application setup is not established by this page. Follow the owning repository's README and setup instructions, and request the approved local access or environment you need. The shared documentation submodule and docs-site commands are described in the repository map and local development guide; they do not start this application.

Flows

Chatbot to business API distinguishes the Dify conversation path from conditional business-API work. Support escalations are covered separately in Support and refunds.

Diagnosis

Compare the UI request and Dify result before looking for a backend call. A backend cache/API request may be conditional; the flow page identifies the reviewed condition and source references when available. UI deployment and upload runbooks are missing here.

Evidence and gaps

The page documents the frontend stack and system relationships; environment configuration, upload contract, deployment steps, and branch-specific diagnostics need source evidence.

Next evidence to add: source commit and file references for the owned boundary, then repository-specific setup and the relevant operations procedure. See the documentation coverage matrix for the system-wide gap record.