# The Hard Part of AI Agents for Marketing Platforms Isn’t the Model. It’s Everything Around It > Source: > Published: 2026-10-16 12:33:44+00:00 - When you put AI agents inside a product that serves many marketing clients, most of the work goes into integrations, tenant isolation, and human approval, not prompts. - We structure these systems in five layers: channels → agents with guardrails → approval queue → escalation routing → per-client data store. - Results from production builds: review response time cut from 18 hours to 4 minutes across 1,200 locations (6-week build), and 62% of first-touch tenant enquiries handled without a human (14-week build). ## The problem: agents that speak for someone else An internal chatbot answers your own team's questions. An agent inside an agency or marketing platform does something riskier: it writes review replies, ad variations, and lead messages **on behalf of your clients**, in public. That changes the engineering requirements: - **Many tenants.** Every client has its own brand voice, banned phrases, channels, and escalation rules. - **Public output.** A bad reply sits under a client's Google listing, not in a Slack thread. - **Mixed data sources.** Review sites, ad platforms, CRMs, property management systems, and inboxes, each with its own auth, limits, and quirks. ## Seven agent shapes, one pattern Across marketing products, we keep building the same seven shapes: | Agent | What it does | | Response | Drafts on-brand replies, escalates sensitive ones | | Qualification | Scores leads, answers first-touch questions | | Research | Gathers prospect context for sales | | Creative adaptation | Reshapes assets per placement | | Assembly | Builds a draft campaign from a brief | | Insight | Answers performance questions in plain language | | Orchestration | Decides which agent runs and when a human steps in | In code, the first six are mostly the same thing: a goal, a set of tools, and a policy for when to stop and ask a person. The seventh is the coordination layer. That's where [AI agent orchestration](https://intercode.com/services/ai-agent-orchestration) does most of its work: routing, shared state, and handoffs. ## The 5 layers 1. **Channel integrations.** Review platforms, ad networks, CRMs, PMS, email, SMS. 2. **Agent layer with guardrails.** Generation plus checks for tone, banned content, and confidence. 3. **Human approval queue.** Drafts waiting for a person. 4. **Escalation routing.** Sensitive cases go to the right human, fast. 5. **Client data store.** Per-tenant context, examples, and history. Layer 1 is usually the biggest share of the effort. Webhooks versus polling, rate limits, token refresh, and normalizing ten different "review" objects into one schema is where weeks go. If you're scoping a project, scope the [API and integration work](https://intercode.com/services/api-development) first. ### Per-tenant policy Every decision the agent makes should read from a tenant policy, never from hardcoded defaults. ### The approval gate Every draft goes through one routing function, so "publish, approve, or escalate" is a single, testable decision: Start every tenant with `autoPublish.enabled = false`. Turn it on per channel once the approval data shows humans rarely edit the drafts. ### Tenant isolation in retrieval The quickest way to lose a client is to quote another client's data in their reply. Scope every read by tenant at the data layer, not in the prompt: ## What this delivered - **Review management, 1,200 locations.** Response time went from 18 hours to 4 minutes. It was a 6-week build with a team of about two and a half people, and it paid for itself within 3 months. This ran on top of the[reputation management platform we had modernized](https://intercode.com/cases/modernizing-a-high-scale-reputation-management-platform) . - **Leasing assistant for apartment marketing.** It handles 62% of first-touch tenant enquiries without a human. It was a 14-week build with a team of five, multi-tenant, and integrated with property management systems. - **Acquisition engine for a multifamily marketing agency.** It cut manual prospect research by 73% and raised outbound capacity 3.2x without new sales hires. ## Trade-offs and gotchas - **Integrations dominate the estimate.** Count channels before you count agents. - **Brand voice fidelity has a cost.** You need per-tenant examples and an evaluation set for each voice, not one global prompt. - **Volume decides payback.** The review project worked because it replaced about 1,100 hours of monthly admin triage. Low-volume workflows may never pay back a custom build. - **Don't automate an unstable workflow.** If the manual process changes every month, fix it first. - **Decide on data and IP ownership up front.** That covers prompts, evaluation sets, logs, and any fine-tuning data. - **Pick the metric before the model.** Response time, enquiries handled, research hours saved. Without one, you can't tell if it works. ## How the delivery usually runs These projects take 6–14 weeks: 1. Discovery and feasibility 2. Architecture and data access 3. Build with guardrails 4. Validation and production ## Wrapping up The model is the easy part. What makes these agents safe to ship is the plumbing around them: integrations, per-tenant policy, an approval gate, escalation, and strict data isolation. *This article was drafted with AI assistance and reviewed by the InterCode team.*