Your Salesforce Field Service jobs, invoiced days sooner.
Your dispatchers keep scheduling in Salesforce Field Service. Time-to-Invoice reads the job there and works it from the moment it's assigned to the moment the invoice goes out.
Book a Demo
Field ServiceStays in Salesforce Field Service
- Work orders
- Appointments
- Scheduling
Time-to-Invoice reads nineteen Salesforce objects and writes to none of them.
| What Time-to-Invoice reads | Objects |
|---|---|
| The job and the visit | WorkOrder, WorkOrderLineItem, ServiceAppointment |
| Who is assigned to it | AssignedResource, ServiceResource, ServiceTerritory, User |
| The equipment and its cover | Asset, AssetWarranty, WarrantyTerm, ServiceContract, ContractLineItem, Entitlement |
| Who it is for | Account, Contact |
| The parts it used | Product2, ProductItem, ProductRequest, ProductRequestLineItem |
Your org is never written to. In MSI Data's own words, in the setup guide your administrator follows: "Production behavior is read-only SOQL; there are no writes to your Salesforce org." If your build depends on a particular object or field, bring it to the call.
Your dispatchers never learn a second scheduling tool.
Work orders and appointments stay where your dispatcher set them. Time-to-Invoice doesn't replace the system they work in and doesn't ask them to schedule anywhere else. Nothing is migrated, and nothing has to be kept in step by hand.
Your admin can see what each connection covers, and switch either one off.
Time-to-Invoice lists the Salesforce Field Service connection alongside any other connections on one screen, each with what it covers and whether it's on. A question about scope has an answer inside the product instead of in an email to us.
Reduce your Time-to-Invoice one job at a time.
The invoice is already running late before the technician gets there. The tech arrives without knowing what the job needs and books a second visit. Something goes uncaptured on site and the office chases it afterward. By the time the work order closes, the invoice is waiting on hours, parts, photos and a signature that sit in different places.
Time-to-Invoice works that span: what the job needs before your technician goes, what gets captured while they're on site, and the close-out summary that comes back as what was found, done and recommended. Your billing team opens a complete job instead of assembling one.
A finished job that has not been billed is work your company has already paid for and cannot invoice yet. The days between the work and the bill come down, and neither system is swapped out to get there.
See how Time-to-Invoice worksYour own administrator can turn this on in about half an hour.
Nothing has to be built for you. Your administrator creates the external client app, grants the integration user read access to the objects above, and sends three values back. The field matching is yours, in the settings screen. If you'd rather have help, the MSI Data engineer on your account will do it with you.
Questions Salesforce Field Service teams ask.
Your Salesforce administrator creates the external client app, grants the integration user read access to the objects above and sends three values back. It takes about half an hour, and the MSI Data engineer on your account can do it with you.
No. It reads nineteen objects and writes to none of them.
No. Work orders and appointments stay where your dispatchers set them, and Time-to-Invoice reads the job there and works it through to the invoice.
No. Service Pro FSM is MSI Data's field service management software, with its own scheduling, dispatch and mobile app, and it connects to Salesforce Field Service as well. Time-to-Invoice works the span from job assigned to invoice sent.
Your demo starts with one of your jobs.
Bring a recent job that took too long to bill. We'll walk it through Time-to-Invoice on Salesforce Field Service, from the visit to the sent invoice. If someone looks after your Salesforce setup, bring them too. We'll answer their questions on the call.
Book a Demo