Industry adoption, read from an operations desk

Latest

Live Nation Scales One Support Agent Across All Its Venues Instead of Building Many

Live Nation is rolling out Agentforce's Venue Agent to U.S. concert venues, following a BottleRock pilot called Melody that logged 37,000 fan interactions in 12 days. The system uses one agent instance plus Data Cloud to serve venue-specific answers, resolving 95% of questions without a human, escalating the rest via Slack.

What changes for operators — For a B2B company running support across multiple product lines, regions or client accounts, the operationally interesting detail isn't the fan-facing chatbot — it's the architecture choice. Live Nation didn't build a separate bot per venue; it built one agent and used a data layer to fetch the right context per interaction, then routed anything unresolved straight into the team's existing Slack workflow rather than a separate ticketing queue. That's a directly reusable pattern for a 10-200 person support or ops team serving several accounts or product SKUs: one agent, one knowledge routing layer, human escalation inside the tool the team already lives in. The 95% no-handoff rate is also a useful benchmark to hold internal deployments against before declaring an automation project done.

Adecco Puts Salesforce's AI Coworker Into 27,000 Employees' Daily Workflow

For a 10-200 person B2B company, the relevant detail isn't the scale — it's the task list Coworker takes over: finding priority prospects, drafting sales briefs, enriching prospect data, checking lead status across teams, and launching pre-screening or onboarding flows for candidates. Those are exactly the manual handoffs that eat rep and recruiter time in smaller teams running Salesforce or similar CRMs. Adecco's case shows this pattern working at enterprise scale under an unlimited Agentforce 360 agreement, but the underlying capability — one interface pulling context from CRM, candidate history and prior interactions — is what any Salesforce customer should be evaluating now, at whatever contract tier fits their size, rather than waiting for a bigger case study.

Salesforce Puts Agentforce to Work Inside TSA Traveler Support

For a 10-200 person B2B company running support on Salesforce or considering Agentforce, TSA's deployment is a useful proof point: a government agency with strict compliance requirements and enormous query volume trusted an AI agent to handle first-line traveler questions without a full support-desk rebuild. That suggests the platform can be layered onto existing case-management workflows rather than replacing them—relevant for ops leads weighing whether to pilot an agent for tier-1 tickets (order status, policy questions, account basics) before committing budget to a broader automation project. The practical takeaway is scope: Ace handles informational queries, not enforcement decisions, which mirrors the safe starting point most B2B teams should take—deflect repetitive questions first, keep judgment calls with humans.

Salesforce's Internal AI Agent Hit 70,000 Users — Here's What It Learned About Scaling Employee Support

A 10-200 person B2B company won't hit 70,000 users, but the mechanics Salesforce describes — starting narrow, routing low-confidence answers to a human, and tracking deflection rate before expanding scope — are exactly the sequence an ops lead should follow when standing up an internal agent for onboarding FAQs, IT tickets or expense policy questions. The lesson isn't the scale, it's the discipline: don't open the agent to every internal query on day one, instrument what it gets wrong, and only widen its remit once escalation paths are proven. Teams that skip that sequencing tend to erode employee trust in the tool within the first month, which is harder to rebuild than to prevent.

Salesforce: Companies Are Doubling Their AI Agent Deployments Year Over Year

If a vendor with Salesforce's customer base is seeing agent deployments double annually, the tooling, integration patterns and internal change-management playbooks have crossed from experimental to operational — which matters because a 10-200 person company doesn't have the luxury of a multi-year pilot phase. The practical takeaway is not "adopt AI agents because everyone else is," but that the barrier to entry (setup complexity, reliability, cost) has likely dropped enough that a lean ops or support team could reasonably pilot a narrow agentic workflow — say, first-line ticket triage or lead qualification — within a quarter rather than a year, provided the underlying process is already well-documented enough to automate.