tech problem

5 posts, 0 answered
  1. Decided
    Decided avatar
    75 posts
    Registered:
    01 Dec 2017
    15 Jan
    Link to this post
    my quit date was jan 9  but my home page says 4 days quit
  2. marianne, quit coach
    marianne, quit coach avatar
    192 posts
    Registered:
    30 Nov 2017
    16 Jan
    Link to this post
    Hello Decided,

    Can you please connect with us through "contact us" so we can troubleshoot with you further.  

    Thank you,

    Marianne
  3. kyle @ smokers helpline
    kyle @ smokers helpline avatar
    49 posts
    Registered:
    28 Nov 2017
    16 Jan
    Link to this post
    Hi Decided,

    This is an issue that is affecting people in a few different ways, and it's due to the design of that dashboard widget. Currently, that section only updates at certain intervals post-quit date (1 day, 2 days, 3 days, 4 days, 10 days, 21 days, 1 month, 2 months, 1 year), because those were the periods for which we had concrete, evidence-based benefits that you would be experiencing after you quit. What we didn't consider was that there was no other counter available in that view to tell you the precise number of days you have been smoke-free. This is something we have in our plans for an upcoming update. We also have the ability to create new messages for additional periods post-quit date, and we intend to do that as well, where we can find relevant statistics (particularly in the post-1 year quit phase).

    I hope that clarifies things.
  4. petermac
    petermac avatar
    18 posts
    Registered:
    29 Nov 2017
    17 Jan
    Link to this post
    can  we  do something about the Lag.    ty
  5. kyle @ smokers helpline
    kyle @ smokers helpline avatar
    49 posts
    Registered:
    28 Nov 2017
    17 Jan in reply to petermac
    Link to this post
    Hey petermac,

    At the moment, we are working with internal staff and our vendor to identify the source of the lag. Our server logs indicate that we are using very little of the existing server loads, so simply bumping up service levels on those will have no impact. As soon as I have something more substantial to report on the slowness issue, I will, but for now, we're still actively working on finding a solution.
5 posts, 0 answered