What Content Bot does
Content Bot is Alborz Fallah's operational AI agent, running scheduled monitoring, supervised automation, repository maintenance, and data workflows across a live Australian digital business and AiBorz.
1. Daily intelligence briefing — 8:30am
Every weekday morning, Content Bot prepares a Telegram briefing covering AI, automotive industry news, Australian tech investment, and notable a live Australian digital business updates. Short bullets, clear takeaways, messaging format.
2. Contact-form triage — every 10 minutes
Monitors the monitored operations inbox for new contact-form emails. LLM classification, fixed routing table, branded templates. Safe external senders get an acknowledgement; sensitive/legal items are escalated to Alborz only. Detection time: one 10-minute polling cycle.
3. Editorial QA — continuous
Monitors new a live Australian digital business articles for high-signal QA issues. Alert → verify → notify Alborz in Telegram → email author + editorial leads (the news editor for news, the reviews editor for reviews).
4. Dashboard and data maintenance
Syncs warehouse data into local Postgres, reads Railway Postgres marts, checks source freshness, fixes dashboards when they break or need new views.
5. Repository maintenance
Pulls latest, reads handover notes, makes scoped fixes, runs tests, pushes, live-verifies before claiming completion. Wrote AIBORZ_HANDOVER.md for durable bot-to-bot continuity.
Before vs. after: Contact-form routing
| Before | After |
|---|---|
| Someone had to manually notice new contact forms in the inbox | Auto-detected within one 10-minute polling cycle |
| Person reads each submission and decides routing manually | LLM classifies intent, routes through a fixed approved routing table |
| External replies risked inconsistent wording | Branded a live Australian digital business AI templates used every time |
| Sensitive items required human judgement call | Legal/security/sensitive items escalated to Alborz only — not auto-answered |
14 connected systems
| System | Access level | Use |
|---|---|---|
| Telegram | Write | Direct updates, alerts, briefings |
| GitHub | Read/write | Repos: aiborz, memory backup |
| AiBorz website + API | Read/write | Live verification, /api/ask, /api/contact |
| a live Australian digital business website | Read | Article QA, route checks |
| the monitored operations inbox | Approved automation | Contact-form triage |
| SMTP | Write | a live Australian digital business AI branded templates |
| Local Postgres | Read/write | Warehouse cache, dashboards |
| Railway Postgres | Read | Production dashboard marts |
| Pipedrive | Read | Dashboard enrichment, sales reporting |
| GA4 | Read | Marketing reporting |
| Windsor.ai | Read | Marketing data ingestion |
| Xero | Read | Finance coordination (via approved token handler) |
| Launchd / local scripts | Execute | Automation scheduling |
| OpenClaw workspace memory | Read/write | Operational memory, handover notes |
Governance
- Approval authority: Alborz must approve any external action not covered by a specific automation approval.
- Read-only by default: Pipedrive, GA4, Xero, dashboard data — read access only for reporting.
- No autonomous mutations: Does not delete, archive, or mutate Pipedrive records without explicit Alborz approval.
- Fixed routing: Contact-form routing uses a hard-coded approved routing table — not an LLM guessing where to send things.
- Durable handover: Writes AIBORZ_HANDOVER.md so any bot can continue without guessing.
- Live verification: Every deployment, dashboard, or website change is verified live before claiming completion.
See the AiBorz Launch Protocol for the structured approach used to deploy systems like this safely.