feat: Add Chatwoot Agent Bot prototype and FAQ knowledge base

- Created chatwoot-agent-bot/ with Node.js webhook server
- Bot detects intent (greeting, billing, technical, features, account)
- Auto-responds from FAQ knowledge base or escalates to human
- FAQ-KB.md: Living knowledge base that grows with customer questions
- CHATWOOT-SETUP.md: Complete deployment and configuration guide
- Supports Telegram notifications on escalation
- Bot runs on port 3001, ready for Chatwoot webhook integration
This commit is contained in:
2026-04-01 16:26:05 -04:00
parent 7ba19752de
commit 5319bcd30b
1074 changed files with 456376 additions and 0 deletions

27
memory/2026-03-31.md Normal file
View File

@@ -0,0 +1,27 @@
# 2026-03-31 - Tuesday
## Session Start
- First session for Forge (new workspace bootstrap)
- No prior memory files exist
- Chris runs a small SaaS business
- Expectation: proactive, autonomous operational support
## Actions Taken
- Read SOUL.md, USER.md, IDENTITY.md
- Confirmed identity: Forge - digital operations engine
- Workspace: /Users/claw/.openclaw/workspace
## TODOs
- [x] Check sales-lead agent cron.log status - working, generating leads
- [x] Check marketing-content agent cron.log status - ISSUE: no runs since Mar 26
- [x] Review self-improving files - no changes since Mar 20
- [x] Investigate marketing-content cron job error state - FIXED
## Issues Found
- Marketing-content daily cron job was MISSING from crontab (not just erroring)
- Last successful run: Mar 26 at 8:33 AM (4 files created)
- Script had session locking issues in mid-March, fixed Mar 22
- Removed broken cron job (971bb469-8fb7-43bb-954a-11de5a2575ff)
- Created new cron job (847f9e9b-98c2-47ff-82a2-d93236e67905) for 9 AM daily
- Sales-lead hourly cron working fine, monitor running every hour
- Sales-lead monitor confirmed working at 8:09 AM cron trigger - processing ROI calc submissions (7791 bytes response)