Fynaxis Blog
Salesforce insights, AI trends, and field service updates from our team of certified experts.
When Salesforce Field Service is right for a small business — and when it's not
Real Salesforce Field Service licence costs, the technician-count threshold where the math actually works, and an honest read on which small businesses are running it in North America and Europe — and which ones shouldn't.
Read more
Service Territory Polygons in Salesforce Field Service: What Architects Wish They'd Known
Service Territory polygons look like a five-minute job — draw a shape, save, done. They're not. Here are the architect-level gotchas that don't show up until you've already tripped over them.
Read more
Salesforce Appointment Assistant: How Customers Can See Where the Field Agent Is
When customers can't see where the technician is, they call the dispatch desk. Salesforce Appointment Assistant gives them an Uber-style live map on their phone instead. Here's what it does, what the technician controls, and what you need to switch it on.
Read more
How Salesforce Field Service Handles Time Zones for Technicians, Customers, and Dispatchers
Cross-zone scheduling is one of the easiest ways to lose customer trust. Here's how Salesforce Field Service keeps every appointment right for the dispatcher who books it, the technician who shows up, and the customer waiting at the door.
Read more
Salesforce Field Service Shifts vs Operating Hours: When to Use What
Operating Hours and Shifts in Salesforce Field Service look like they do the same job — they don't. Here's a casual walkthrough of which to use when, how the Scheduling Policy ties them together, and the bits most teams get wrong.
Read more
Agentforce + Field Service Dispatching: the honest architecture
Most "AI dispatching" pitches overstate what an Agentforce agent actually does. Here's the architecture that works in production — Agentforce reasoning sitting beside the FSL Optimisation engine, not on top of it.
Read more
First-Time Fix Rate: where the leverage actually is (and why AI isn't lever number one)
Most "AI for first-time fix" pitches sell you the cherry without the cake. Four boring levers move 90% of FTFR — skill match, parts on the van, pre-work context, and asset history. AI is the multiplier that earns its keep on top of those.
Read more
Appointment Reminders in Salesforce Field Service: the architecture under the hood
A reminder text looks simple. Behind it is a 4-layer stack — triggers, channel routing, templating, delivery tracking — that decides whether your customer gets the right message at the right time, on the right channel, in the right language.
Read more
Salesforce Field Service in the GCC: the architecture decisions before any rollout
Vision 2030 is the headline. Hyperforce region, data residency, Shield posture, workweek configuration, and localisation are the architectural decisions you actually make. Each one is hard to reverse — get them right at week one.
Read more
Predictive Maintenance with Salesforce Field Service: Real vs Pitch
Predictive maintenance in Salesforce isn't a button — it's a pipeline. Telemetry → trained model → triggered Work Order. Here's what each layer actually requires, and the prerequisites the keynote demos quietly assume you already have.
Read more
Crew vs Complex Work Order in Salesforce Field Service: The Architect Decision
Two ways to schedule multi-technician jobs in Salesforce Field Service — and most teams pick the wrong one. Here are the architect-level differences in the data model, scheduling, and skill-matching that decide which is right.
Read more
Pre-Work Briefs in Field Service Mobile: the data model behind the magic
A Pre-Work Brief looks like a tidy mobile screen. Behind it is a data-modelling discipline most teams skip — the briefcase rules, the Knowledge linkage, and the sharing rules that decide whether the tech actually sees anything useful.
Read more