@Helga It would be very helpful to have this cache refresh timing documented somewhere clearly. So often it is about managing expectations. I don’t like making promises that turn out to wrong. This reflects poorly on my professional reputation. For instance (after my initial post) I had advised the client 48 hours when I found this information posted by Elfsight on an earler Q&A. To be frank 72 hours has the perception of being a really, really long time in this day and age where everything else has become instantaneous. And @George7 is reporting 4 days as his usual experience. I think a delay like that is unacceptable. Yes you have technical issues with increasing the frequency. That sounds to me (as a technical person) that management needs to resource this function (spend money on a fix) and are avoiding this. Apart from this issue, the Elfsight product does a lot of things right. Reducing this cache time to a more reasonable level (maxm 48hrs) would go a long way to meeting the expectations of your customers and your potential sales.
Thank you for sharing your thoughts, @user14340!
First off, I’m truly sorry about this frustrating situation our widget has caused. I completely understand your feelings, and I agree that it would be nice to at least let you know that our widget uses cache.
I’ve shared this thread with the team once again so they better understand the urgency. I know they’re currently discussing possible solutions, and I’ll make sure to update you once I know more.
Thank you for the constructive dialogue!
On August 16th, you mentioned that you would forward the message from @user14340 to your team to emphasize the urgency.
It has now been over a month since @user14340, @Hugh , me and others, requested a resolution to the issue, and more than two months since I reported the problem, which is damaging our professional reputation and client trust. We’ve only received promises from you, but there’s been no visible progress.
How many more months do we need to wait for this urgent and serious issue, which affects all of us using your Google Reviews API service, to be resolved?
Thank you.
Hi @George7, thank you for following up!
Indeed, we were discussing possible solutions to reduce cache time for our Reviews widgets, and we’re currently working on one idea. For now, we’ve decided to implement different cache timings based on your chosen plan.
Since the task is still in progress, I don’t have any specific details yet, but we’re aiming to roll out this functionality by the end of October.
Thank you for your patience, we’re doing our best to deliver this update sooner rather than later.
Actually I said I did not have a problem with a few days to update.
Let’s face it, amending your software to update every 24 hours, instead of 72 hours is the most simplistic of software updates. Soooo trivial. To take a quote from NIKE, just DO it
Hi @user15067 
I understand that some things might seem easy to implement, but in reality, they can be far more complex. Unfortunately, this request is a perfect example of that.
There are some obstacles preventing us from setting the cache time to 24 hours for now, but we’re working on introducing cache time limits based on the chosen plan. We believe it could be a first step in the right direction.
I’d also like to mention our CEO’s latest reply in this thread where he highlights the technical challenges we’re facing:
Thank you for your comment! We’ll be happy to update you here once we have any news to share.
It is not trivial. It would be easy for elfsight to request more frequent updates through their program. My understanding however is there is a limited number of API calls software can make to google in any given period, and if you go over, google puts your updates on hold.
I believe that just because you don’t need this feature doesn’t mean others don’t. I understand that if you get feedback once in a while or monthly, it might not seem important to you.
However, for someone like me, who receives several of feedbacks daily, this feature is crucial!
As a paying client, I’m really dissatisfied and annoyed by how poorly feedback updates are managed. These changes need to happen at least once every 24 hours.
I’ve seen others asking for the ability to manually refresh feedback, and people keep supporting this idea, yet nothing has been done. It’s beyond frustrating.
And don’t tell me it’s impossible—your competitors are doing it! They offer updates as often as every 3 hours. Meanwhile, your system updates once every 4 days. That’s just unacceptable.
You’ve had months to introduce such a simple feature, and still, no action. If you can’t figure it out, hire someone who can. It’s a one-time investment, and you’ll have the feature forever.
Please, add this feature already. It’s getting incredibly frustrating. Enough delays, just get it done!
_
Hi @George7 
Our devs believe they will implement the idea of different cache timings based on the plan by early November 
At the very least, I would expect the update frequency to be documented in the widget description.
Without this description, my expectation was that new reviews would appear immediately. I can understand that new reviews only appear after a few hours. The minimum expectation would be a refresh at least daily.
I could also understand if a free plan updated the content a little less frequently.
However, I immediately decided to purchase a paid plan because I basically like the functionality and I wouldn’t have thought that updates would only appear after several days. I am quite disappointed. And if I had known this beforehand, I might have looked for a different provider. Or at least I would have known what I was letting myself in for.
more precise description => less disappointment.
Hi @Germo_Gortz, thank you for your comment!
First of all, I’m really sorry that the widget cache time didn’t meet your expectations and that the information wasn’t clear. We explain why the Google Reviews aren’t updated instantly in our Help Center, but I understand it might not be the most obvious way. I’ve shared your feedback with the team to ensure they’re aware of this concern.
Additionally, we’re actively working on an option to provide different cache times depending on the plan. I really hope I’ll be able to share an update on this functionality soon 
Thank you for sharing your feedback, we do appreciate it!