ServiceMax Engage is an app install inside a Salesforce Org. On My Way is a link.
ServiceMax Engage is the customer-facing companion to PTC’s asset-centric service platform. It installs into your Salesforce Org as an extension package, and customers download it from the App Store. On My Way is link-based, FSM-agnostic, and built for the residential moment-of-truth — tracking, rebooking, NPS, in-appointment marketing.
Used by enterprise operators in
Brinks Home runs OMW for US residential service — link-based, no app install, no Salesforce community licence.
What ServiceMax Engage is — in PTC’s own documentation.
ServiceMax Engage is positioned by PTC as a “turnkey mobile app that connects service organizations with their end customers.” Per the Salesforce AppExchange listing, Engage is installed into the customer’s Salesforce Org as an extension package to ServiceMax Core or Asset 360, with end-customer interactions happening in the context of a Salesforce Community (Experience Cloud licence implications).
That architecture works elegantly for ServiceMax’s native audience: asset-owner B2B operations — manufacturing plants, fleet operators, OEM service. For residential field service, the app-store-download flow and the Salesforce Community dependency are a different fit.
Every claim on this page is sourced to PTC’s product page, the Salesforce AppExchange listing, the PTC SaaS Service Description PDF, or G2 reviewer commentary. We’ve cited the source for each.
How ServiceMax Engage is architected.
Installs into your Salesforce Org.
“Engage is installed into the Customer’s Salesforce Org as an extension package to the Core or Asset 360 managed package.” That means a Salesforce Org plus ServiceMax Core or Asset 360 is a prerequisite to running Engage at all.
— Salesforce AppExchange listing
Customer-facing flow lives in a Salesforce Community.
End-customer interactions happen in the context of a Salesforce Community — with the Experience Cloud licensing implications that brings. A different operating model from a link-based customer experience.
— PTC product page / AppExchange listing
Custom-object extension is restricted.
From the PTC SaaS Service Description: customers “may not use the Salesforce components to create or use custom objects beyond those that appear in the Service.” The data model is fixed to what ServiceMax ships.
— PTC SaaS Service Description PDF
App-store download for end customers.
Engage is a native iOS / Android mobile app that customers download from the App Store or Google Play. For one-off residential service moments (boiler call-out, white-goods repair, alarm install) the install step is a different flow from a tap-the-link experience.
— Apple App Store / Google Play listings
Built around asset-owner B2B service.
PTC’s pitch: customers “access, interact with, and update in-depth asset data, including key performance metrics, bills of materials, service history, and product manuals.” A model built for equipment owners with ongoing asset visibility, not single-visit residential service.
— PTC ServiceMax Engage product page
A boiler customer at 7am on a Saturday isn’t downloading an app.
For B2B asset service — a facilities manager tracking a fleet of machines, an OEM technician supporting equipment owners — the value of a persistent app is real. Asset history, BoMs, manuals, performance metrics: an app is the right vehicle.
For residential field service — a homeowner with a one-off boiler call-out, a tenant rescheduling an annual service, a customer waiting for an installer — the friction of an app install at the moment they need to interact is the friction OMW was built to avoid. A link, opened in the customer’s existing browser, no install, no profile, is a measurably different conversion shape.
That’s why ServiceMax Engage is excellent for the audience PTC built it for — and why operators in residential and consumer-facing field service typically reach for something else.
ServiceMax Engage vs On My Way.
| Capability | ServiceMax Engage (PTC) | On My Way |
|---|---|---|
| Architecture | Salesforce Org extension package on ServiceMax Core / Asset 360 | SaaS layer on top of any FSM |
| Customer access | Native iOS / Android app download | Link — opens in the customer’s existing browser |
| Customer-facing flow | Salesforce Community (Experience Cloud licence implications) | Standalone customer-facing layer |
| Primary audience | Asset-owner B2B (manufacturing, fleet, OEM service) | Residential and consumer-facing field service |
| Data model extensibility | Restricted to objects shipped by ServiceMax (per SaaS terms) | SaaS — configured by Leadent |
| Prerequisites | Salesforce Org + ServiceMax Core or Asset 360 managed package | Your existing FSM and any CRM |
| Self-reschedule with WFM write-back | Yes, within ServiceMax-managed objects | Yes, FSM-agnostic |
| NPS & post-visit feedback | Available in the app | Built in — native to the customer link |
| In-appointment marketing | Not a focus | Native upsell on the tracking screen |
| Performance guarantee | None | 35% call deflection in 90 days — or we work free until you do |
| Cross-FSM portability | Tied to ServiceMax + Salesforce | Live across Oracle, IFS, SAP, Salesforce, Dynamics, ServiceMax |
| Named residential reference at scale | n/a publicly | Worcester Bosch (350 engineers), Foxtel, E.ON, Brinks Home (1.7M households via Reliance) |
ServiceMax architecture descriptions sourced from the Salesforce AppExchange listing and the PTC SaaS Service Description PDF. G2 implementation pain points (long timelines, learning curve, customisation friction) summarised from G2 ServiceMax reviewer aggregations.
"ServiceMax Engage is excellent for the audience PTC built it for. For residential service, the conversion shape is different."
Leadent implements field-service operations across Salesforce, Oracle, IFS and ServiceMax. The reason OMW sits alongside ServiceMax (rather than replacing it) is that customer audiences differ. ServiceMax Engage is built for asset-owner B2B: equipment owners, OEM service, fleet operators who benefit from a persistent app with asset history. OMW is built for residential field service: link-based, no app install, no Salesforce Community licence. Both can run in the same operation, for different segments.
Everything procurement asks about — built in.
SSO via Microsoft Entra ID
Single sign-on, role-based access — works alongside your existing Salesforce / ServiceMax SSO model.
Passcode-protected access
Customer links are passcode-protected by default — relevant for home-security and utilities.
Encrypted in transit
End-to-end encryption between your FSM and On My Way.
GDPR & Works Council ready
Built to meet GDPR and Works Council requirements out of the box.
Regional data residency
UK / EU residency available, named in procurement diligence.
No app-store dependency
Customer-facing layer is link-based — no install, no app-store approval, no version migration treadmill.
ISO 27001 aligned
Security management built to ISO 27001 — named in enterprise procurement diligence.
Customer view, agent view — the same live picture, both sides of the call. No app install required for the customer side.
Outcomes from operations running OMW for residential service.
53%
fewer ETA-related calls
Worcester Bosch · UK gas service
34%
reduction in change calls
Brinks Home · US home security
1.7M
households on On My Way
Reliance Home Comfort · Canada
The verdict.
- ServiceMax Engage is excellent at what PTC built it for: asset-owner B2B service with ongoing equipment-history visibility.
- Engage requires a Salesforce Org plus ServiceMax Core or Asset 360 plus an Experience Cloud Community to operate — and customers reach it via an app-store download.
- For residential, consumer-facing, single-visit service, those architectural choices change the conversion shape at the moment-of-truth.
- OMW is link-based, FSM-agnostic, built for the residential moment, and ships with the 35% call-deflection guarantee in 90 days.
Hit 35% call deflection in 90 days — or we work for free until you do.
Layer OMW on top of your existing FSM — even one running ServiceMax. Run a 6-week pilot. If we haven’t cut your appointment-related call volume by 35% within 90 days of full live, we keep working at no fee until we have.
Frequently asked questions
We already use ServiceMax. Why would we add OMW?
Engage is built for asset-owner B2B service. If you also run residential or consumer-facing work, the app-install flow and the Salesforce Community dependency are a different conversion shape from a link-based experience. OMW takes the residential customer-facing layer; ServiceMax keeps doing what it’s best at.
Can OMW work alongside ServiceMax Engage?
Yes. OMW sits on your scheduling / FSM data and surfaces a link-based customer experience. It doesn’t replace Engage — it operates alongside, often for different customer segments (Engage for asset-owner accounts, OMW for residential).
Does OMW require us to use Salesforce?
No. OMW is FSM-agnostic and CRM-agnostic. We run on top of Oracle Field Service, IFS PSO, SAP FSM, Salesforce Field Service, Dynamics 365 Field Service, and ServiceMax. Your existing stack is your prerequisite, not ours.
What if our customers expect an app for asset history?
Then Engage is the right fit for those customers. OMW isn’t an asset-management app; it’s a customer-experience layer for single appointments and the moment-of-truth around them. Most operators in our customer base run both for different audiences.
How does OMW handle pre-visit data — photos, notes?
Natively. Pre-visit photo upload and notes were the feature E.ON used to drive a 19% first-time-fix improvement on their utilities deployment.
What about the data model restrictions PTC publishes?
Those are PTC’s own SaaS terms — customers “may not use the Salesforce components to create or use custom objects beyond those that appear in the Service.” OMW has no such restriction because it’s a separate SaaS layer; Leadent manages the configuration.
What’s the implementation timeline?
Four to six weeks. We offer a 6-week pilot with the first 30–60 days free; the 35% call-deflection guarantee starts the day you go full live.
Compare On My Way against another option.
A link, not an app install — for the residential moment-of-truth.
Put OMW on top of your existing FSM for 6 weeks. Hit 35% call deflection in 90 days — or we work free until you do.