Everything you need for the initial setup of SupportFlowAI — from Ollama through .NET 10 to the first admin account.
SupportFlowAI runs as a .NET 10 web application (Razor Pages + Minimal API) and requires a
locally running Ollama
service at http://localhost:11434 — the only "AI" dependency, running fully
offline on your own machine. The data itself lives in a local SQLite database
(data/supportflowai.db).
IIS deployment supported: dotnet publish automatically
produces a matching web.config for in-process hosting via the ASP.NET Core
Module V2 — the three background services then run in the same w3wp.exe
process as the web UI.
During initial setup at /Setup, alongside the first administrator account, you
also choose the hardware mode — it determines which Ollama model tags are used for
embedding and text generation:
all-minilm, text generation
phi3.5:3.8b-mini-instruct-q4_0 — lean enough for a normal server without a
dedicated GPU.bge-m3, text generation
llama3.1:8b-instruct-q4_K_M — higher answer quality when a GPU is available.
Before the first launch, the chosen models must be downloaded once via ollama pull,
e.g. ollama pull phi3.5:3.8b-mini-instruct-q4_0 and
ollama pull all-minilm for CPU mode.
Model choice can be changed later: The choice is stored in
data/model-settings.json and becomes effective without restarting the
application via IOptionsMonitor<OllamaOptions> — so switching between CPU
and GPU mode later is always possible.
dotnet run --project src/SupportFlowAI.Api
or the published IIS site — the browser automatically opens to /Setup as long
as no user has been created yet./Setup is permanently locked./Login with the account you just
created./Admin/MailAccounts — see chapter 3 of the tutorial
series.New accounts always start inactive: a freshly created email account is always saved inactive — only after cleaning patterns, a test import, and checking the knowledge base do you deliberately switch it to "Active".
The global confidence thresholds live in data/retrieval-settings.json —
default HighConfidenceThreshold 0.85 (required for full automation) and
MediumConfidenceThreshold 0.60. There is deliberately no admin UI for this; the
file is edited directly and reloaded automatically by the application.
The account created during setup automatically receives the
SystemAdministrator role — the only role with full access including
full-automation approval. Additional users with more restricted roles (AccountManager,
Reviewer, Auditor) are created afterwards under /Admin/Users.