Multi-brand Intercom rollout for fan operations
One Intercom workspace had to route fan conversations across a primary team, two affiliates, retail, and Guest Experience without collapsing brand presentation or sales-team ownership. Delivered as an Intercom partner engagement, the implementation used per-brand Messenger configuration, custom and Resolution Bot flows, routing rules, tags, staging, and rep enablement ahead of a draft-day launch.
Executive Summary
Context
The franchise operated several public domains and distinct sales or service teams, while ticketing, retail, and fan questions arrived through the same chat platform. The build segmented Intercom by brand and configured Ohio IP targeting, round-robin routing, and a Resolution Bot "call me" flow. The core rollout launched on June 23, 2022, on the planned pre-draft schedule. Later work used remaining partner-funded hours for a Salesforce installation and a BigCommerce-era retail self-service bot; the Salesforce installation was confirmed working, while the retail flows were completed pending final approval.
What We Built
Intercom was configured around per-brand sales teams, custom and Resolution Bots, per-domain branding, tagging, a staging environment, and rep invitation and training. Ohio IP people segments directed a defined audience into the appropriate routing logic, while round-robin assignment and the live "call me" flow gave sales representatives an operational path into chat. Salesforce served as the CRM destination for chat-sourced leads in follow-on work. After construction closed the physical retail location, the retail bot shifted toward BigCommerce self-service content drawn from an FAQ document.
Tech Stack
- Intercom, Salesforce, BigCommerce, SeatGeek
This work fits teams that need one Intercom workspace to preserve separate domain presentation, routing ownership, and bot behavior across related consumer-facing operations. It is not evidence for a full customer-support deployment, an approved production launch of the retail bot, or a documented Salesforce sync architecture: the record does not specify the integration's objects, fields, mappings, or downstream reporting.
The Challenge
Fan conversations crossed four brand domains, but each brand required its own presentation, bot behavior, and sales-team ownership. The original requirements also called for a staging environment, reporting tags, Ohio IP geo-targeting, and rep training before launch. A roster change shifted ticket sales toward brokers after the business requirements were drafted, and construction closure of the physical retail location redirected the retail workstream toward eCommerce self-service.
Our Approach
The workspace was segmented before launch rather than treating every inbound chat as one queue. Per-brand bots and branding separated public entry points, while people segments, tags, and routing rules controlled qualification and handoff. The team validated the configuration in staging, confirmed round-robin routing, and tested the Resolution Bot's "call me" path live on launch day. When retail requirements changed, FAQ content was converted into self-service flows covering shop hours, in-venue stand locations, and guidance to shop online. Remaining scope hours also supported a Salesforce installation for chat-sourced lead and fan data.
Impact
Separate brand routing in one Intercom workspace
Per-brand bots, per-domain branding, and separate sales-team requirements were configured within one Intercom workspace, keeping routing ownership distinct across the franchise's consumer-facing operations.
Live sales-rep response observed at launch
Launch-day testing on June 23 showed a sales representative entering a chat immediately. The rollout launched on the planned pre-draft schedule after staging, routing, and bot-flow preparation.
Salesforce installation confirmed working
Salesforce was the CRM of record and intended destination for chat-sourced leads. Follow-on work used remaining hours from the original partner-funded scope, and the available email record confirms that the installation was completed and working.
Retail self-service flows completed for approval
Construction closure of the physical retail location moved the retail workstream toward BigCommerce self-service. Intercom confirmed that the Resolution Bot flows were completed on November 7, 2022 and awaiting final approval; the available record does not confirm approval or production launch.
Brand separation required more than different bot copy. The implementation paired per-domain branding with per-brand teams and bot requirements, so the Messenger entry point, conversation path, and ownership model could remain distinct inside one workspace.
Ohio geo-segments, round-robin routing, tags, and the "call me" flow were configured before launch. Staging and launch-day live testing gave the delivery team a way to observe whether the intended handoff reached an available sales representative rather than relying on configuration alone.
The retail bot was not a static extension of the original scope. When construction closed the physical location, the content model changed to eCommerce self-service. FAQ-driven flows were iterated around shop hours, in-venue stand locations, and online-shopping guidance.
The Salesforce installation is documented as completed and working, but the available record does not describe its object model, field mappings, sync direction, or reporting behavior. Those details are therefore not represented as part of this Blueprint's technical design.
Intercom workspace: core chat platform, segmented into four unnamed brand-domain entry points with per-domain Messenger branding, custom bots, Resolution Bots, tags, Ohio IP people segments, routing rules, round-robin assignment, staging, and separate sales or service teams. Salesforce: CRM destination in follow-on work for chat-sourced leads and fan data; the record does not specify objects, fields, mappings, or sync direction. BigCommerce: retail self-service context after physical-store closure; FAQ content informed Resolution Bot flows, but no system-to-system data flow is documented. SeatGeek: named platform, but its role and flows are not documented. Each brand-domain entry point sends fan chats to Intercom when a visitor opens Messenger. Intercom routes tagged and segmented conversations to the appropriate team through round-robin assignment; staging validation and launch-day live testing gate the handoff. FAQ content moves into Intercom bot flows when retail requirements change. Place the four entry points on the left, Intercom centrally, teams on the right, Salesforce and BigCommerce below, and SeatGeek isolated with no edges.
FAQ
The documented design used one Intercom workspace segmented by brand, with per-domain branding, per-brand bot requirements, separate sales teams, tags, people segments, and routing rules. The record confirms the implementation requirements and launch preparation, but it does not provide a complete configuration export.
No production launch is confirmed in the available record. Intercom confirmed on November 7, 2022 that the retail Resolution Bot flows were complete and awaiting final approval. A final project-sync meeting was logged on November 10, but no meeting notes or written approval were retained.
