PureCloud

Discussion Thread View
Expand all | Collapse all

Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

Louis Goh01-29-2018 01:59

  • 1.  Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    Posted 01-29-2018 01:59


  • 2.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    Posted 01-29-2018 02:04

    i have created a email flow to make the email interaction waiting until open schedule to transfer to ACD, it works in my test environment, but it is found that the email interaction only can stay in a flow for 3 hours, after 3 hours, it will disconnected automatically.

     

    So i have no idea to make it happen.



  • 3.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    GENESYS
    Posted 20 days ago
    Basically, the only thing that has been done so far is to increase the limit to 24 hours instead of 3. That enhancement was released a month or two ago.

    https://purecloud.ideas.aha.io/ideas/CLINB-I-252 and https://purecloud.ideas.aha.io/ideas/CLPLA-I-284 are a couple of related Ideas you can vote for

    ------------------------------
    George Ganahl GCP (PureCloud) ICCE CCXP
    Principal Technology Consultant
    Genesys
    ------------------------------



  • 4.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    Posted 16 days ago
    Hello George

    Thank you very much for your response.

    For my clarification please, does that mean using the "Wait" function in the architect, the email can only wait for 24 hours and will be disconnected if it is not sent to queue in-time?

    ------------------------------
    Thanks and regards
    Samuel Polgar
    CVT (Global) Pty Ltd
    ------------------------------



  • 5.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    GENESYS
    Posted 15 days ago
    Yes, that is correct. It used to be 3 hours before disconnect, now it is 24. Which does not get you through a full weekend.


    ------------------------------
    George Ganahl GCP (PureCloud) ICCE CCXP
    Principal Technology Consultant
    Genesys
    ------------------------------



  • 6.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    GENESYS
    Posted 13 days ago
    The email will not necessarily be disconnected if it exceeds the 24 hour window. It can be sent to an error queue at that point.

    ------------------------------
    Lucie DeCristofaro
    Genesys - Employees
    ------------------------------



  • 7.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    GENESYS
    Posted 13 days ago
    You are talking about the Error Event Handling, correct, Lucie?


    But, there is no way to automatically transfer emails from that error queue back over to the original queue...it would have to be done by someone picking them up and transferring to the main queue, or using the API (if that's possible...I haven't worked through whether it could be done). Is that correct?


    ------------------------------
    George Ganahl GCP (PureCloud) ICCE CCXP
    Principal Technology Consultant
    Genesys
    ------------------------------



  • 8.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    GENESYS
    Posted 12 days ago
    Yes, the email will be delivered to the error queue you define. The agents would pick it up from that queue.

    ------------------------------
    Lucie DeCristofaro
    Genesys - Employees
    ------------------------------



  • 9.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    GENESYS
    Posted 12 days ago
    Ok. Thank you!

    ------------------------------
    George Ganahl GCP (PureCloud) ICCE CCXP
    Principal Technology Consultant
    Genesys
    ------------------------------



  • 10.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    Posted 01-30-2018 15:29

    Email SLAs currently do not take into account open or closed hours. It's a feature we have in the backlog.



  • 11.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    Posted 01-31-2018 02:55

    will it be included in the road map 1q or 2q of 2018? any workaround(like do something in the email flow) for this currently?



  • 12.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    Posted 12-11-2018 04:54
    Hi all,
    any update on this feature?

    ------------------------------
    Sergio Picchioni
    Bizmatica Sistemi S.p.a.
    ------------------------------



  • 13.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    Posted 21 days ago
    Hello community

    Is there an update on this feature, please?

    ------------------------------
    Thanks and regards
    Samuel Polgar
    CVT (Global) Pty Ltd
    ------------------------------



  • 14.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    Posted 21 days ago
    We've been using purecloud for a few years now and have been pushing for this feature with no avail. Genesys did propose a work around about holding emails back and putting them in another queue untill a certain time but this wasn't practical.
    Emails are a truely weak feature of Purecloud and has caused a number of issues during our time in using it. Basic features such as cherry picking not being available causes us problems on a daily basis.

    ------------------------------
    sam spicer
    Curo Group
    ------------------------------



  • 15.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    Posted 16 days ago
    Hello Sam

    We are very much looking forward to the Cherry Picking features as well, which will provide great enhancements to agent workflow.

    Do you mind explaining the workaround that Genesys proposed, please?


    ------------------------------
    Thanks and regards
    Samuel Polgar
    CVT (Global) Pty Ltd
    ------------------------------



  • 16.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    GENESYS
    Posted 15 days ago
    I posted this higher in the thread, but it probably should be down here:

    Basically, the only thing that has been done so far is to increase the limit to 24 hours instead of 3. That enhancement was released a month or two ago.

    https://purecloud.ideas.aha.io/ideas/CLINB-I-252 and https://purecloud.ideas.aha.io/ideas/CLPLA-I-284 are a couple of related Ideas you can vote for


    ------------------------------
    George Ganahl GCP (PureCloud) ICCE CCXP
    Principal Technology Consultant
    Genesys
    ------------------------------



  • 17.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    GENESYS
    Posted 12 days ago
    Just an additional note...there is an Idea regarding In-Queue Email flows that folks might want to comment on and vote for:

    https://purecloud.ideas.aha.io/ideas/CLINB-I-476

    ------------------------------
    George Ganahl GCP (PureCloud) ICCE CCXP
    Principal Technology Consultant
    Genesys
    ------------------------------



  • 18.  RE: Is there any solution or workaround to stop the SLA clock for email interaction during closed schedule period?

    GENESYS
    Posted 12 days ago
    For the SLAs themselves, at this point we plan to extend the timeout to be longer than 24 hours but we need to do more work before that is available.

    ------------------------------
    Lucie DeCristofaro
    Genesys - Employees
    ------------------------------