Concierge Cache Configuration
Why Caching Needs Attention
Concierge reads its settings directly from the WordPress database on every request, bypassing the WordPress object cache entirely. This is intentional — on hosting environments with persistent object caching such as Redis, the standard WordPress get_option() function can return stale data after a settings save, causing the plugin to behave as though nothing has changed.
This direct database approach means that Concierge settings always reflect what is actually stored. However, it also means that the Concierge REST API endpoints — which the widget uses for all chat and lead submissions — must not be cached at the page or HTTP level, as caching a response from one visitor and serving it to another would produce incorrect and potentially confusing behaviour.
What To Exclude From Caching
In your caching plugin or server configuration, exclude the following URL path from all caching rules:
/wp-json/cnc/
This covers the chat endpoint, the lead submission endpoint, and the licence verification endpoint. Any response cached from these URLs will produce errors or incorrect results for subsequent visitors.
LiteSpeed Cache
If your site uses LiteSpeed Cache, flush the cache after installing or updating Concierge. In cPanel, go to LiteSpeed Web Cache Manager and click Flush All.
To exclude the Concierge endpoints permanently, go to LiteSpeed Cache > Cache > Excludes in the WordPress admin and add /wp-json/cnc/ to the Do Not Cache URIs list.
WP Rocket
/wp-json/cnc/ to the Never Cache URLs list. Save your settings and flush the cache.Redis Object Caching In cPanel
Sites hosted on cPanel may use Redis for persistent object caching. On first installation, or after a settings save that does not appear to take effect, restart Redis from your control panel and then return to the Concierge Settings screen and click Save Settings once more.
This two-step process ensures the new settings are written directly to the database and that the Redis cache is cleared so they are read correctly on the next request. This is a one-time step on first setup — subsequent saves do not require a Redis restart.
If your licence status shows as Unknown after verification, or if your proxy secret is shown as not stored despite having entered it, a Redis cache issue is the most likely cause. Restart Redis and save settings again to resolve it.