What happened
What this says
Current to 10 Oct 26Jenna Price requested on-demand or batch refresh for individual CRM records. Bethan Lister logged it as a feature request; Jenna acknowledged overnight refresh is workable but team sometimes needs intraday checks.
Problem: nightly-by-07:00 refresh feels slow when placement statuses change fast (shortlisted to rejected). Jenna asked for on-demand or batch refresh. Handling: Bethan logged it as a feature request for the product team. Jenna accepted the constraint but noted the team is stretched and sometimes needs intraday checks. This could resurface as a renewal concern if placement velocity increases.
Details
Updated 9 Oct 26Trail
- created · Jenna Price 20 Aug 2024 14:00Hi, we've been using the brain for a few months now and it's great for seeing placements and pipeline in one place. But when a record gets updated in our CRM – like a candidate moving from shortlisted to rejected – we have to wait for the nightly refresh to see the change in the brain. Is there any way to force a refresh on individual records, or batch? Our consultants are asking for it.
- public_reply · Bethan Lister 21 Aug 2024 04:35Hi Jenna, thanks for the detail. Just so I've got this right – you're looking to see CRM changes in the brain without waiting for the scheduled refresh? That's a good request. Right now every update comes through on the nightly cycle, which completes by 07:00 your local time. I've logged this as a feature request and flagged it to the product team. In the meantime, is the overnight delay workable for most queries, or is there a specific use case slowing things down? Cheers, Bethan.
- public_reply · Jenna Price 21 Aug 2024 16:33Thanks for getting back to me. I realise it's not urgent – most of the time overnight is fine. The consultants just like to check a status during the day sometimes. We can work around it for now. Sorry for the slow reply, the team's a bit stretched at the moment. Jenna.
- status_change · 25 Aug 2024 23:59