> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.3-changes-overview/improvements-to-contact-tags.md).

# Improvements to Contact Tags

## New Contact Tag Allocation Method

We've added a new Allocation method in Builder: You can now allocate work based on Contact Tags. You do this by selecting the 'Contact Tags' option from primary or secondary allocation method dropdown in the allocation window. 

![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FV0iuAWdKczk761fV4oRa%2Fimage.png?alt=media\&token=50b0aafc-bdc0-4739-ae9b-38312868f25a)

You then choose which specific contact tag value you would like that piece of work to be assigned to from the 'Contact Tag' dropdown. 

![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FYYQIEgcf4Q1L0Vz17hzz%2Fimage.png?alt=media\&token=5827ed76-8e3e-48b4-a02c-755730eba561)

The list of contact tags you can choose from are defined in the [General Settings section of Builder](https://docs.enate.net/enate-help/builder/builder-2021.1/system-wide-settings#contact-tags).

At runtime, the system will look for users associated with the work items which have been tagged with the configured user type tag, and allocate the work to them. If multiple users share this tag, the system will select the user with the least amount of work items in their inbox to allocate to.

## Global Contact Tags

You now have the option to set Contact Tags as global so they can by used by any service agent, regardless of their Supplier Company. You can do this when adding a new [Contact Tag in the General Settings section of Builder](https://docs.enate.net/enate-help/builder/builder-2021.1/system-wide-settings#contact-tags) and leaving the Supplier Company field blank. The Contact Tag will then be classed as global and can be used by any service agent, regardless of their Supplier Company.

![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FVSP6eGZvtstQxngTCm3f%2Fimage.png?alt=media\&token=d3e6080b-c0d7-437e-aae2-b010bc417c02)

If you do select a Supplier Company, the Contact Tag can only be used by service agents with the same Supplier Company.

{% hint style="info" %}
Please note that the Supplier Company cannot be changed after the Contact Tag has been added.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.3-changes-overview/improvements-to-contact-tags.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.