Advanced Tag Options (Compilers)

Community Tags  are Tags which ask the same consistent set of questions for every user in the compiler. They are very useful in CRM systems, where they can be configured as part of a general template and ‘read’ the account to which they need to be allocated from the CRM data. They are created centrally, and then appear in an identical form within each account attached to your compiler. These are very useful when you wish to:

Maintain a common approach to customers – Community Tags ask the same questions and work the same way irrespective of who is using them. The ‘owner’ of the compiler can create a community Tag from their own account, and can edit it to work as they require, and each copy of that Tag is then fixed in each person’s account, and can be downloaded, but can neither be edited or deleted. Thus a customer gets exactly the same feedback request irrespective of who is serving them.

Use Tags as part of a CRM or data based system – versions of the same Community Tags all have identical links, with the exception of the user’s alias or email address. This makes them very easy to use in CRM or data-based systems. For more information on how Community Tags can be used in this way, please download our guide.

Understand performance on the same activity across several groups  – because all copies of a community Tag ask precisely the same questions, they can be summed and averaged across different groups within your compiler at a detail level. This is very useful to track the progress of a business-wide change initiative, or to look at aspects of culture which should be common to every area.

Creating a Community Tag is an identical process to creating a normal Tag but within the ‘Community’ tab, rather than the ‘Personal’ tab. However (except in exceptional circumstances) it can only be done by the owner of the compiler, who will see a blue ‘NEW TAG’ button at the bottom of the list of Community Tags. If you are in the ‘Community’ tab, and you scroll down, and you cannot see the blue button, you do not have permission to create a Community Tag, and you will need to talk to your compiler owner.

At present, these further developments of the Community Tag are best configured by us, but new developments on the horizon will enable you to configure these things directly. In the meantime, if you wish to make use of any of the following, please contact us.

Self-AutoTags, or Pulse Tags – these can be sent to every user in any section (or all) of the compiler on a scheduled basis, and be used to update each individual’s self-score (useful for pursuing culture change, and in training) or to update a central Tag (useful for gathering feedback on cultural aspects).

Secure Tags – these can only be responded to under pre-defined conditions by bona-fide members of your compiler (or other pre-defined individuals) and can increase response security/confidence where that may be an issue.

Tracked Tags – these Tags contain coding that enables you to track their progress and thereby understand response rates and identify those partners you need to work with to increase your response rates.

Root Cause Analysis – this system of Tags enable your staff to attribute performance variations in their own Tags to the key factors which enabled (or undermined) that performance. This enables you to cascade performance back down the supply chain, and equip your support and indirect functions with the data to improve their own performance.

Response Page Options – these configure your Tags’ response pages to carry your own logo, and/or to emphasise different parts of the response page depending on the initial response from the respondent.

Enhanced Tags – these Tags enable you to gather further bespoke contextual information from the respondent.