Nina Ahrens
25 Nov 2019 05:13 PM ( 93 days ago )
Hi Daniel,
I believe it was generally for all step 3 applications.
With the rebuild this issue may be resolved anyway!?
As long as we can make sure that we can define our own SLA’s in the back office to determine due dates shown in the system, then all is good.
The issue here was that our SLA was 7 days (to validate the link response) but the system thought it was 14 days.
I can explain in details but I think it’s one of those issues created by “sticking on” this extra step and link to 2 step campaign to create 3 step campaigns.
Nina
---------------------------------------------------------------------
Daniel Rhodes
25 Nov 2019 01:31 PM ( responded in 103 days )
Hello Nina,
This is a very old ticket that is "ON HOLD", but I would just like to clarify if this shortcoming is just to do with "cron queue" scheduled emails OR you mean generally for all step 3 campaign applications?
Kind regards,
Daniel
---------------------------------------------------------------------
Nina Ahrens
13 Aug 2019 11:32 AM ( 198 days ago )
Hi Daniel,
re the due dates for link validation for:
Step 2 Ready to Verify (s2v)
we should have 7 days committed to the back office, not 14 (it is correct for Step 1 Ready to Verify (s1v) 0 7 days)
I wonder if the 14 days come from the 14 days we have to make an offer. When we verify Step 3 Ready to Verify (s3v) the time frame IS 14 days as this is how much time we have to send the offer.
Not sure if we can fix this or if this is a general short coming of the 3 step campaigns... If we can fix please do but otherwise i will let the team know to subtract 7 days from the due date as they have been doing so far.
thanks
Nina
Related Articles
[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 ...
[CAMPAIGNS] "Second applicant on same code" issue
Hi Daniel, John as discussed, I am raising this ticket, so that in a quiet moment (if there ever is one of those) we can have a look at the "Second applicant on same code" issue. Quick summary of issue: We know of a couple of occurrences at least, ...
All about demo codes for multi-tier campaigns
All about demo codes for multi-tier campaigns [Q1] Can demo codes be created for each tier (and how to do that)? [A1] TODO [Q2] Do the created demo codes *basically* work? [A2] TODO [Q3] Do the demo codes have the normal demo code behaviour (around ...
All about responsive banner sizes
All about responsive banner sizes All about responsive banner sizes for campaign sites. Usage patterns Tends to be one of the following: Every page of campaign site has same banner [used by some campaigns] "Home" or "landing" page has a particular ...
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 ...