Assignment and routing

Route by a territory table

Route records by configured country and segment territory rules while preserving existing owners.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Your selection stays with you through signup.

What it does

Case-insensitive trim matching, wildcard rules, conflict detection, fallback, and protected existing owner behavior matching the installed R013-1.0.0 release.

What to customize

Configure rules, fallbackOwnerId, and preserveExistingOwner using real owner IDs for production.

Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.

Expected outcome

This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.

Sample input

sample-input.json

{
  "inputFields": {
    "field1": "GB",
    "field2": "enterprise",
    "field3": ""
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "owner-gb",
    "output2": "routed",
    "output3": "1 matching rule(s)."
  }
}

Returned fields

output1: owner ID
output2: routed, fallback, preserved, ambiguous, invalid, or unmatched
output3: reason

What changes when it runs

Reads country field1, segment field2, and existing owner field3; returns routing decision and performs no CRM write.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe