> 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.4-changes-overview/contact-tag-enhancements.md). # Contact Tag Enhancements We have added a default contact tag option to make using contact tags on work items faster and easier. You can now set up a default tag value for an individual contact record, for example: If you know that 'Jane Smith' is always going to be the Broker on any work item she's added to as a contact, you can give Jane's Contact record a default tag of 'Broker' so it gets auto-populated for her in the work item - rather than you having to manually set this tag value each time. The Default Tags list of available options is maintained in Builder in the [General Settings >> Contact Tags](https://docs.enate.net/enate-help/builder/builder-2021.1/system-wide-settings/contact-tags) section. You can set this Default Tag whenever you add a new contact into the system. ![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FVIfDrLegb8BH1Dq2yi63%2Fimage.png?alt=media\&token=e87e099a-e6c2-4a5e-b327-e544cae2c4a5) You can also set the Default Tag when editing a contact via the Contacts page. ![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FfSxvjLPOd0hlYm0WmJpT%2Fimage.png?alt=media\&token=8b049d54-1f78-4cb2-a6da-4f31dd894ffa) The Default Tag attribute is also available to edit in bulk, i.e. you can set this for multiple contacts at one time - simply select a number of contact records when you're in the Contacts page grid and click on the Edit button to access the Bulk Edit popup. ![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FA9ao5l2jM3sVvixnPzkY%2Fimage.png?alt=media\&token=da996df8-862f-4d2a-9b1e-ddfa0d454740) Note that there can only be one Default Tag value set per contact record. Additionally, when a work item is created from the 'Start work item' button on the [Contact Activity Page](broken://pages/-MWqMpejnkCxXtGXw015), that contact will be tagged as the Requester, Subject and Primary Contact of the work item. Additionally their Default Tag will be added too (if they have one). #### Default Contact Tag behaviour if set not to 'Allow Multiple' If a specific tag value has not been set to 'Allow Multiple', only one contact in a Work Item is allowed to have the value. Example: it may be that there can be only a single 'Broker' contact for a Ticket. This obviously impacts default tagging if two contacts with the same 'must be unique' Default Tag get added to a work item, either manually or automatically. In this scenario the system will allocate the Default Tag to only one contact (and therefore remove the Default Tag for the other contacts). The system will allocate to the Contact already tagged with an existing *other* tag value, in the following priority order. * Primary Contact * Requester * Subject * CC * Any other contact on the work item **Additional notes about Supplier Company mismatches with Contact Tags:** * You will not be able to add a Default Tag to a contact if the company they are assigned to has a different Supplier Company to the Default Tag. * You will not be able to submit a work item with a contact whose Default Tag is set to a different Supplier Company than the work item. --- # 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.4-changes-overview/contact-tag-enhancements.md?ask=&goal= ``` `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.