---
title: "What is FieldBuddy?"
canonical: "https://help.fieldbuddy.com/space/FBDOCS/5262802967/What%20is%20FieldBuddy%3F"
format: markdown
---
FieldBuddy is [field service management](https://en.wikipedia.org/wiki/Field_service_management) software built by the company named [FieldBuddy B.V](https://www.fieldbuddy.com/nl/over-ons/), located in Amsterdam. 

> **Field service management (FSM)** refers to the management of a company's resources employed at or en route to the property of clients, rather than on company property. Examples include locating vehicles, managing worker activity, scheduling and dispatching work, ensuring driver safety, and integrating the management of such activities with inventory, billing, accounting and other back-office systems. FSM most commonly refers to companies who need to manage installation, service, or repairs of systems or equipment. It can also refer to software and cloud-based platforms that aid in field service management.

![image](media://d66529e9-94f5-47c1-8985-0453e4233fef)

## The company

FieldBuddy B.V. is a registered company located in Amsterdam. Find more [about us](https://www.fieldbuddy.com/about-us/) and the team on our public website. Contact us directly via [this form](https://www.fieldbuddy.com/contact/). 

> ℹ️ Company name: FieldBuddy B.V.  
> ℹ️ Address: Kraanspoor 42, 1033 SE Amsterdam  
> ℹ️ Bank account: NL24INGB0104241608  
> ℹ️ Swift: INGBNL2A  
> ℹ️ KvK number: 87750368  
> ℹ️ VAT number: NL8643.93.210.B01  
> ℹ️ DUNS number: 494409660  
> ℹ️ Phone: +31(0)20-2611100

Starting 7/1/2026:

> ℹ️ Company name: FieldBuddy B.V.  
> ℹ️ Address: Willem Fenengastraat 16 G 1096 BN Amsterdam  
> ℹ️ Bank account: NL10ABNA0128375418  
> ℹ️ Swift: ABNANL2A  
> ℹ️ KvK number: 27359150  
> ℹ️ VAT number: NL821428378B02  
> ℹ️ DUNS number: 489595430  
> ℹ️ Phone: +31(0)20-2611100

## The product

FieldBuddy consists out of the following applications: 

1. [FieldBuddy Service Center](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5041750021), a web-application. This is were all data and processes are stored and is mainly used by the back-office.
2. [FieldBuddy Swift](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/4940759085), a mobile application. This is to process Work Orders on a mobile phone or tablet.
3. [FieldBuddy Dispatch Panel](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5181046791), a planning web-application. This is to schedule Work Orders.
4. [FieldBuddy Setup](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5367267365), an administration tool to modify processes, data-model and more.
5. [FieldBuddy Customer Portal](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5367136310), a web-application accessible for external users(customers, partners, ..) to access services like reporting a service request.
6. [FlexConnect](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5262540804), an integration solution. This is used to connect external systems to FieldBuddy.

For each application there’s documentation available. 

> ⚠️ For each application there are hardware and software requirements. You can find them here:  
> ⚠️   
> ⚠️ [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5367464036](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5367464036) 
> ⚠️ 
> ⚠️ [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5183340667](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5183340667) 
> ⚠️ 
> ⚠️ [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5367136324](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5367136324) 
> ⚠️ 
> ⚠️ [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5367398432](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5367398432)

#### Product structure

Each application has one or more modules. A module consists out of features. Some modules or features are depended on the [edition ](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5262802967/What+is+FieldBuddy#Editions)of the product. 

You can find the different modules of each application in its documentation. 

## Our websites

You can find FieldBuddy on numerous locations. These are the most important:

1. The login page for all our customers, [login.salesforce.com](http://login.salesforce.com). FieldBuddy customers get automatically their own private login page, but this page is applicable for all customers.
2. Our main website, [www.fieldbuddy.com](http://www.fieldbuddy.com). Primarily for new potential customers.
3. Our help website, [help.fieldbuddy.com](http://help.fieldbuddy.com). Primarily for our customers and implementation partners.
4. Our customer portal, [customers.fieldbuddy.com](http://customers.fieldbuddy.com). The support portal for customers to create cases.
5. Our job page, [fieldbuddy.recruitee.com](https://fieldbuddy.recruitee.com/). We list our job offers on this page.

FieldBuddy can be found on external websites, like:

1. [Salesforce Appexchange](https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000008ZZkbEAG)
2. [Exact Online App Store](https://www.exact.com/nl/app-store/fieldbuddy)
3. [AFAS Partner](https://partner.afas.nl/koppeling/fieldbuddy)

Social Media:

- [LinkedIn](https://nl.linkedin.com/company/fieldbuddy)
- [Facebook](https://www.facebook.com/fieldbuddy/?locale=nl_NL)
- [Twitter](https://twitter.com/fieldbuddy)

## Our implementation partners

FieldBuddy offers the product and the licenses, and our partners offer the services. 

## For who is FieldBuddy?

Company’s that have field service processes and a mobile workforce. Each application is used by a user of a certain role. Exceptions are possible, in general it is the following:

The users of the FieldBuddy Service Center are:

- Backoffice employees
- (Service) Managers
- C-level managers
- Administrators

The users of the FieldBuddy Swift applications are:

- Technicians
- Inspectors
- Contracters

The users of the FieldBuddy Dispatch Panel are:

- Planners

The users of the FieldBuddy Setup are:

- Administrators

The users of the FieldBuddy Customer Portal are:

- Your customers
- Your partners
- Your contractors

## Editions

FieldBuddy has three editions:

1. FieldBuddy Starter
2. FieldBuddy Professional
3. FieldBuddy Enterprise

Its differences and pricing can be found [here](https://www.fieldbuddy.com/pricing/).

## FieldBuddy functionally

The application is functionally split up in several product area’s. Each product area has a landing page on [our website](https://www.fieldbuddy.com/). There’s also a list of all features available on [our website](https://www.fieldbuddy.com/all-features/).

![image](media://af0a3aa3-56ef-46be-a527-4b34ab8e2609)

Our application is functionally split up into three layers:

- Application, see [our list](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5262802967/What+is+FieldBuddy#The-product) of applications.
- Module, a module is a group of features.
- Feature, a capability that a user has.

![image](media://556e3bff-99df-4f68-b89b-ba53da6017cd)

## FieldBuddy technically 

FieldBuddy consists out of multiple elements. All together they are offered as FieldBuddy (including the items that are part of the Salesforce platform). 

The Salesforce platform is offered to third party developers by Salesforce as [PAAS](https://nl.wikipedia.org/wiki/Platform_as_a_service), platform as a service. 

> ℹ️ Salesforce Platform (formerly known as force.com) is a platform as a service (PaaS) that allows developers to add applications to the main Salesforce.com application.  These applications are hosted on Salesforce's infrastructure.
> ℹ️ 
> ℹ️ Force.com applications are built using Apex, a proprietary Java-like programming language to generate HTML originally via the "Visualforce" framework. Beginning in 2015 the "Lightning Components" framework has been supported. 
> ℹ️ 
> ℹ️ As of 2014, the Salesforce.com platform had 1.5 million registered developers according to Salesforce.  
> ℹ️   
> ℹ️ Source [Wikipedia](https://en.wikipedia.org/wiki/Salesforce).

The platform is cloud based and [multi-tantent](https://en.wikipedia.org/wiki/Multitenancy). Read more about Salesforce their architecture [here](https://architect.salesforce.com/fundamentals/platform-multitenant-architecture). The platform is available worldwide and its [servers](https://help.salesforce.com/s/articleView?id=000396845&type=1) are located in many regions.

The elements that FieldBuddy consists out of are:

![image](media://a98b0557-27df-487b-8c6a-4e388966947a)

These elements are:

1. Un-managed content on the Salesforce platform (Quick Create Work Order, Work Order PDF, ..)
2. FieldBuddy Package which hosts multiple applications
3. FlexConnect Package which offers integrations to external systems
4. Salesforce platform features (Setup, Reports and Dashboards, ..)
5. A mobile application named FieldBuddy Swift

### Unmanaged content

Unmanaged content are components that are part of FieldBuddy but which are explicitly left out of the package. These components can be heavily modified during an implementation by a partner. The source code of these components are available for modification. Components that are in the package can <u>not</u>** **be modified, its source code is protected. 

The components that are unmanaged:

1. Community Template for the FieldBuddy Customer portal
2. Some custom fields
3. Quick Create Work Order
4. Work Order PDF

### FieldBuddy Package

FieldBuddy Package consists out of the following components: 

1. FieldBuddy Service Center
2. FieldBuddy Dispatch Panel (an application)

### Extension Package

An [extension package](https://developer.salesforce.com/tools/vscode/) is a package depended on another package. The FieldBuddy Smart Planning package is depended on the FieldBuddy package. The FieldBuddy Smart planning package has the integration with [Quinyx](https://www.quinyx.com/nl/), our AI provider for route and planning optimalisation.  

### FlexConnect Package

The FlexConnect package is like the FieldBuddy package a [managed package](https://help.salesforce.com/s/articleView?id=sf.s1_branded_apps_managed_package_about.htm&language=en_US&type=5). 

### Salesforce platform features

The platform offers to FieldBuddy customers tons of features, like:

1. One or more Community (Customer Portals)
2. Layout Editor to modify pages
3. Object manager to create objects and custom fields
4. etc.

### Mobile application

FieldBuddy Swift is a mobile application built in the react-native framework

## Core of FieldBuddy

In order to understand what the core of the application is, please make sure to read [this](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/edit-v2/5262802967#FieldBuddy-technically) ('What is FieldBuddy technically') first.

The core of the application is the following:

- The FieldBuddy managed package (including the FieldBuddy Dispatch Panel)
- The mobile application FieldBuddy Swift
- The Smart Planning extension packages

What is <u>not</u> the core of the application:

- Anything that is configured/customized/built on top of FieldBuddy. For example:
  - Any unmanaged [content](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/edit-v2/5262802967#Unmanaged-content)
  - Anything configured by a (partner) consultant or administrator
  - Modifications done to the FieldBuddy Swift config & briefcase
  - Workflows, custom fields, custom fields, etc.
- Usermanagement
- Permissions

> ℹ️ All what is not the core of the FieldBuddy application is supported by the partner.  
> ℹ️ All what is the core of the FieldBuddy application is supported by FieldBuddy.

## FieldBuddy on the Salesforce platform

FieldBuddy is a native software application built on the Salesforce platform. It uses technology from the Salesforce platform and is part of the Salesforce eco system. Find us on the [Appexchange](https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000008ZZkbEAG).

> ⚠️ Customers don’t require to be a Salesforce customer to purchase FieldBuddy. Being a user of other Salesforce products is **optional**.

Salesforce is mostly known for its CRM solution, the [Salesforce Sales Cloud](https://www.salesforce.com/nl/products/sales-cloud/overview/). But Salesforce offers many products, and one of those products is the [platform](https://www.salesforce.com/eu/products/salesforce-platform/) itself to third party OEM partners. FieldBuddy is a Salesforce OEM Partner.

Being a native solution on the platform offers great advantages:

1. We are scalable, it does not matter if your company has 1, 10, 1000 or 10.000 users.
2. We are available world wide.
3. We have 0% downtime in 10 years time.
4. We are flexible, because part of buying FieldBuddy is lots of technology to modify, configure FieldBuddy to your needs.
5. We are secure, the platform has the highest level of [security ](https://security.salesforce.com/)standards.

In technical terms, our application is known as a [managed package](https://help.salesforce.com/s/articleView?id=sf.s1_branded_apps_managed_package_about.htm&language=en_US&type=5#:~:text=A%20managed%20package%20is%20a,to%20request%20a%20managed%20package.) and is distributed via the [Salesforce Appexchange](https://appexchange.salesforce.com/). 

FieldBuddy has two types of customers:

1. Customers that uses FieldBuddy and no other Salesforce products. These customers have no legal relation with Salesforce.
2. Customers that uses FieldBuddy and Salesforce products. These customers have a <u>single</u> environment in which the Salesforce product and FieldBuddy product natively work together. Users are often not realizing that they are moving from one product to the other.

## Licenses

FieldBuddy has three editions of its solution and is a native application on the Salesforce platform. Licenses are per individual user and offer access to FieldBuddy. A company can only have a single edition (Starter, Professional, Enterprise) license in their organization, these can not be mixed. 

There are different ways to explain a FieldBuddy license. From a commercial, legal or technical point of view. In this documentation we describe what it technically means.  

> ℹ️ This information is primarily for Administrators.

A license consists out of two parts:

1. Access to the Salesforce platform
2. Access to the FieldBuddy managed package

These two parts are managed differently and are different from each other but they are commercially sold as one, for example: ‘FieldBuddy Professional’. 

### Access to the Salesforce platform

The Salesforce part gives the user access to the platform. There are different license types to get access to the platform:

1. **Platform** (this is used by all users that require access to the FieldBuddy Service Center, Dispatch Panel and our mobile application)
2. **Salesforce** (full license, for each FieldBuddy customer at least one full license is available for the System Administrator. This license gives you access to the SETUP)
3. **Customer Community** (this license is used for FieldBuddy portal users)
4. **Integration **(this license is used by application that integrate with the platform)

Having this license will allow you to login to the platform. But does **not **give you acces to the FieldBuddy Managed package.

Read [here](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/4908154897) in how to create users.

### Access to the FieldBuddy Managed package

In order to get access to the FieldBuddy managed package including all its data, metadata and applications a user requires the second part: a license of the managed package.

All FieldBuddy managed package licenses are the same. There’s no differentiation, only one type. A managed package license can be assigned to a user and removed at any time. 

Read [here ](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/4908154897)in how to assign and remove licenses from a user.

## Integrations

There are multiple types of integrations with external systems. These are the types:

1. FlexConnect integrations
2. Middleware integrations
3. Custom integrations
4. Native integrations

### FlexConnect integrations

[FlexConnect](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5262540804) is a native application on the Salesforce platform build by FieldBuddy B.V. This application acts as middleware. Its fully in the cloud and has no required servers. The integrations that are offered via FlexConnect are:

- Exact Online
- AFAS
- Twinfield
- Accountview
- Unit 4

There’s no additional fee for FieldBuddy customers to use FlexConnect.

### Custom integrations

Our platform offers numerous ways to integrate with FieldBuddy. The platform offers:

1. [Custom webservices](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_rest.htm), build custom REST endpoints for external systems to integrate.
2. [External services](https://help.salesforce.com/s/articleView?id=sf.external_services.htm&language=en_US&type=5), use point and click tooling to create integrations.
3. [REST API](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm), use the natively built in REST API to integrate with any data in FieldBuddy.

### Middleware integrations

The platform has many middleware solutions that can be used to connect FieldBuddy to other systems. This is a brief list of solutions:

1. [Pentaho ](https://help.hitachivantara.com/Documentation/Pentaho/Data_Integration_and_Analytics/9.1/Products/Pentaho_Data_Integration)
2. [Microsoft SQL Server Integration Services](https://learn.microsoft.com/en-us/sql/integration-services/sql-server-integration-services?view=sql-server-ver16)
3. [Mulesoft](https://www.mulesoft.com/)
4. [Zapier](https://zapier.com/)

These middleware integrations often use the REST API to communicate with the platform.

> ℹ️ Make sure that your middleware solution has the option to communicate with custom objects or objects coming from a managed package.

### Native integrations

Native integrations are integrations with other applications that are built on the Salesforce platform. These integrations don’t require data to leave the platform. 

The Salesforce platform has thousands of applications on their [Appexchange](https://appexchange.salesforce.com/). Salesforce itself has solutions as Salesforce Sales Cloud to which you can natively integrate.

## Releases & Updates

FieldBuddy updates their software frequently. We apply the ‘[release early, release often](https://en.wikipedia.org/wiki/Release_early,_release_often)’ principle. There are different types of releases:

1. Platform updates
2. FieldBuddy Swift updates
3. FieldBuddy Package updates

### Platform updates

The platform updates three times per year automatically. Read more about this [here](https://help.salesforce.com/s/articleView?id=sfdo.SFDO_Keep_Up_SF_Rels.htm&type=5). 

### FieldBuddy Swift updates

Our mobile solution FieldBuddy Swift is frequently automatically updating. Release notes can be found [here](https://help.fieldbuddy.com/page/release-notes) and more about its process [here](https://help.fieldbuddy.com/space/FBDOCS/4940759085/About+our+mobile+application:+FieldBuddy+Swift).

### FieldBuddy Managed package updates

Our managed package, the technical package that hosts the FieldBuddy Service Center and FieldBuddy Dispatch Panel is also frequently updated automatically. 

Releases notes can be found [here](https://help.fieldbuddy.com/page/release-notes).

## Screenshots & Video’s

To give some impressions on how the FieldBuddy looks like:

Video’s:

More can be found on our [Youtube channel](https://www.youtube.com/@Fieldbuddy).