The Retell Community is where innovators, call center leaders, and AI enthusiasts come together to share ideas, learn best practices, and explore the future of voice automation. Join to connect with peers, get early access to product updates, and collaborate on building human-like AI voice experiences that transform customer service.

Retell AI

The knowledgebase that we setup for Agent is not synching, we're synching manually. please suggest a resolution

For URL-based sources, you can enable auto-refreshing, which automatically re-fetches all URLs every 24 hours. You can also enable auto-crawling for specific URL paths to automatically crawl pages every 24 hours.

If  you're using files or text sources, those don't auto-sync since they're static uploads. You'd need to update them manually or programmatically

Thanks for the response, but I don't need auto sync every 24 hrs, just want to sync every 1 week, so I use to manually sync every week. but from last two weeks, the synching isn't working

<@1405365110880338062>  - can you check my response above and reply back

<@1361773912341483520> can you send me your org id

Hi <@1405365110880338062>  - did you get any update from the team. The last Refresh is on Jan 27th, and having issue with AI answering with latest details from website. I can't even select the "Updates existing content every 24 hours" as its greyed out.

Hi <@1361773912341483520> should be fixed now.

Hi <@1405365110880338062> - this is not synching again. Looks like some ongoing issue, can you please fix it on priority. I'm getting complaints from my customer that the AI is not responding witht he updated information from the website

<@698250327287398401> <@605090813025976344> <@1335889378517585920> <@493285168019275776>  - Hi, can you please look into the above issue. had synching issue last week, your team fixed it. Then the Agent synched. And today when I again tried to sync, it's not working. Can you please look into this on priority.

Hi <@1361773912341483520> I have again notify the team about this issue

<@1361773912341483520> Should be fixed now