Skedulo

This is a scheduling layer, not a full field service back office, and that distinction is the whole point of the product. Skedulo describes using integrations, APIs and events to exchange data with CRM, HR, payroll and other business systems, and its own worked examples show workflows that update a work order in Salesforce. It ships a Salesforce managed package that sets up the data structures in the CRM, supports API calls from Apex, and documents SSO through a Salesforce custom domain. In honesty, Skedulo also presents itself as a system of record for work and people data and does not state how responsibility divides with a CRM or ERP, so it is not strictly CRM-dependent. But a buyer evaluating it against Jobber or ServiceTitan is comparing different things: those replace your back office, this schedules against one you keep.

The platform layer is called Pulse Platform, with shipped modules named Tempo for AI scheduling, Field for field scheduling and routing with an optimiser called Mastermind, Shift for rostering, and Mobile for the technician app. Covering both job-based dispatch and shift rostering in one platform is genuinely unusual and matters where the same workforce is both rostered and dispatched, for example healthcare and human services, which is a named vertical alongside home services, telecommunications, energy and solar, security and facilities, inspections and safety, and manufacturing.

Two things stand out as unusually good. First, the developer platform is complete and public: GraphQL with an interactive explorer, a REST API reference, an object reference, a CLI, Functions and sample repositories. Very few FSM products expose this much. Second, offline is documented with bounded, specific scope rather than asserted. Offline edits to job details and notes queue in a visible Pending changes tab and sync automatically on reconnect, with a banner when connection drops and data retained when the app is backgrounded or the user logs out.

• Nothing commercial is published. The pricing page carries no figures, no plan names, no licensing wording and no trial. The only call to action is Book a Demo, with a promised reply within one business day. Booking a demo is not a trial.
• There is no public integration catalogue. Skedulo refers only to supported integrations, APIs and events, and the 121 integrations tile on its platform page is part of a mockup, not a factual count. Buyers cannot pre-check connector fit.
• Two mobile app generations run in parallel, with the current one called Skedulo Plus and the older v2 offline guide sitting under a Deprecated heading. That is a migration question to ask.

Good fit: mid-market and enterprise organisations with a frontline or deskless workforce who already have a system of record they are not going to move, most obviously Salesforce. The Salesforce managed package makes that pairing concrete. It is the best fit in this category when the same people are both rostered into shifts and dispatched to jobs, because Field and Shift are both first-class rather than one being bolted onto the other. Engineering-capable teams will get real value from the GraphQL, REST, webhook and CLI surface, which is more complete than most competitors offer.

Poor fit: small businesses, which Skedulo shows no evidence of targeting. Also a poor fit as a standalone back office: quoting, invoicing, inventory, service contracts and customer portal were all unverifiable on the vendor site, which suggests the product is not trying to be the system that bills your customers. If you need one product to take a job from quote to cash, look at the trades products in this category instead. Finally, it is a poor fit for buyers who need to shortlist on published price or to self-serve a trial, because neither exists.

Typical use cases: healthcare and human services visit scheduling, telecoms and energy field scheduling against an existing CRM, inspections and safety programmes, and mixed rostered and dispatched workforces. Budget for a sales-led evaluation and ask specifically about mobile app generation migration.