Clarifying the default decline reasons (or "campaign checks")

Clarifying the default decline reasons (or "campaign checks")

I can confirm that the following decline reasons (or "campaign checks") are defaults and are baked into the system:

  • Name check (which is, for example, "Applicant/Passport Mismatch")
  • DOB check (which is, for example, "The age of the participant does not match the Terms and Conditions")
  • Dupe check (which is, for example, "Participant Dupe")
But, unhelpfully, these will not appear in the list of "campaign checks" for a campaign in the backoffice :-/

Also note that these are defaults for *all* validation stages of a campaign. So, two-step campaigns will get these checks when approving s1v ('step 1 verify') and three-step campaigns will get these checks when approving both s1v and s2v.

UPDATE (09/04/2018):

Flights team have reduced and clarified the decline reasons that they want to go forward with (see attached file).
The master plan going forward is:

[1] Ignore historical data
[2] Ignore baked-in default checks (*)
[3] Go forward with new decline reasons
[4] Success!

(*) Which may or may not cause headaches - watch this space - (UPDATE no problems so far)

Here is how (a sample of) the new campaign checks have been defined in the backoffice database (the category in the attached Excel has been prefixed onto the check name):

----
Hi Pete,

 

I have add the following rejection codes for Thule campaign:

 

g_3rd_party_transfer

g_affiliate

g_id_invalid

g_id_illegible

g_id_missing

g_non_resident

g_outside_promo_period

g_outside_oa_period

pop_illegible

pop_missing

g_mismatch_name_code

g_mismatch_name_travel_id

g_name_duplicate

g_dob_invalid

pop_invalid_product

pop_invalid_retailer

 

g = GLOBAL category

 

Please can you update your list using the following format.

 

Thanks,

 

John.

----


UPDATE (30th April 2018):

Have had the idea myself, but have also heard from Isabella about "hiding" the now-defunct default decline reasons wherever they manifest themselves in the backoffice. Especially the "application declined" email template, and the actual decline tickbox screen for the agents. (see Zoho ticket #


    • Related Articles

    • Discouraged characters in campaign application codes

      Certain characters cause problems when they are used - or input - as part of an application code. The following table lists all known problematic characters and why they are discouraged: CHARACTER DISCOURAGEMENT REASON space internal technical ...

    • What the different "Campaign greet formality" settings look like

      What the different "Campaign greet formality" settings look like We can control the email salutation via the "Campaign greet formality" option of the campaign editor in the backoffice. Here is what the email salutation will look like for each setting ...

    • [CAMPAIGNS] Code entry box not honouring campaign start / stop dates

      Hello Isabella, Yes, the campaign dates issue for when we don't pre-bank the codes is already in this Zoho ticket Kind regards, Daniel --------------------------------------------------------------------- Hi Isabella, (1) only seems to happen for ...

    • Clarifying the different settings for “Christmas unblock”

      Here is a clarification on the different settings for “Christmas unblock”: Current settings (as of 18/01/2018) and what they mean NO RESTRICTION = no restriction: all blocks removed / nothing blocked "Cannot travel during Christmas" = blocked from ...

    • An improvement (the actual spec?) for rejection stages

      ---- Hi Dev team, Mareike has reported an additional error in the back office stages on Stoneleigh. Please see below for her report on the issue: as discussed for Stoneleigh we should have two rejection stages:   For awaiting PDF mail ( 1st stage) it ...