Is there any way to stop the communicate app from logging out after a period of inactivity ?. I have tested on a number of different mobiles and the time you are logged in differs on each however it still appears to log out after about 15 minutes which isn't ideal.

Is the app on the phone whitelisted from memory, battery, and storage?  Also, needs to allow background operation.  

Is there any way to stop the communicate app from logging out after a period of inactivity ?. I have tested on a number of different mobiles and the time you are logged in differs on each however it still appears to log out after about 15 minutes which isn't ideal.

Is the app on the phone whitelisted from memory, battery, and storage?  Also, needs to allow background operation.  

Is there any way to stop the communicate app from logging out after a period of inactivity ?. I have tested on a number of different mobiles and the time you are logged in differs on each however it still appears to log out after about 15 minutes which isn't ideal.

Hey Robert,

Any idea why inbound calls don't ring on the app? It seems to work once or twice, but then calls either go straight to VM or ring on the customer end, but not the app.

I recall there was something about having the WebRTC phone set as default on the user profile but that doesn't seem to make a difference.

Any ideas?

Will 

Is the app on the phone whitelisted from memory, battery, and storage?  Also, needs to allow background operation.  

Is there any way to stop the communicate app from logging out after a period of inactivity ?. I have tested on a number of different mobiles and the time you are logged in differs on each however it still appears to log out after about 15 minutes which isn't ideal.

With the latest updates on Android, I have a hard time getting ANY app to work over long periods.  It seems if you set them to always run and have restrictions on battery, wifi, and memory, you still can't get the app to stay active.  I am not sure if that is the issue, but for me it is a hassle.  Previously, this was not an issue and I could get it to stay running in the background and it would notify me of incoming calls.  Now, when I leave it open and go back to it, I am met with the log-in screen.  

One issue with the Communicate app and license, is that you can't get and ACD call transferred to you if you are not logged into the UI - it will just go to voicemail.  I am guessing that is to not allow customers to use one or two agents that just transfer to groups or users and still want to report on the calls as ACD.  I had a customer once on PureConnect that had 2 agents logged into 2 phones on the wall and the agents (30 of them) used Pickup to answer the ACD call.  

Hey Robert,

Any idea why inbound calls don't ring on the app? It seems to work once or twice, but then calls either go straight to VM or ring on the customer end, but not the app.

I recall there was something about having the WebRTC phone set as default on the user profile but that doesn't seem to make a difference.

Any ideas?

Will 

Is the app on the phone whitelisted from memory, battery, and storage?  Also, needs to allow background operation.  

Is there any way to stop the communicate app from logging out after a period of inactivity ?. I have tested on a number of different mobiles and the time you are logged in differs on each however it still appears to log out after about 15 minutes which isn't ideal.

Hey Robert,

Any idea why inbound calls don't ring on the app? It seems to work once or twice, but then calls either go straight to VM or ring on the customer end, but not the app.

I recall there was something about having the WebRTC phone set as default on the user profile but that doesn't seem to make a difference.

Any ideas?

Will 

Is the app on the phone whitelisted from memory, battery, and storage?  Also, needs to allow background operation.  

Is there any way to stop the communicate app from logging out after a period of inactivity ?. I have tested on a number of different mobiles and the time you are logged in differs on each however it still appears to log out after about 15 minutes which isn't ideal.

Hi Will, Did you ever get clarity on this? I have a user testing out the communicate app as well and he has the similar symptom that you're describing where it works a few times and then stops. We've made sure there's nothing locally setting wise or connectivity with the device he has the app installed on, permissions are good, nothing in org settings like an inactivity timeout enabled. So far the only thing that seems to be making any difference (and it's still too soon to say definitively) is he logs out of any other session open in a browser, etc. so exclusively using the mobile app. That's not viable for us though cause our target user is a manager so they will be up and down around their location, sometimes preferring to access genesys via a browser while at desk but frequently getting up and need to answer via phone. 

Hey Robert,

Any idea why inbound calls don't ring on the app? It seems to work once or twice, but then calls either go straight to VM or ring on the customer end, but not the app.

I recall there was something about having the WebRTC phone set as default on the user profile but that doesn't seem to make a difference.

Any ideas?

Will 

Is the app on the phone whitelisted from memory, battery, and storage?  Also, needs to allow background operation.  

Is there any way to stop the communicate app from logging out after a period of inactivity ?. I have tested on a number of different mobiles and the time you are logged in differs on each however it still appears to log out after about 15 minutes which isn't ideal.