Sync CMS Pages data

You can navigate to this screen by choosing the Tellofy AI -> Data Sync -> Pages menu option.



This screen will allow you to add/remove CMS pages data from the chatbot knowledge base. NOTE: Since page data can be website/store view specific, their data would be synced to the chatbot instance(s) associated with the selected website/store view.

All pages (that have a status of “enabled”) available in your store will be displayed here. The “Selected” column indicates whether the data will be sent to TAI or not. “No” indicates that the data will NOT be synced. “Yes” indicates that the data will be synced to TAI.

Only data that has been added to TAI i.e. has a Yes as selected status will be available within the chatbot. 

The default Selected status for all pages would be set to No (unless you have opted to import cms pages at the time of login).

Adding Pages to Tellofy AI: To add pages, select specific or all pages and then choose the Add Selected to TAI option from the Actions drop-down.   

The selected pages will be added to the product sync queue to be added to Tellofy AI when the CRON is executed (this can be at a scheduled interval/time or can be executed manually for data to be instantly added to Tellofy AI). The Selected status of these pages will be set to Yes. Once pages have been added to Tellofy AI, customers can ask and receive answers pertaining to them, within the chatbot.  

Pages need to be added to Tellofy AI only once; post being added, page data will be re-synced only when they have been modified.

Removing Pages from Tellofy AI: To remove pages, select all/specific pages that have a Selected status of Yes. Now, choose the Remove Selected from TAI option from the Actions drop-down. These products will be added to the delete pages sync queue and will be deleted from Tellofy AI end when the CRON is executed (either at the scheduled time or executed manually to delete data immediately). The Selected status of these pages will be set to No. Once pages have been deleted their details would not be available to customers within the chatbot.  

Did this solve your problem?