Front Door Agent
What the marketing tech support agent has to hold to take in work, answer questions, route requests and report back, shown at its optimal state.
Take in a request
Answer the question
Check completeness
Validate against QA findings
Route and prioritize
Handle the simple ones
Report status back
Capabilities read context, they do not hold it.
Shared context layer
Change cadence
Agent memory
- This request — What was asked, what was missing, what was answered, what changed.
Hive memory
- Promoted routes, rules, and self-serve answers — Corrected routes and answers promoted into rules, recurring asks turned into self-serve, decline precedents, turnaround actuals.
Operational state
- The queues, the page, and who has capacity — The Workfront queue, the web defect queue and the QA agent's open findings, the page as it stands, the Hub record, who has capacity this week.
Organizational knowledge
- Request types, routing rules, and the approval matrix — Request types and required fields, routing rules and the approval matrix, how the site is built (a CMS content change versus a code change), the standards it answers from.
Ontology
- One model shared across the agent fleet — Request types, owners and roles, priorities and statuses, page and entity vocabulary: one model shared with the other three agents.
Resolved across systems of record, never copied into a new queue: many doors, one record. Classification per #5706-0567.
Systems of record and action
- WorkfrontSensitive
- Microsoft OutlookSensitive
- Microsoft FormsSensitive
- Azure DevOpsCompany
- GitHubCompany
- Marketing Data HubCompany
- Builder.ioPublic
Governance
Tier: HighA2 — Human-reviewed, then published or sent broadly- Why this tier
- High tier: it reads Workfront and email, both Sensitive. Named approver per use, one specific mitigation.
- The ladder
- Rungs: answer and check, then validate a reported issue against what the QA agent already found, then suggest a route, then route, then act on a defined simple set with approval.
- Never
- Patient details arrive through requests: detect and hold, never store or forward.
- Audit
- Full audit. One-step reversal. A named owner of the layer.
Governed promotion: a weekly review accepts candidate rules and answers, each owned.
Built by increment
One request type and one question set first.
Portable by construction
Vocabulary, rules and answers as plain versioned files, shared by all four agents.
Living
Every override and every corrected answer is a candidate rule.