
Tekunda Team

Tekunda Team

Connected-asset triage on Service Cloud is the path from a raw device signal to a resolved case: the event lands as a platform event, an agent decides whether it needs a human, and Field Service dispatches a technician only when it does. Done well, most signals never become a truck roll, and the visits that remain arrive with the device history, entitlement and likely fix already attached.
Most guides on connected field service stop at "sensors create work orders". The hard part is the middle: deciding, at volume, which events deserve a case and which cases deserve a visit. That is where we have spent our time at Tekunda, and it is what this article covers.
Triage is the decision layer between telemetry and service. Salesforce describes connected field service as using internet-connected sensors and data analysis to monitor and maintain equipment at customer sites. Triage adds the judgement: suppress noise, group related signals, resolve remotely when possible and escalate with context when not. If your team still runs ticket-first support, start with how Service Cloud is changing customer support.
This is the flow behind asset lifecycle management for connected devices, and Tekunda IoT Cloud runs it natively on Service Cloud, Field Service and Data 360.
The numbers make the point. At ASSA ABLOY, weekly cases fell from 3,000 to 350 while the connected base grew from 5,000 to 11,000 devices and peaked at 2.5 million events a week, with no added support staff. The full story is in how connected-device teams cut support cases by 93 percent.
Salesforce announced Asset Service Lifecycle Management in June 2024 as an add-on for asset-intensive industries. It brings pre-configured Data Cloud data kits plus tools to select service entitlements, view all active entitlements per asset, send work-order quotes on site and manage campaigns such as recalls and upgrades. A sibling add-on, Connected Assets, links asset data with customer information and responds to bi-directional telematics events.
Triage is where these pieces earn their keep: entitlements decide what a signal is owed, and campaigns turn one fault pattern into a fleet-wide fix. Our asset lifecycle management practice builds directly on them.
Salesforce renamed Data Cloud to Data 360 at Dreamforce 2025 and positions it as the data layer that gives agents context. For triage, that means the agent reasons over telemetry, service history and ERP data in one place, not three. As a Data 360 partner, we design the data model those agents read.
At TDX 2026, Salesforce launched Headless 360, which exposes the platform as APIs, MCP servers and CLI commands so agents can work without a browser. Headless MCP matters for connected assets because the device side is never a person at a screen. Tekunda is the first and only partner running headless CRM plus MCP in production, and the first to run agent-to-agent (A2A) and SWARM orchestration in production, where a triage agent hands work to a parts agent and a scheduling agent instead of doing everything itself.
Start with Salesforce's own Agentforce ROI calculator. It estimates three-year net benefits for selected use cases, including Customer Service and Field Service, from inputs such as headcount, compensation, cases handled and first-time fix rate, and it estimates the Flex Credits you will need. Salesforce notes the results are illustrative and exclude implementation costs and licences.
For connected assets, add two inputs the calculator cannot see: cases that never open because duplicates collapse, and truck rolls avoided by remote fixes. Those usually carry the business case. The goal is more capacity for the same team on Salesforce, not fewer seats.
Every gateway that publishes events is an integration identity. Scope its connected app tightly, rotate its credentials and log what it does. Before go-live, work through our connected app security readiness guide. If you are packaging a triage product for AppExchange, the same discipline carries you through security review, and as a certified Salesforce SI, ISV and PDO partner we take ISVs through it.
Does every device event create a Service Cloud case?
No. Triage filters and deduplicates events first, so a case opens only when a signal needs action, and repeat signals update that case.
Do I need Field Service for connected-asset triage?
You need it for the dispatch step. Remote resolution can run on Service Cloud, but scheduling a technician with full context is a Field Service job.
What is headless MCP in Salesforce?
It is Salesforce exposing its platform through MCP servers, APIs and CLI so AI agents can call data and workflows without a user interface. Salesforce launched it as Headless 360 at TDX 2026.
Does connected-asset triage replace our ERP?
No. A case can trigger parts, work orders and compliance evidence back into your ERP, which stays the system of record.
If your service team still learns about faults from customers, see how we run Field Service for connected devices and dispatch only when a visit is truly needed.