Why your team still opens five tabs for one status question
Every Monday the project lead opens five tabs: Kanban board, performance reports, wiki, finance, team chat. A simple question—"how many overdue tasks in the next release?" or "what did we decide about the API?"—costs ten minutes of hunting, exports, and Slack pings. By the time the answer arrives, the standup has already moved on.
An AI project chatbot connected to the same PostgreSQL database as your PM tool can answer in seconds. The difference from raw ChatGPT is not "smarter prose." It is grounded answers from real tasks, wiki pages, and finance records—and FeatureAccess enforcement so a USER account never sees confidential tasks from another project.
WKFGo's chatbot service runs on port 4000 with intent classification, conversation context management, and wikiVectorSearch over the shared backend database. The floating ChatbotContainer widget in the authenticated app shell connects via REACT_APP_CHATBOT_URL. OpenAI and Gemini are optional in .env; without API keys, queries still run on local database logic.
Symptoms and hidden costs of scattered status
When status lives in people's heads instead of the system, the organization pays in ways that rarely appear on a budget line:
| Signal | Hidden cost |
|---|---|
| "Check the board" is the manager's default answer | Time spent exporting instead of deciding |
| Decisions never captured in wiki | Same questions every month |
| ChatGPT without live data invents numbers | Decisions with false confidence |
| Five tabs for one KPI | Status meetings instead of analysis |
| New hires ask the same onboarding questions | Senior ICs become human search engines |
The cumulative cost is not one slow query—it is hundreds of micro-delays per week across every squad. PMs become export operators. Engineers context-switch before they can start work. Leadership receives narrated optimism instead of measured facts.
A six-step framework for a useful PM chatbot (this week)
Step 1: List your top repeated questions
With the team, write ten questions asked three times a week: overdue tasks, individual load, budget status, release date, open blockers, pending approvals. Map each question to a data source—list_tasks, finance_summary, search_docs, get_project_report. Without this map, the bot stays generic and users stop trusting it after the third wrong answer.
Step 2: Test permissions before rollout
Test with USER and ADMIN accounts on the same question. The bot must not bypass JWT and FeatureAccess middleware. If a task belongs to a project the user cannot access, the answer is "no access"—not a leak. This is the same permission model as /dashboard and /reports; the chatbot is not a back door.
Step 3: Link answers to tasks or wiki
Answers without citations erode trust. "Based on task #123" or "wiki page auth-decision"—one click to verify. That is what separates a PM chatbot from a generic one. Teach the team to click through once a week until the habit of verification becomes automatic.
Step 4: Teach MCP for advanced workflows
For dev teams, the MCP server (user-wkfgo) exposes my_queue, my_day, smart_search, get_project_report, and list_tasks from Cursor or Claude Desktop—same data, no tab sprawl. The chatbot serves everyone in the browser; MCP serves deep synthesis sessions at the desk. Both hit the same backend.
Step 5: Collect wrong answers and move patterns to wiki
Every bad reply is a missing intent or data gap. Monthly, add patterns to wiki FAQ or runbooks—the bot improves when organizational knowledge is written down. If a finance answer was wrong, audit whether finance_summary permissions were correct or the query parsed incorrectly.
Step 6: Pair chatbot with async visibility
When ICs post daily summaries from my_day and PMs query the chatbot before short syncs, status meetings shrink to exceptions only. The chatbot is not a replacement for board hygiene—it accelerates access to data the board should already contain.
Anti-patterns that kill chatbot trust
- Chatbot with no DB connection—same hallucination risk as generic AI; numbers will be invented.
- Giving everyone ADMIN "for speed"—confidential finance and cross-project leaks become inevitable.
- Replacing formal reports entirely—chat complements audit trails; it does not replace
/reportsor decision logs. - Sensitive finance questions with no logging—use
finance_summarywith permissions, not pasted exports. - "Trust AI" without source links—one wrong burn-rate number in a board meeting destroys months of adoption.
- Rolling out before wiki is populated—the bot cannot cite decisions that were never written down.
WKFGo chatbot and MCP: honest feature map
Chatbot service (port 4000): floating ChatbotContainer, intentClassifier, contextManager, wikiVectorSearch, financeReport, optional OpenAI/Gemini via .env.
MCP tools for the same data: list_tasks, smart_search, finance_summary, get_project_report, my_day, search_docs, list_pending_approvals.
Web UI alternatives: /dashboard Kanban, /reports performance summaries, /my-tasks personal assignments, /wiki and /knowledge-hub for documented decisions.
Permissions: every path respects FeatureAccess—the chatbot, MCP, and web app share one authorization model.
FAQ — AI project chatbot
Does it replace the project manager?
No. It speeds status and search; prioritization, stakeholder negotiation, and scope tradeoffs stay human.
Does data go to OpenAI?
Depends on configuration—OpenAI and Gemini are optional. Align data policy with security before rollout. Local DB logic works without external API keys.
UI chatbot vs MCP—which should we use?
UI for everyone in the browser; MCP for dev and leadership in Cursor or Claude Desktop. Same backend, same permissions, different interface.
Does it handle Persian wiki content?
Yes—embeddings and search work on FA/EN project content. WKFGo supports bilingual UI with Jalali calendar utilities.
Start today
Define your top ten repeated questions. Test permissions with a USER account. Populate wiki with decisions your team keeps re-asking. Then open the chatbot and ask one real question—with a citation you can verify.