Curious to know how other Programs users set up their Default variant? In any other tool I've used, the default is exactly that, a default and shouldn't have any filters assigned.
Gainsight specifically advises to add a filter to capture anyone that doesn't meet the filters of the other variants - even though there is a checkbox to defer anyone not matching the criteria to receive the default. Depending on how complex those filters get, it would be pretty hard to capture all 'other' participants in some scenarios.
I've never set a Default filter because the default version should rarely ever be sent since participants should meet the criteria of the other filters. Is this how others use it as well?
Solved
How are other users configuring Email Variants?
+3Best answer by diane_morneau
We never put a filter on the default variant.
We often use variants for language support. The default is used for English correspondents and any correspondent for which we do not have a localized variant that match their language. Each variant is associated with a language code. When a contact does not match the defined languages, they receive their e-mail in English. It does have tokens but they all have defaults if not filled.
On a few occasions, we used variants for other purposes like service consumption - we have put the most common case as default and defined specific letter variations as variants as needed for the consumption we are addressing.
We use the default for the current communication for repeating communications. From one month to another, we clone the current to a new variant to track past communications - since their tokens are not set up, they will not run off. Then, we edit the default variant with the new text ensuring its tokens remain intact. This way we have in the template the past communications for the year. We set up a new template per year. There is a limit of 18 variants per template.
We often use variants for language support. The default is used for English correspondents and any correspondent for which we do not have a localized variant that match their language. Each variant is associated with a language code. When a contact does not match the defined languages, they receive their e-mail in English. It does have tokens but they all have defaults if not filled.
On a few occasions, we used variants for other purposes like service consumption - we have put the most common case as default and defined specific letter variations as variants as needed for the consumption we are addressing.
We use the default for the current communication for repeating communications. From one month to another, we clone the current to a new variant to track past communications - since their tokens are not set up, they will not run off. Then, we edit the default variant with the new text ensuring its tokens remain intact. This way we have in the template the past communications for the year. We set up a new template per year. There is a limit of 18 variants per template.
+5We do not often configure the filter of the default variant because we typically want anyone who doesn't meet the fitler for other variants to receive the default and it would be more time consuming to specify all the scenarios that the default would apply to.
We never put a filter on the default variant.
We often use variants for language support. The default is used for English correspondents and any correspondent for which we do not have a localized variant that match their language. Each variant is associated with a language code. When a contact does not match the defined languages, they receive their e-mail in English. It does have tokens but they all have defaults if not filled.
On a few occasions, we used variants for other purposes like service consumption - we have put the most common case as default and defined specific letter variations as variants as needed for the consumption we are addressing.
We use the default for the current communication for repeating communications. From one month to another, we clone the current to a new variant to track past communications - since their tokens are not set up, they will not run off. Then, we edit the default variant with the new text ensuring its tokens remain intact. This way we have in the template the past communications for the year. We set up a new template per year. There is a limit of 18 variants per template.
We often use variants for language support. The default is used for English correspondents and any correspondent for which we do not have a localized variant that match their language. Each variant is associated with a language code. When a contact does not match the defined languages, they receive their e-mail in English. It does have tokens but they all have defaults if not filled.
On a few occasions, we used variants for other purposes like service consumption - we have put the most common case as default and defined specific letter variations as variants as needed for the consumption we are addressing.
We use the default for the current communication for repeating communications. From one month to another, we clone the current to a new variant to track past communications - since their tokens are not set up, they will not run off. Then, we edit the default variant with the new text ensuring its tokens remain intact. This way we have in the template the past communications for the year. We set up a new template per year. There is a limit of 18 variants per template.
+3Thanks John and Diane - that confirms how I've been using it as well. I thought the feedback I received was odd - that I had to set a default filter so I'm glad to see others' experience.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.