Skip to main content

How-To: Configure Reservice & Driving Score Metrics - Applause Scorecards

What is needed to configure the driving score metric with your fleet integration provider and your reservice metric

Reservice Metric:

  • To enable Reservice metrics in Scorecards, we just need your designated "re-service" codes used in your CRM. These are the service types that represent a reservice, callback or recall jobs. Whatever you consider to be these services, these will be the ones that we enter in your location and integrations section.

    1. To configure reservice job types, go to Location → Integrations and set the appropriate service codes. We can work on this together and ensure these are input correctly, as they vary by CRM integration. Connect with a support agent if we can help with this.

    * If a customer has an active CRM, but has not yet configured the reservice field, it will result in the metric being displayed as “No Data”

  • Q: How do I know what my ID is for my CRM?

    A:

    • PestPac - Service Code IDs

    • Realgreen - Service Code IDs

    • Jobber API - visit.job.title

    • Fieldroutes API - Service Type IDs

    • Housecall pro - No support for reservice codes

    • Evolve - ServiceType

    • Senske - ServiceType

    • Evolve - ServiceType

    • Affiliated Tech - ServiceType

    • Gorilla Desk - Job Name

    • Service Titan - Job Type

    • Aspire - Service Type

    • Service Pro - Service or Event name

    • Service minder - Appointment name

    • Pool Brain - Service Type (title)

    • Service fusion - Job service

    • Fieldroutes Webhook - ServiceType - code ID number

    • FieldWork - ServiceType name

If you need help finding out your code ID from your CRM, please reach out to us!


​Driving Score Metric:

Driving scores in ApplauseHQ rely on data from external systems such as telematics providers. These systems must be integrated with ApplauseHQ using API tokens or fleet integration IDs. Once set up, the data flows seamlessly into the platform, enabling accurate score calculations.

Steps for Setting Up External System Integration

1. Generate and Configure API Tokens (Linxup)

If you are using Linxup as your telematics provider, follow these steps:

  1. Generate an API Token: Log in to the Linxup portal as the business owner and create an API token. Ensure the token is set to never expire.

  2. Enter the API Token in ApplauseHQ: Navigate to the Location Integration – Fleet field in ApplauseHQ and input the API token.

  3. Link Driver Names: Copy each technician’s Driver Name from Linxup and add it to the Associate Fleet Management ID field in the corresponding ApplauseHQ user profile. Typically, this is the technician’s username.

2. Set Up Fleet Integration IDs (Samsara)

For Samsara users, the fleet integration ID must be configured to link the technician’s profile to the driving integration. Here’s how:

  1. Locate the Driver’s Username in Samsara: Access the Drivers section in Samsara to find the username associated with the technician.

  2. Add the Fleet Integration ID in ApplauseHQ: Input the fleet integration ID into the technician’s user profile in ApplauseHQ. This step ensures that driving scores are calculated and displayed correctly. Having a driving score integration is a part of our pro plan, so it can be subject to an additional cost.

Troubleshooting Common Issues

If driving scores are not appearing on the scorecard, consider the following:

  • Missing or Incorrect Integration ID: Ensure that the fleet integration ID or API token is correctly entered in the technician’s user profile.

  • Expired API Token: Verify that the API token (for Linxup) is set to never expire.

  • Unlinked Driver Names: Check that the Driver Name from the external system matches the Associate Fleet Management ID in ApplauseHQ.

External System-Specific Notes

  • Linxup: Ensure the API token is generated by the business owner and set to never expire.

  • Samsara: Use the Drivers section to locate usernames and ensure they are correctly linked in ApplauseHQ.

Did this answer your question?