Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usehatchapp.com/llms.txt

Use this file to discover all available pages before exploring further.

What does the ServiceTitan integration do?

Hatch offers a native integration with ServiceTitan that you can activate within the App Marketplace (located in your Hatch workspace). This integration syncs contact data from ServiceTitan to Hatch, and can also sync Hatch events to ServiceTitan. While active, the ServiceTitan integration will sync new and updated ServiceTitan data every 15 minutes. It will also sync Hatch events back to ServiceTitan as soon as they occur (if you have enabled this feature). To get started, open the App Marketplace in your Hatch workspace and follow the setup instructions below.

How do you set up the integration?

Requirements

You will need the following to set up the integration:
  • Hatch account with manager privileges
  • ServiceTitan account with admin privileges on your tenant

Setup Steps

Hatch now has an official ServiceTitan App! All users are required to utilize our official ServiceTitan application over a personal application (as per their API terms of use). The Hatch app automatically provides us with the permissions to read or update data in your ServiceTitan tenant. The scopes requested by our app cover all of the possible use cases in Hatch. For reference, the scopes are listed below in the FAQ section. The following is the set of steps required to activate the integration:
Before you begin, consider reviewing ServiceTitan’s documentation around managing client IDs and secrets. However, all of the necessary information is included in the instructions below.
  1. This first step is manual and will need to be completed in order to proceed with the rest of the setup steps. In order to make the Hatch app available for activation within your ServiceTitan instance, we will need to add your ServiceTitan Tenant ID to our ServiceTItan application. Please send your Tenant ID over to your onboarding representative to complete.
    1. _If you’re unsure where to find your Tenant ID, you can find it in ServiceTitan via Settings → Integrations → API Application Access
  2. Once the Hatch app has been activated for your tenant, you may proceed with setup. In Hatch, open the App Marketplace.
  3. Under the CRMs filter, click the Connect button for ServiceTitan.
  4. Proceed through the setup until you reach the connection configuration screen.
  5. Open the ServiceTitan instance that you want to connect to your Hatch workspace and navigate to SettingsIntegrationsAPI Application Access.
  6. Click the Connect New App button, accept the terms and conditions (if prompted), and select Hatch from the list of apps.
  7. With Hatch selected, click Connect.
  8. Scroll to the bottom of the screen that appears.
  9. In the restriction by booking provider option, choose No Restriction.
    1. This simply allows Hatch to post Bookings in ServiceTitan without restriction to a specific booking provider id.
  10. Click Allow Access.
  11. On the resulting Application Details screen, copy/paste the Tenant ID and the Client ID into the associated fields on the Hatch configuration screen.
  12. Click the Generate button next to Client Secret and then click Yes, Continue to generate the secret.
  13. Copy/paste the Client Secret into the associated field on the Hatch setup screen.
  14. You may now close any open ServiceTitan pages. All of the remaining steps are completed in Hatch.
  15. Enable the opportunity models you would like to sync with Hatch
    1. additionally select which related objects to include in the data model
  16. Configure your push communications preferences.
  17. Make sure to complete the full setup and click Finish in order to officially activate your Hatch integration.
    1. If successfully activated, the integration will begin syncing your last 90 days of data.

How to upgrade the ServiceTitan app

If an application is configured with incorrect scopes or an upgrade to the scopes is required to access new information, you will need to first edit the application in the ServiceTitan dev portal, and then upgrade the connected app within ServiceTitan. Upgrade the connected Hatch app to the new version:
  1. Login to your Service Titan account
  2. Manage API Application Access page: <https://go.servicetitan.com/#/Settings/Api-Apps>
  3. In the Hatch App, you should see a message informing about the scope update. Untitled (3)
  4. Click the “upgrade version” button and confirm.

Configuration Options

These options can be set during the integration setup: Choose the ServiceTitan data that syncs to Hatch:
  • Choose which opportunity models the integration should sync from ServiceTitan, and subsequently which data objects to include with the model. We will go into further detail regarding the data objects further down in this article in the section “What ServiceTitan data is available in Hatch?
  • Configure a filter for placeholder emails: if your org utilizes placeholder emails within your ServiceTitan, this filter will prevent contacts from merging in Hatch based on the shared information
Push Events and Communications:
  • Choose where outgoing campaign messages should sync — if/where Hatch should create ServiceTitan notes for outgoing campaign message events
  • Sync message content for outgoing campaign messages — if the message content should be included in notes created for outgoing campaign message events
  • Choose where incoming messages & calls should sync — if/where Hatch should create ServiceTitan notes for incoming messages & calls
  • Sync message content for incoming messages & calls — if the message content should be included in notes created for incoming messages & calls
  • Choose where outgoing manual messages & calls should sync — if/where Hatch should create ServiceTitan notes for outgoing manual messages & calls
  • Sync message content for outgoing manual messages & calls — if the message content should be included in notes created for outgoing manual messages & calls

Configuration Best Practices

  • We recommend utilizing the object selector feature in the data configuration to select only the information necessary for your campaigns. While the integration can sync a wide range of information that might seem relevant, it can also make it more difficult to pick out the pieces that are truly important and useable with your campaign strategies. Now you can customize what you want to sync. Read more about this feature here.

When does Hatch sync data to/from ServiceTitan?

ServiceTitan → Hatch

ServiceTitan data can be sync’d to Hatch in the following scenarios. These options are configured during the integration setup.
Keep in mind that syncs occur every 15 minutes for Job and Membership data. Completed calls sync instantly using ServiceTitan webhooks.
  • When a Job record is created or updated in ServiceTitan, Hatch syncs the Job record along with any associated data (see below for specific fields)
  • When a Membership record is created or updated in ServiceTitan, Hatch syncs the Membership record along with any associated data (see below for specific fields)
  • When a call is completed, Hatch syncs a record along with any associated data

Hatch → ServiceTitan

Automatically Book Jobs Users of Hatch AI can benefit from our calendar integration to automatically book jobs on your schedule. Learn more about how our ServiceTitan scheduler bot in our dedicated calendar integration article. Sync Communications Hatch events and/or communications can be sync’d to ServiceTitan in the following scenarios. These options are configured during the integration setup.
Keep in mind that push communications occur instantaneously. There must be a ServiceTitan record in Hatch at the time of the sync in order for it to succeed.
  • When a Hatch campaign sends a text/email/voicemail to a contact, Hatch creates a Note for the event on the associated Job, Customer, or Location
  • When a contact calls or sends a text/email/voicemail to a Hatch workspace, Hatch creates a Note for the event on the associated Job, Customer, or Location
  • When a Hatch user calls or sends a text/email to a contact, Hatch creates a Note for the event on the associated Job, Customer, or Location
  • When events occur within a Hatch campaign, Hatch creates a Note for the event on the associated Job, Customer, or Location
    • A contact is launched (added) to a Hatch campaign
    • A contact is sent the first message of a Hatch campaign
    • A contact is removed from a Hatch campaign before it has ended
    • A contact completed a Hatch campaign
Below is an example of push communications and push events sent to ServiceTitan Job Notes:

image (32)

How is ServiceTitan data stored in Hatch?

Opportunity Models

There are two types of Hatch opportunities that the ServiceTitan integration creates:
  • Job Opportunity — Created from ServiceTitan Job records, this is the primary opportunity type in our ServiceTitan integration. Additional related data is also included (see below).
  • Membership Opportunity — These opportunities are created from ServiceTitan Membership records. Additional related data is also included (see below).
  • Inbound Call Opportunity — These opportunities are created when a inbound call is completed in ServiceTitan.

Opportunity Creation & Update

When an opportunity is generated that doesn’t match an existing contact , a new contact will be created. A new opportunity will be added to an existing contact if a match is found.
The integration will replace an existing Hatch opportunity when:
  • The sync’d Hatch External ID matches the existing opportunity’s Hatch External ID (see below for how the External ID is mapped)
The integration will create an additional (new) Hatch opportunity when:
  • The sync’d Hatch External ID does not match the existing opportunity’s Hatch External ID (see below for how the External ID is mapped)

What ServiceTitan data is available in Hatch?

Selecting Object Resources

The latest version of our integration allows you to select the resources that are most relevant to your campaigns, instead of syncing all possible data by default. This customizability allows you (and your integration) to operate more efficiently. Each opportunity model has a certain set of required objects that are needed in order for some aspect of Hatch to function. The additional resources are optional. We have defaulted the configuration with the most commonly used optional resources, but users can select or deselect as needed. The resources available with a Job opportunity are:
  • Estimates — Necessary in order to utilize a sales follow-up strategy.
  • Appointments — Useful for appointment confirmation or canceled-appointment campaigns.
  • Appointment Assignments — Can only be enabled if Appointments is selected. Useful if you want technician information in your campaigns.
  • Cancel Reasons — Useful for canceled-appointments campaigns.
  • Tag Types — Useful for segmenting audiences based on existing ServiceTitan tags.
  • Campaigns — Useful for segmenting audiences based on existing ServiceTitan campaign attribution.
  • Zones — Useful for location-based targeting.
  • Employees & Technicians (Sold By) — Necessary if you need the estimate or membership Sold By information.
  • Invoices — Necessary for accounts-receivable campaigns or post-completion review/referral targeting. The resources available with a Membership opportunity are:
  • Recurring Services & Events — Aggregates the latest, next, and full list of recurring service events plus an unused-services count.
  • Tag Types — Same as above, applied to the membership’s customer.
  • Zones — Adds zone metadata to the membership’s location and recurring location.
  • Employees & Technicians (Sold By) — Adds the membership’s soldBy info.
  • Payment Type — Adds payment type metadata.

Available Resource Fields

The following fields are available in the Job opportunity details:
ResourceField NameData Type
Jobjob:idNumber
Jobjob:jobNumberString
Jobjob:jobStatusString
Jobjob:priorityString
Jobjob:noChargeBoolean
Jobjob:notificationsEnabledBoolean
Jobjob:createdOnDate
Jobjob:modifiedOnDate
Jobjob:completedOnDate
Jobjob:customFields:{name}String
Customercustomer:idNumber
Customercustomer:nameString
Customercustomer:typeString
Customercustomer:activeBoolean
Customercustomer:doNotServiceBoolean
Customercustomer:contacts:#:idNumber
Customercustomer:contacts:#:typeString (Email, Phone, MobilePhone, Fax)
Customercustomer:contacts:#:valueString
Customercustomer:contacts:#:phoneSettings:doNotTextBoolean
Customercustomer:tagTypes:#:idNumber
Customercustomer:tagTypes:#:nameString
Customercustomer:tagTypes:#:activeBoolean
Customercustomer:customFields:{name}String
Business UnitbusinessUnit:idNumber
Business UnitbusinessUnit:nameString
Business UnitbusinessUnit:officialNameString
Business UnitbusinessUnit:activeBoolean
Job TypejobType:idNumber
Job TypejobType:nameString
Campaigncampaign:idNumber
Campaigncampaign:nameString
Campaigncampaign:activeBoolean
Locationlocation:idNumber
Locationlocation:nameString
Locationlocation:activeBoolean
Locationlocation:address:streetString
Locationlocation:address:unitString
Locationlocation:address:cityString
Locationlocation:address:stateString
Locationlocation:address:zipString
Locationlocation:address:countryString
Locationlocation:address:latitudeNumber
Locationlocation:address:longitudeNumber
Zonelocation:zone:idNumber
Zonelocation:zone:nameString
Tag TypestagTypes:#:idNumber
Tag TypestagTypes:#:nameString
Tag TypestagTypes:#:activeBoolean
Appointmentsappointments:#:idNumber
Appointmentsappointments:#:appointmentNumberString
Appointmentsappointments:#:statusString
Appointmentsappointments:#:startDate
Appointmentsappointments:#:endDate
Appointmentsappointments:#:arrivalWindowStartDate
Appointmentsappointments:#:arrivalWindowEndDate
Appointmentsappointments:#:specialInstructionsString
Appointmentsappointments:#:createdOnDate
Appointmentsappointments:#:modifiedOnDate
Appointment Assignmentsappointments:#:appointmentAssignments:#:idNumber
Appointment Assignmentsappointments:#:appointmentAssignments:#:technicianIdNumber
Appointment Assignmentsappointments:#:appointmentAssignments:#:technicianNameString
Appointment Assignmentsappointments:#:appointmentAssignments:#:assignedByIdNumber
Appointment Assignmentsappointments:#:appointmentAssignments:#:assignedOnDate
Appointment Assignmentsappointments:#:appointmentAssignments:#:statusString
Appointment Assignmentsappointments:#:appointmentAssignments:#:isPausedBoolean
Cancel ReasonscancelReasons:#:reasonIdNumber
Estimatesestimates:#:idNumber
Estimatesestimates:#:nameString
Estimatesestimates:#:summaryString
Estimatesestimates:#:activeBoolean
Estimatesestimates:#:subtotalNumber
Estimatesestimates:#:status:valueNumber
Estimatesestimates:#:status:nameString (Open, Sold, etc.)
Estimatesestimates:#:soldOnDate
Estimatesestimates:#:createdOnDate
Estimatesestimates:#:modifiedOnDate
EstimatesopenEstimatesNumber (count)
EstimatesopenEstimatesSubtotalString (decimal)
EstimatessoldEstimatesNumber (count)
EstimatessoldEstimatesSubtotalString (decimal)
Sold By (Employee/Technician)estimates:#:soldBy:idNumber
Sold By (Employee/Technician)estimates:#:soldBy:nameString
Sold By (Employee/Technician)estimates:#:soldBy:emailString
Sold By (Employee/Technician)estimates:#:soldBy:activeBoolean
Invoicesinvoices:#:idNumber
Invoicesinvoices:#:summaryString
Invoicesinvoices:#:referenceNumberString
Invoicesinvoices:#:invoiceDateDate
Invoicesinvoices:#:dueDateDate
Invoicesinvoices:#:subTotalNumber
Invoicesinvoices:#:totalNumber
Invoicesinvoices:#:balanceNumber
Invoicesinvoices:#:invoiceType:idNumber
Invoicesinvoices:#:invoiceType:nameString
Invoicesinvoices:#:customer:idNumber
Invoicesinvoices:#:customer:nameString
Invoicesinvoices:#:termNameString
Invoicesinvoices:#:depositedOnDate
Invoicesinvoices:#:createdOnDate
Invoicesinvoices:#:modifiedOnDate
Invoicesinvoices:#:adjustmentToIdNumber
Invoicesinvoices:#:projectIdNumber
Invoicesinvoices:#:employeeInfo:idNumber
Invoicesinvoices:#:employeeInfo:nameString
Invoicesinvoices:#:employeeInfo:modifiedOnDate
Invoicesinvoices:#:assignedTo:idNumber
Invoicesinvoices:#:assignedTo:nameString
Invoicesinvoices:#:sentStatusString
Invoicesinvoices:#:reviewStatusString
Invoicesinvoices:#:syncStatusString
Invoicesinvoices:#:items:#:idNumber
Invoicesinvoices:#:items:#:displayNameString
Invoicesinvoices:#:items:#:membershipTypeIdNumber
Invoicesinvoices:#:items:#:serviceDateDate
Invoicesinvoices:#:items:#:modifiedOnDate
Invoicesinvoices:#:customFields:#:nameString
Invoicesinvoices:#:customFields:#:valueString
The following fields are available in the Membership opportunity details:
ResourceField NameData Type
Membershipmembership:idNumber
Membershipmembership:statusString
Membershipmembership:followUpStatusString
Membershipmembership:activeBoolean
Membershipmembership:fromDate
Membershipmembership:toDate
Membershipmembership:followUpOnDate
Membershipmembership:cancellationDateDate
Membershipmembership:nextScheduledBillDateDate
Membershipmembership:billingFrequencyString
Membershipmembership:renewalBillingFrequencyString
Membershipmembership:durationNumber
Membershipmembership:renewalDurationNumber
Membershipmembership:initialDeferredRevenueNumber
Membershipmembership:memoString
Membershipmembership:createdOnDate
Membershipmembership:modifiedOnDate
Customercustomer:idNumber
Customercustomer:nameString
Customercustomer:typeString
Customercustomer:activeBoolean
Customercustomer:doNotServiceBoolean
Customercustomer:contacts:#:idNumber
Customercustomer:contacts:#:typeString
Customercustomer:contacts:#:valueString
Customercustomer:contacts:#:phoneSettings:doNotTextBoolean
Customercustomer:tagTypes:#:idNumber
Customercustomer:tagTypes:#:nameString
Customercustomer:tagTypes:#:activeBoolean
Customercustomer:customFields:{name}String
Business UnitbusinessUnit:idNumber
Business UnitbusinessUnit:nameString
Business UnitbusinessUnit:officialNameString
Business UnitbusinessUnit:activeBoolean
Membership TypemembershipType:idNumber
Membership TypemembershipType:nameString
Membership TypemembershipType:activeBoolean
Membership TypemembershipType:discountModeString
Membership TypemembershipType:locationTargetString
Membership TypemembershipType:revenueRecognitionModeString
Membership TypemembershipType:createdOnDate
Membership TypemembershipType:modifiedOnDate
Locationlocation:idNumber
Locationlocation:nameString
Locationlocation:activeBoolean
Locationlocation:address:streetString
Locationlocation:address:unitString
Locationlocation:address:cityString
Locationlocation:address:stateString
Locationlocation:address:zipString
Locationlocation:address:countryString
Locationlocation:address:latitudeNumber
Locationlocation:address:longitudeNumber
Zonelocation:zone:idNumber
Zonelocation:zone:nameString
Recurring LocationrecurringLocation:idNumber
Recurring LocationrecurringLocation:nameString
Recurring LocationrecurringLocation:activeBoolean
Recurring LocationrecurringLocation:address:streetString
Recurring LocationrecurringLocation:address:unitString
Recurring LocationrecurringLocation:address:cityString
Recurring LocationrecurringLocation:address:stateString
Recurring LocationrecurringLocation:address:zipString
Recurring LocationrecurringLocation:address:countryString
Recurring LocationrecurringLocation:address:latitudeNumber
Recurring LocationrecurringLocation:address:longitudeNumber
Recurring LocationrecurringLocation:zone:idNumber
Recurring LocationrecurringLocation:zone:nameString
Sold By (Employee/Technician)soldBy:idNumber
Sold By (Employee/Technician)soldBy:nameString
Sold By (Employee/Technician)soldBy:emailString
Sold By (Employee/Technician)soldBy:activeBoolean
Payment TypepaymentType:idNumber
Payment TypepaymentType:nameString
Recurring Service AggregationrecurringServiceAggregation:unusedServicesCountNumber
Recurring Service AggregationrecurringServiceAggregation:latestRecurringServiceEvent:dateDate
Recurring Service AggregationrecurringServiceAggregation:latestRecurringServiceEvent:statusString
Recurring Service AggregationrecurringServiceAggregation:latestRecurringServiceEvent:membershipIdNumber
Recurring Service AggregationrecurringServiceAggregation:latestRecurringServiceEvent:locationRecurringServiceIdNumber
Recurring Service AggregationrecurringServiceAggregation:latestRecurringServiceEvent:jobType:idNumber
Recurring Service AggregationrecurringServiceAggregation:latestRecurringServiceEvent:jobType:nameString
Recurring Service AggregationrecurringServiceAggregation:nextRecurringServiceEvent:dateDate
Recurring Service AggregationrecurringServiceAggregation:nextRecurringServiceEvent:statusString
Recurring Service AggregationrecurringServiceAggregation:nextRecurringServiceEvent:membershipIdNumber
Recurring Service AggregationrecurringServiceAggregation:nextRecurringServiceEvent:locationRecurringServiceIdNumber
Recurring Service AggregationrecurringServiceAggregation:nextRecurringServiceEvent:jobType:idNumber
Recurring Service AggregationrecurringServiceAggregation:nextRecurringServiceEvent:jobType:nameString
Recurring Service AggregationrecurringServiceAggregation:recurringServiceEvents:#:dateDate
Recurring Service AggregationrecurringServiceAggregation:recurringServiceEvents:#:statusString
Recurring Service AggregationrecurringServiceAggregation:recurringServiceEvents:#:membershipIdNumber
Recurring Service AggregationrecurringServiceAggregation:recurringServiceEvents:#:locationRecurringServiceIdNumber
Recurring Service AggregationrecurringServiceAggregation:recurringServiceEvents:#:jobType:idNumber
Recurring Service AggregationrecurringServiceAggregation:recurringServiceEvents:#:jobType:nameString
The following fields are available in the Inbound Call opportunity details:
ResourceField NameData Type
Callcall:idNumber
Callcall:eventIdString
Callcall:webhookIdString
Callcall:directionString (Inbound)
Callcall:callTypeString
Callcall:fromString (phone)
Callcall:toString (phone)
Callcall:durationString (HH:MM:SS)
Callcall:durationInSecondsNumber
Callcall:receivedOnDate
Callcall:modifiedOnDate
Callcall:recordingUrlString
Callcall:voiceMailUrlString
Callcall:reason:idNumber
Callcall:reason:nameString
Callcall:reason:leadBoolean
Callcall:reason:activeBoolean
Callcall:agent:idNumber
Callcall:agent:externalIdString
Callcall:agent:nameString
Callcall:createdBy:idNumber
Callcall:createdBy:nameString
Callcall:campaign:idNumber
Callcall:campaign:nameString
Callcall:campaign:activeBoolean
Callcall:campaign:sourceString
Callcall:campaign:otherSourceString
Callcall:campaign:mediumString
Callcall:campaign:otherMediumString
Callcall:campaign:businessUnitString
Callcall:campaign:dnisString
Callcall:campaign:createdOnDate
Callcall:campaign:modifiedOnDate
Callcall:campaign:category:idNumber
Callcall:campaign:category:nameString
Callcall:campaign:category:activeBoolean
Customercall:customer:idNumber
Customercall:customer:nameString
Customercall:customer:emailString
Customercall:customer:typeString
Customercall:customer:activeBoolean
Customercall:customer:balanceNumber
Customercall:customer:doNotMailBoolean
Customercall:customer:doNotServiceBoolean
Customercall:customer:hasActiveMembershipBoolean
Customercall:customer:importIdNumber
Customercall:customer:mergedToIdNumber
Customercall:customer:createdByNumber
Customercall:customer:createdOnDate
Customercall:customer:modifiedOnDate
Customercall:customer:address:streetString
Customercall:customer:address:streetAddressString
Customercall:customer:address:unitString
Customercall:customer:address:cityString
Customercall:customer:address:stateString
Customercall:customer:address:zipString
Customercall:customer:address:countryString
Customercall:customer:address:latitudeNumber
Customercall:customer:address:longitudeNumber
Customercall:customer:contacts:#:idNumber
Customercall:customer:contacts:#:typeString
Customercall:customer:contacts:#:valueString
Customercall:customer:contacts:#:memoString
Customercall:customer:contacts:#:activeBoolean
Customercall:customer:contacts:#:modifiedOnDate
Customercall:customer:phoneSettings:#:phoneNumberString
Customercall:customer:phoneSettings:#:doNotTextBoolean
Customercall:customer:memberships:#:idNumber
Customercall:customer:memberships:#:activeBoolean
Customercall:customer:memberships:#:statusString
Customercall:customer:memberships:#:fromDate
Customercall:customer:memberships:#:toDate
Customercall:customer:memberships:#:locationIdNumber
Customercall:customer:memberships:#:type:idNumber
Customercall:customer:memberships:#:type:nameString
Customercall:customer:memberships:#:type:activeBoolean
Customercall:customer:customFields:#:typeIdNumber
Customercall:customer:customFields:#:nameString
Customercall:customer:customFields:#:valueString
Tenantcall:__tenantInfo:idNumber
Tenantcall:__tenantInfo:nameString

Standard Field Mapping

Hatch standard fields are mapped from ServiceTitan detail fields as detailed below. Job Opportunity
The base object of this opportunity model is the ServiceTitan Job. Therefore, (as an example) the id field would indicate the ID of the ServiceTitan Job record.
In Job opportunities, the following Hatch standard fields are mapped from ServiceTitan detail fields:
Hatch Standard FieldServiceTitan Detail Field
EmailThe value of the first item in the customer:contacts list that has type equal to email
External IDid
External Contact IDcustomer:id
External Created AtcreatedOn
External Updated At
(used for Hatch opportunity sorting)The most recent date within these fields:
modifiedOnappointments:1:modifiedOn
estimates:1:modifiedOn
First NameIf there is no comma incustomer:name :
The first word in the customer:name value
If there is a comma incustomer:name :
All text after the first comma in the customer:name value
Last NameIf there is no comma in the customer:name value:
Everything after the first word in the customer:name value
If there is a comma in the customer:name value:
All text before the first comma in the customer:name value
PhoneThe value of the first item in the customer:contacts list that has type equal to mobilePhone
IF ABOVE IS MISSING: The value of the first item in the customer:contacts list that has type equal to phone
Membership Opportunity
The base object of this opportunity model is the ServiceTitan Membership. Therefore, (as an example) the id field would indicate the ID of the ServiceTitan Membership record.
In Membership opportunities, the following Hatch standard fields are mapped from ServiceTitan detail fields:
Hatch Standard FieldServiceTitan Detail Field
EmailThe value of the first item in the customer:contacts list that has type equal to email
External IDid
External Contact IDcustomer:id
External Created AtcreatedOn
External Updated At
(used for Hatch opportunity sorting)modifiedOn
First NameIf there is no comma incustomer:name :
The first word in the customer:name value
If there is a comma incustomer:name :
All text after the first comma in the customer:name value
Last NameIf there is no comma in the customer:name value:
Everything after the first word in the customer:name value
If there is a comma in the customer:name value:
All text before the first comma in the customer:name value
PhoneThe value of the first item in the customer:contacts list that has type equal to mobilePhone
IF ABOVE IS MISSING: The value of the first item in the customer:contacts list that has type equal to phone
Inbound Call Opportunity
Hatch Standard FieldServiceTitan Detail Field
Emailcall:customer:email
External IDcall:webhookId
External Contact IDcall:customer:id
External Created Atcall:receivedOn
External Updated Atcall:modifiedOn
First NameSame comma/space split rule as Job & Membership applied to call:customer:name
Last NameSame comma/space split rule as Job & Membership applied to call:customer:name
Phonecall:from
Statuscall:callType

What are the limitations of the integration?

  • The ServiceTitan API does not provide information related to the Job’s “Opportunity”, so Hatch is unable to target audiences based on the follow-up date or status.
We have a template library to help get you started on building audiences. These are what we’ve found works best to accomplish common use cases. Feel free to use these as a starting point for your own campaigns, but it’s always wise to evaluate what targeting strategy works best with your internal processes.

Speed to Lead (Removal Rules)

The goal in mind here is to remove contacts from the STL campaign when a job (appointment) has been scheduled in ServiceTitan. There are a couple ways to achieve this: ST appt removal rules

FAQ

The scopes are standardized via our official ServiceTitan application so they are not able to be customized. If there are any scopes your organization does not wish Hatch to have access to, many of the features are optional and can be turned off. In that case, the integration would not access the related scopes.

The following Read scopes are required:
  • Accounting: Invoices, Invoice Items, Payment Types, Tax Zones
  • CRM: Booking Provider Tags, Bookings, Customers, Leads, Locations, Tags
  • Dispatch: Appointment Assignments, Capacity, Non-Job Appointments, Zones
  • Job Planning and Management: Appointments, Job Cancel Reasons, Job Hold Reasons, Jobs, Job Types
  • Memberships: Customer Memberships, Membership Types, Recurring Service Events, Recurring Services, Recurring Service Types
  • Marketing: Campaigns, Campaign Categories
  • Sales & Estimates: Estimates
  • Settings: Business Units, Employees, Tag Types, Technicians, User Roles
The following Write scopes are required:
  • CRM: Customers, Leads, Locations
  • Dispatch: Capacity
  • Marketing: Campaigns
  • Job Planning and Management: Jobs, Appointments