This integration is an early preview and not available for all users.

Connect your ArcSite and ServiceTitan environments to have seamless flows of information that can be used in customer relationship management and much more.

Linking your ServiceTitan Environment with your ArcSite account can eliminate double-entry and can speed your sales process up significantly.

Key Features

Setup Overview

Connecting ArcSite and ServiceTitan

Product to Item Mapping

ArcSite Project Information to ServiceTitan Job Information Mapping

Setup Considerations

Usage Considerations

Potential Error Conditions

Additional Questions and Answers

When a job is booked in ServiceTitan, ArcSite will receive a notification and automatically create a project based on the job information, linking the created project with the job.

This includes assigning the new ArcSite Project to a specified team member.

Subsequent operations in ArcSite will continuously synchronize information to ServiceTitan.

When a new version of an ArcSite drawing is uploaded to the ArcSite cloud, this integration will automatically push the latest Drawing PDF to the related ServiceTitan's Job.

Each drawing version uploaded to cloud will push to ServiceTitan as a new attachment in the Job.

Users can push the ArcSite Proposal to ServiceTitan in two ways:

One drawing will create one corresponding estimate in ServiceTitan. If the drawing is updated later and pushed again, the latest drawing data will be used to update the estimate in ServiceTitan.

The push is automatically triggered at the following two points:

• Signed on Device: {Proposal Name} - Signed on Device.pdf

• eSigned: {Proposal Name} - eSigned.pdf

Where does the signed Proposal get placed

NOTE: The ServiceTitan integration requires an ArcSite resource to complete. Please contact your Customer Success Manager or reach out to support@arcsite.com.

Connecting to ServiceTitan in ArcSite requires 4 steps:

Walk through all of these Connection steps one by one here.

Details on why an ArcSite resource is required can be found below in the Account Permission Issue section of this document.

Once connected, you can map your individual ArcSite products to ServiceTitan items from the User Site > Settings > Integrations > Product Manager screen.

ArcSite supports connecting with three types of ServiceTitan items and allows creating and updating ServiceTitan item information in ArcSite.

There are certain pricing and cost considerations to take into account given how the two different softwares manage these objects. See the Environment Setup Considerations section below for more detail.

Walk through each of these Product Mapping steps one by one here.

ArcSite creates corresponding ArcSite projects through ServiceTitan's JobScheduled webhook event. The specific correspondence is as follows:

There are several considerations with regards to Price and Cost and how the Products and Items are set up on both Softwares. While ArcSite allows you to capture both a Price and Cost on any product, ServiceTitan does not in all cases.

By default, ServiceTitan does not support a Unit Price on Material Items.

Therefore we recommend setting a Unit Cost and the Pricing Method Calculated Price for any ArcSite Products that will be matched with a ServiceTitan Material Item, unless that Item has the materials Chargeable feature enabled.

ServiceTitan does not support a Unit Cost on Service Items.

Therefore we recommend setting a Unit Price and the Pricing Method Input Price For any ArcSite Products that will be matched with a ServiceTitan Service Item.

Some existing ServiceTitan Services or Equipment items may already be associated with Materials. In this context, inconsistencies can arise in both the ArcSite drawing and line items and the pricing defined in ServiceTitan.

This is because services with associated materials or equipment will automatically add the associated materials or equipment when added to an estimate. The automatically added materials or equipment will carry their price and cost, which will lead to inconsistencies between the pushed estimate's line items and ArcSite's drawing line items if a product associated with such a services item is used in the drawing. Lastly, the estimate's price may not match ArcSite's total price.

Solution 1:

Try not to associate such services items, as they will result in unexpected estimate results. If such services items are associated and the estimate line items are expected to remain consistent with ArcSite, manually delete the associated equipment or materials lines after the estimate is created.

Solution 2:

To avoid affecting the estimate's total price, reasonably set the service's price. Set the prices and costs of the associated materials or equipment to 0, so they will not affect the estimate's total price.

Due to ServiceTitan's authorization process and tenant system's unique characteristics, users cannot independently complete the account connection work. It must be completed in conjunction with an ArcSite resource.

Specifically obtaining the user's Tenant ID and adding it to the ArcSite App cannot be completed independently.

ServiceTitan has strict control over account permissions. The tenant account in ServiceTitan associated with ArcSite needs to have admin privileges. The integration functionality in ArcSite will involve the following permissions:

If the integrated account lacks any of these permissions, it will cause abnormalities in the integration functionality.

Currently, a ServiceTitan tenant can only correspond to one ArcSite company in ArcSite.

ArcSite needs to determine which ArcSite company to create the project for when processing the tenant's JobScheduled webhook.

If a tenant is associated with multiple companies, it cannot determine the project's affiliation, and even if projects are created in multiple companies, changes to any company's project are pushed to ServiceTitan, causing data confusion.

By default, whenever a new drawing version is uploaded to the cloud, ArcSite will automatically push the latest Drawing PDF to the corresponding job in ServiceTitan.

When a project is associated with a job, if there are multiple drawings under the project, by default, whenever there is an update to the drawings in the project and it is uploaded to the cloud, the latest Drawing PDF of the corresponding drawing will be pushed to the job.

So if there are multiple drawings under the project and frequent updates, there will be the same number of attached PDFs in the corresponding job in ServiceTitan.

Each drawing version will correspond to an attachment PDF. This is because the ServiceTitan API does not support deleting and modifying attachments, so users can only manually maintain these attachments.

By default, a drawing version will only push a Drawing PDF to ServiceTitan once.

The filename of the pushed attachment is "Drawing Name.pdf".

ArcSite project always have a Project Owner. In the context of the ServiceTitan integration, that owner will be the Default Owner set during the connection setup.

Technicians will not be assigned as the project owner. However Technicians will be added as collaborators on the project, giving them access and editing permissions.

NOTE - The Project Owner in ArcSite does not carry any functional business logic, it simply indicates the project creator.

If Technicians are specified within Servicetitan, ArcSite will check and attempt to add them one by one as Project Collaborators. For each Technician, if their email matches an active ArcSite user account with the same username within the same company, they will be successfully added as a Collaborator. If this condition is not met, the addition of that Technician will fail.

When pushing an Estimate, because ServiceTitan requires that all products used in the Drawing must be associated with a ServiceTitan Product, if there are any products in the Drawing that are not associated with a ServiceTitan Product, the push process will be interrupted, and an error message will be returned to the user.

Error Message seen

Failed to Push Line Items from (Job: Drawing 1 - v2) for ServiceTitan Integration Testing: Some products used in this drawing are not connected to ServiceTitan: Service Product Non Taxable

Solution:

Map all ArcSite products to ServiceTitan product from the Integration > Product Manager screen on the ArcSite User Site.

ArcSite requires a unique name for each project. If a project creation request uses an existing name, it will fail.

Solution: Ensure project names are unique when pushing from ServiceTitan.

ArcSite uses ServiceTitan's discounts and fees features to complete the mapping of estimates' discounts and markups.

ArcSite will check if the corresponding discount item and fee item have been created in ServiceTitan when pushing estimates.

If not, it will create them and create the corresponding taxable discount item and non-tax discount item according to whether it is taxable.

Their codes are:

Do not delete from within ServiceTitan, or errors will occur.

ArcSite uses ServiceTitan's Equipment to map custom pricing line items added in the app.

ArcSite will check if the corresponding custom item has been created in ServiceTitan when pushing estimates. If not, it will create them and create the corresponding taxable item and non-tax item according to whether it is taxable.

Their codes are:

Please do not delete them in ServiceTitan, or it will cause push abnormalities.

Proposal PDFs can be pushed repeatedly.

By default, their push can be initiated on the User Site and in the pop-up window after exporting Proposal PDFs in the app. Each Drawing Version will only push one Proposal PDF to the Job. ArcSite will check if a Proposal PDF has already been pushed for that specific Drawing Version, and if it has, it will not push it again. Therefore, each Drawing Version will only push one Proposal PDF.

The filename of the attachment PDF is the same as the filename of the exported Proposal PDF.

In ArcSite, each project needs a definite owner. When connecting to ServiceTitan, the page will need to specify the project owner. This owner will act as the owner of all projects created from ServiceTitan.

Projects will be visible to the owner, project manager and collaborators.

Sales representative information will come from the selected technicians. If no technician is specified when booking a job, the sales rep information will not be filled.

If multiple technicians are selected when booking a job, ArcSite will check whether the emails of these specified technicians already exist as ArcSite accounts, and these accounts also need to exist in the company's project. These existing ArcSite accounts will be added to the project's collaborator list, and they will have access to the project.

ArcSite uses the JobScheduled Webhook event from ServiceTitan to create associated ArcSite Projects, which is the foundation of the integration. Users need to request the ServiceTitan API Team to enable the Webhook settings for their environment. Provide the following information to the ServiceTitan API Team:

The ServiceTitan API Team email: integrations@servicetitan.com

The Tenant ID is a unique identifier for the user in the ServiceTitan system, and ArcSite uses this ID to communicate with ServiceTitan. To obtain the Tenant ID, follow these steps: