Skip to main content
All CollectionsAdvanced Topics
Configuring the ResponseScore background job
Configuring the ResponseScore background job
Michael Fatica avatar
Written by Michael Fatica
Updated over a month ago

The ResponseScore background job calculates a response score for each location based on lead interaction data. The score considers response rate, response time, and lead volume, and it updates a specified in your data.

Configuring the ResponseScore Job

  1. Create a new Job under Background Jobs.
    ​

  2. Choose ResponseScore as the job type

  3. Provide a Job Name

  4. Provide The following required arguments as described below.

Arguments

The background job accepts the following arguments:

Arguments

1. destination_field

  • Description: The database field in the locations table where the calculated response scores will be stored.

  • Required: βœ… Yes

  • Usage: Provide the safe name of the database field. If this field does not exist, it should be created as a "Numeric, Decimal" field.

  • Validation:

    • If not provided, the job will terminate with an error: "destination_field is required."

    • If the specified field does not exist in the locations table, the job will terminate with an error: "<destination_field>... does not exist in the locations table."


3. response_rate_weight

  • Description: The weight applied to the response rate component of the score calculation.

  • Default Value: 0.7

  • Type: double

  • Usage:

    0.8

4. response_time_weight

  • Description: The weight applied to the normalized response time component of the score calculation.

  • Default Value: 0.2

  • Type: double

  • Usage:

    0.3

5. lead_volume_weight

  • Description: The weight applied to the adjusted lead volume component of the score calculation.

  • Default Value: 0.2

  • Type: double

  • Usage:

    0.1

6. max_lead_acknowledgement_time

  • Description: The maximum acceptable lead response time, used to normalize response times.

  • Default Value: 5000 (milliseconds)

  • Type: integer

  • Usage:

    5000

7. lookback_days

  • Description: The number of days to look back when analyzing lead data.

  • Default Value: 90

  • Type: integer

  • Usage:

    60

Did this answer your question?