How to Start Testing Agentforce for Mobile Workers in Salesforce Field Service
In this Office Hours Insight session, Leigh-Anne Nugent explores two practical ways to improve the mobile technician experience in Salesforce Field Service: first, by using simple visual cues like emojis in service appointment list views, and second, by setting up Agentforce for mobile workers. The bigger takeaway is that even small UX improvements can help drive better field behavior, while AI-powered pre-work briefs can start turning the mobile app into a smarter assistant for technicians in the field.
LESSONS YOU CAN TAKE FROM THIS:
1. Small mobile design choices can improve technician behavior
One of the quickest wins shown in this session is using formula-based emoji status indicators in the service appointment list view. That gives technicians an immediate visual cue for what to do next, like calling the customer before heading out or recognizing that a job is already in transit. It is simple, but it is a smart reminder that mobile UX matters in field service.
2. Agentforce for mobile workers depends on more setup than it first appears
Turning on Agentforce for mobile workers is not just a one-click feature. Leigh-Anne walks through enabling Agentforce default first, assigning the right permission sets, activating the supporting flow, and making sure the work order has the correct pre-work brief template ID populated. That setup sequence matters, and missing one piece can stop the whole experience from working.
3. Pre-work briefs are only as useful as the data they can access
A strong theme in this session is that the AI brief itself is not the real magic. The value comes from what data is being gathered and passed into it. Work orders, assets, contacts, work order line items, work plans, and potentially even products or required parts all shape how useful that pre-work brief will be for a technician before they start the job.
4. AI in the mobile app still needs real-world testing
This session is also a reminder that enabling a feature and seeing it work are not the same thing. Permissions, prompt setup, mobile login behavior, SDK settings, and device-specific support all affect the result. Just like other field service mobile features, Agentforce for mobile workers needs hands-on testing in the actual app before teams can trust it in production.
KEY TAKEAWAYS:
Simple emoji cues can make the mobile app more intuitive for technicians.
Agentforce for mobile workers requires setup across Agentforce, permissions, flows, and work order fields.
Pre-work brief quality depends on the objects and related data included in the prompt.
Mobile AI experiences still need careful testing, especially around permissions and platform behavior.
The long-term opportunity is turning the mobile app into a more proactive field assistant, not just a status-update tool.
