Tools & integrations, read from an operations desk

Latest

Slack adds Frontline, a mobile workspace for non-desk staff

Slack has launched Slack Frontline, a lightweight mobile workspace for people who work away from a desk, such as retail, healthcare, factory and field staff. It bundles role-specific channels, Huddles with HQ, agents and automated workflows. It is available now as an add-on for Slack Enterprise+ customers.

What changes for operators — If you run operations at a company of 10-200 people with shift workers, technicians or store staff, the useful part is that handoffs, alerts and escalations can move out of group texts and into governed channels that agents and workflows can act on. The catch is the entry requirement: Frontline is an add-on to Slack Enterprise+, and the source gives no price. Check your current Slack plan and ask sales for a quote before planning around it. Nothing in the announcement shows how it performs outside the vendor's own scenarios, so a pilot with one site or one shift is a sensible first step.

Salesforce Packages Role-Specific AI Agents Into Agentforce

If your company already runs on Salesforce, this narrows the gap between what you'd have paid a consultancy to build (a lead-qualification agent, a service-ticket triage bot) and what now ships as a configurable module. That's worth an hour of evaluation before greenlighting a custom build on the same use case. But for the 10-200 person range, Agentforce's enterprise pricing tiers and CRM dependency mean most teams still get faster time-to-value from point automations wired directly into their existing stack — email, helpdesk, CPQ — rather than adopting a full Salesforce agent layer. The practical move is to treat this release as a benchmark: if a prebuilt Agentforce agent covers 80% of a workflow you're planning to automate, price it against a custom build; if it only covers the CRM-native slice, keep building outside Salesforce where your actual tools live.

Salesforce Gives AI Agents a Visual Interface Inside Slack

For a 10-200 person B2B company that already runs support tickets, deal approvals, or internal requests through Slack, this closes a real gap: today an AI agent posting in Slack can describe what it wants to do, but a human still has to jump into a separate CRM or ticketing tool to actually approve or execute it. If Slack Surfaces works as described, an agent can surface a customer record with an 'approve refund' or 'escalate to human' button right in the channel, cutting a step out of the loop and reducing the number of tools a support or ops rep has to touch per ticket. The near-term catch is that this only pays off if the underlying agent (Agentforce or a connected third-party agent) is already wired into the systems of record the buttons act on — teams without that integration in place gain a nicer chat window, not a faster process.

Slack Adds Built-In AI Coding Agent for In-Channel Requests

Most 10-200 person B2B companies don't have engineers sitting in every support or ops thread — a broken webhook, a misfiring Zapier step, or a report that needs one more filter usually waits in a backlog. Slack Code puts a coding agent where the request already happens: the Slack channel where support flagged the bug or ops asked for a tweak. If it works as described, a support lead can type the problem in plain language, get a proposed fix or script back in the same thread, and route it to a human reviewer before merging — no separate ticket, no context lost translating the issue to a developer. The catch is governance: someone still needs to review and approve what the agent proposes before it touches production systems, and access controls over which repos or workflows the agent can reach will matter more than the convenience.

Salesforce Splits CRM Into API-Callable Building Blocks for AI Agents

For a 10-200 person B2B company running sales or support through Salesforce, this matters because it changes the integration layer, not the interface: automation platforms building AI-driven workflows (auto-updating opportunity stages, triggering case creation from a support ticket, syncing lead data into an outbound sequence) could get more stable, granular hooks into Salesforce instead of fragile UI scraping or broad, hard-to-maintain API calls. In practice this can lower the engineering cost of wiring AI agents into an existing Salesforce deployment and reduce breakage when Salesforce updates its interface, though exact API names, pricing, and rollout timing for these headless capabilities are unconfirmed pending Salesforce's technical documentation.