Chat button agent availability status refreshed every 10 seconds upon Page refresh and it will take upto 50 seconds if page is not refreshed

This is dependent upon if there are any available agents for that chat button. The availability checks are long-polling so you may see some variance in how long it takes for a chat button to recognize that agents are available and reflect the same (or vice versa). 
 

The chat button status/availability is cached at most for 10 seconds. Visitors ping to check the availability every 50 seconds. When any visitor pings for the status of a chat button and it's been more than 10 seconds since the last time we updated the status (cached), it will get the current status and cache again for 10 seconds (whether the button is online or offline). If other visitors ping within the next 10 seconds, the status will remain the same whether agents become available or unavailable. Those same visitors won't ping again for 50 seconds, at which point the same logic will apply.
 

You can confirm this behavior with a simple HTML test page:

1. Create a test Chat Button & Deployment in Setup;
2. Copy and paste the code for the Button and Deployment and paste it into Notepad, save the code with a .html format;

3. Open the test page in your browser;

4. If the Agent Status changes from Online to Offline or vice-versa:

   • ​​Refreshing the page will update Agent status within 10 seconds

   • Without refreshing the page it will take up to 50 seconds for the status to change