FieldPulse can be connected as your field service system, in the same role Housecall Pro, Jobber or ServiceTitan fill for businesses using those.
Connect one. Two field service systems reporting the same work is how a job gets counted twice.
What it brings in
The usual core: customers, jobs, invoices, estimates and payments.
And several record types the other systems do not expose, which is the reason to prefer it if you already use it:
Projects — work larger than a single job, with jobs underneath.
Subtasks — the steps inside a job.
Timesheets — hours recorded against work, which is what makes labour cost real rather than estimated. See job costs.
Assets — equipment at a customer's site, with its manufacturer. For maintenance businesses this is the history that makes a service visit efficient: knowing what is installed before arriving.
Purchase orders — what was ordered for the work.
Why timesheets matter most
Of everything above, timesheets change the numbers.
A job costed for materials and not labour always looks more profitable than it was, and labour is the larger number on most service work. Where hours are recorded against the job, job margin is a fact. Where they are not, it is an estimate that flatters.
Where it appears
Jobs and customers flow into Operations, and the money into your accounting figures. FieldPulse's own records get a view using its vocabulary — see what Operations shows for your field service system.
Access and data
The connection is authorised against your FieldPulse account and reads your records. It does not create or alter jobs, invoices or customers there, so nothing Omnyra does can change your field service data.
Access can be revoked from your FieldPulse account at any time, which stops the feed immediately and leaves everything already imported in place.