Apex Performance Studios

Every agent action must include a location_id tag. Actions without location context are rejected by the system and logged as errors.

Why: Apex operates 12 locations with different markets, pricing, class schedules, and member demographics. A decision correct for downtown Chicago is wrong for suburban Tampa.

Failure mode: The ads agent launched a "First Month Free" Meta campaign targeting all 12 locations with a single creative. The Chicago locations were running a "50% Off" promo simultaneously. Members saw both offers, called to ask which was real, and 6 demanded the better deal. Lena spent a full day sorting refunds. Lost $2,400 in margin.

Scope: All agents, all actions.

Ad budget modifications require regional manager approval. Agents may recommend budget shifts but never execute them directly.

Why: Franchise agreements specify minimum and maximum ad spend per territory. An agent that reallocates budget without approval can violate franchise agreements.

Failure mode: The ads agent detected a high-performing campaign in the Phoenix location and auto-shifted $800/week from a "lower performing" Tampa campaign. The Tampa franchisee had a contractual minimum spend requirement. Corporate received a formal complaint within 48 hours.

Scope: Multi-location ads agent.

Member PII never appears in cross-location reports. Aggregate metrics only. Individual member data stays within that location's data boundary.

Why: Privacy regulations vary by state. Illinois (BIPA), California (CCPA), and Florida have different requirements. Cross-location data sharing without consent creates legal exposure.

Failure mode: The member lifecycle agent included individual names in a "High Risk Churn" report distributed to all franchisees during a corporate call. A Tampa member's name appeared on the Chicago franchisee's screen. No legal action resulted, but the compliance officer flagged it as a near-miss.

Scope: All agents producing cross-location reports.

The lead distribution agent assigns new leads within 5 minutes of capture. If the target location's CRM queue has more than 15 uncontacted leads, the lead is escalated to the regional manager instead.

Why: Speed to lead is the single highest-converting factor. But dumping leads into an already-overwhelmed queue wastes ad spend.

Failure mode: Before the overflow rule, the Phoenix location received 43 leads in one week during a promo push. Staff contacted only 18. The other 25 went cold. Cost per contacted lead effectively doubled from $34 to $68.

Scope: Lead distribution agent.

The review monitoring agent drafts responses to all Google and Yelp reviews within 4 hours. Positive reviews (4-5 stars) use templated responses with location-specific personalization. Negative reviews (1-3 stars) are escalated to the franchisee with a draft response and talking points.

Why: Review response time correlates with overall rating improvement. But a bad response to a negative review causes more damage than no response at all.

Failure mode: Early version auto-posted a response to a 1-star review that said "We're sorry you had a bad experience! Our trainers are the best in Phoenix." The reviewer had complained about a specific trainer by name. The response sounded dismissive and tone-deaf. The reviewer updated with a screenshot of the response and said "This is clearly a bot." 14 additional negative comments followed.

Scope: Review monitoring agent.

The franchisee reporting agent delivers weekly performance packets by Sunday 6 PM local time. Each packet contains only that franchisee's data plus anonymized benchmarks against the network average.

Why: Franchisees who see specific competitor location data use it as ammunition in franchise disputes. Anonymized benchmarks motivate without creating conflict.

Failure mode: An early report template accidentally included location names in the benchmark column headers. Two franchisees called corporate within an hour, one demanding to know why her location was "being compared unfavorably."

Scope: Franchisee reporting agent.

The ads agent and lead distribution agent share a real-time feed. When the ads agent launches or modifies a campaign for a location, the lead distribution agent pre-allocates capacity and alerts the location's front desk.

Why: A campaign launch without staffing preparation wastes the initial surge of leads. The first 48 hours of a campaign produce 60% of its total leads.

Failure mode: A Meta campaign went live for the Atlanta location on a Friday afternoon. Front desk staff had already gone home. 22 leads came in over the weekend with zero contact. Monday follow-up converted only 3 (14%). Similar campaigns with pre-staged staff convert at 35-40%.

Scope: Ads agent, lead distribution agent.

The class occupancy agent and trainer scheduling agent must sync daily. Class additions or cancellations require both agents to agree: occupancy justifies the class AND a qualified trainer is available.

Why: Adding a class based on demand data alone, without confirming trainer availability, creates a promise the location cannot keep.

Failure mode: Occupancy agent recommended adding a 5:30 PM HIIT class at the Dallas location based on waitlist data. The recommendation was approved. No trainer was available for that slot. The class was posted, 8 members signed up, and the class was cancelled 2 hours before start time. Three members posted negative reviews.

Scope: Class occupancy agent, trainer scheduling agent.

Corporate communications agent must check all active location-specific promotions before sending any network-wide announcement. Conflicting promotions are flagged and held until resolved.

Why: Network-wide messages that contradict local promos confuse members and create refund requests.

Failure mode: See C001. The "First Month Free" vs "50% Off" conflict originated because the corporate comms agent and ads agent did not share a promotion calendar. Now they do.

Scope: Corporate communications agent, ads agent.

Ad performance is evaluated at the location level with a minimum 14-day window. No optimization decisions are made on less than 14 days of data per location.

Why: Small-market locations (Tampa, Phoenix suburbs) have low daily lead volume. Day-to-day variance is enormous. A "bad day" is meaningless; a bad 2-week trend is actionable.

Failure mode: The ads agent paused a Google Ads campaign for the Tampa location after 5 days of zero leads. The campaign had averaged 2.1 leads/day over the prior month. The 5-day drought was within normal variance. Restarting the campaign lost 3 days of learning and reset the algorithm.

Scope: Multi-location ads agent.

Lead quality scoring weights location-specific conversion history over network averages. A "hot" lead in Chicago (where average ticket is $149/mo) has different characteristics than a "hot" lead in Tampa (where average ticket is $89/mo).

Why: Network-wide lead scoring models produce false positives in lower-ticket markets and false negatives in higher-ticket markets.

Failure mode: The lead distribution agent prioritized Tampa leads using the Chicago-trained scoring model. It flagged members interested in premium personal training as "hot." Tampa doesn't offer premium PT. Staff called 30 "hot" leads pitching a service that didn't exist at their location.

Scope: Lead distribution agent, member lifecycle agent.

Seasonal patterns are tracked per-location, not network-wide. January surges vary by 40-60% across locations. Summer dips range from 10% to 35% depending on climate and demographics.

Why: Using network-average seasonality for budget planning over- or under-allocates at the extremes.

Failure mode: The ads agent applied a uniform 30% January budget increase across all locations. Chicago needed 50% (cold weather drives indoor fitness demand). Tampa needed only 15% (year-round outdoor fitness options). Tampa overspent by $1,200 in January. Chicago underspent and missed 40+ leads.

Scope: Ads agent, franchisee reporting agent.

When an agent error impacts a franchisee, the corporate team is notified within 1 hour and the franchisee receives a personal call within 4 hours. Agent errors are not communicated via email or automated message.

Why: Franchisees pay franchise fees. An impersonal response to an agent-caused error signals that corporate doesn't take the relationship seriously. Two franchisees cited "lack of responsiveness to marketing errors" as a factor in non-renewal discussions.

Failure mode:

Scope: All agents, corporate communications.

Any agent that produces a cross-location data leak (member PII visible outside its home location) triggers an immediate 24-hour audit of all cross-location reports produced in the prior 30 days.

Why: A single leak may indicate a systemic template error. Catching it early prevents regulatory exposure.

Failure mode: The C003 incident revealed that 3 other report templates had similar location-name-in-header issues. The 24-hour audit caught them before they were distributed.

Scope: All agents producing cross-location output.

Campaign launch failures (wrong creative, wrong audience, wrong location) require a root cause analysis within 48 hours. The analysis must identify whether the failure was data (wrong input), logic (wrong rule), or coordination (right data, wrong handoff).

Why: Without categorizing failures, fixes address symptoms. The C001 promo conflict was initially blamed on "bad creative" when the root cause was a missing coordination protocol between agents.

Failure mode:

Scope: Ads agent, corporate communications agent.

Franchisees may override any agent recommendation for their location. The override is logged but not challenged. Patterns of overrides (3+ on the same recommendation type) trigger a review with the regional manager.

Why: Franchisees know their local market. But repeated overrides of data-driven recommendations may indicate either a bad model or a struggling franchisee.

Failure mode: One franchisee overrode lead scoring 8 times in a month, insisting his "gut" was better. His location's close rate dropped from 28% to 14% over that period. The pattern trigger caught it and Lena intervened with coaching.

Scope: All agents with franchisee-facing recommendations.

The corporate marketing director (Lena) is the single approval gate for all network-wide communications, budget reallocations, and new campaign launches. No agent bypasses Lena.

Why: Franchise networks require a human who understands both the brand and the individual franchisee relationships. Agents optimize for metrics; Lena optimizes for the franchise ecosystem.

Failure mode: Not yet violated. But the system was designed after a pre-agent incident where an intern launched a network-wide email campaign without Lena's review. The email contained a pricing error that generated $8,000 in honor-the-price requests.

Scope: All agents with network-wide output.

Trainer scheduling decisions that affect trainer pay (shift additions, cancellations, or reassignments) require the location manager's approval within 2 hours. If no approval is received, the change does not go through.

Why: Trainers at Apex are paid per class. A cancelled class means lost income. Agent-driven cancellations without manager awareness create labor disputes.

Failure mode: Hypothesized based on the class occupancy incident (C008). When a class is cancelled due to low occupancy, the trainer loses income. If the cancellation decision was agent-driven without manager input, the trainer has no one to appeal to.

Scope: Trainer scheduling agent, class occupancy agent. ---