Integrations
You aren't replacing your service systems. Neither are we.
FieldPal sits on top of what you already run rather than asking you to move into it. Answers come from your existing documentation today; two-way integration into your service and warranty systems is in active development.
The principle
A layer, not a landgrab
Most frontline software arrives asking you to move your work into it. That is a migration, a data model argument, and a two-year programme before anyone sees value.
FieldPal takes the opposite position. Your CMMS keeps the work order. Your service system keeps the job. Your document store keeps the manuals. FieldPal is designed as the layer that makes those things reachable by voice at the point of work, and writes structured records back into them as two-way integration ships.
Find already works this way today, answering from documentation you point it at. That is also why FieldPal can be useful in week one rather than after a platform rollout.
Where it sits
Above your systems of record, not instead of them
Top
At the asset
The layer
FieldPal
Underneath
What you already run
On the roadmap
The systems we are building this for
None of this is shipped yet. This is what two-way integration is being built to do. Tell us your stack and we'll tell you where each one stands today.
-
Microsoft Dynamics
Push structured job and service records into the system your commercial teams already work from.
-
ServiceNow
Raise and complete work with the detail attached, rather than a closing note typed from memory.
-
SharePoint and document stores
Point FieldPal at the manuals, bulletins and technical instructions you already hold, wherever they currently live.
-
CMMS and service platforms
This complements the system of record rather than competing with it. It keeps the work order; FieldPal fills in what happened.
-
Parts and warranty systems
Connect the record to the claim, so narrative and evidence arrive together and inside the submission window.
-
Your own applications
Where you need FieldPal inside a workflow of your own, integration will be scoped as part of onboarding.
How integration will work
Sized to the deployment, not to the invoice
-
01
Out of the box
Smaller teams will connect common systems with simple configuration and self-service onboarding. There is no consultant and no project plan.
-
02
Enterprise integration
Complex environments will get professional services, from us or a certified partner, to map FieldPal into legacy systems and existing workflows.
-
03
Partner-delivered
We are deliberately designing this so channel partners can deliver integration and support, so delivery scales with you rather than queueing behind us.
Questions
What people ask about fitting FieldPal in
- Do we have to migrate our data into FieldPal?
- No. The intent is that your CMMS keeps the work order, your service system keeps the job, and your document store keeps the manuals. FieldPal is designed as the layer that makes those things reachable by voice and puts structured records back into them, as two-way integration ships.
- Is FieldPal integrated with our systems today?
- Not yet. Two-way integration with Microsoft Dynamics, ServiceNow, SharePoint, CMMS and service platforms, and parts and warranty systems is in active development. Find already answers from documentation you point it at; writing records back into your systems is the part still being built.
- When will integration be available?
- Tell us which system matters most to you and we'll give you a real answer on timing rather than a generic date, plus where you sit if you want to be an early integration customer.
- Will a partner be able to deliver the integration instead of FieldPal?
- That is how it is being designed. Channel partners will be able to deliver integration and support, so delivery scales with you rather than queueing behind us.
Tell us what you're running
Bring your stack and a real workflow. We'll show you where FieldPal slots in and just as clearly where it doesn't.