Quick links in this article:
...
In this article, we’ll explore the final step in creating your content library - publishing content, ready for your agents to use! Not yet created your content? Try here first: Creating Classic Content Responses
Testing Content Responses
Before navigating to an interaction and opening the Content Response library (see the agent-focused article Using Content Responses for more information), here are some useful things to know:
...
| Note |
|---|
These restrictions are in place to protect the performance speed of your Gnatta domain. If whilst testing your content you find it doesn’t appear as expected, please get in touch, we’re here to help: https://gnatta.atlassian.net/wiki/spaces/HELP/overview |
Publishing content
Now that you’ve setup your Content Response (complete with a display condition and at least one variation!), it’s time to publish it. If you’ve got a large content team working on building your content library, it can be useful to use the review process to manage delivery of content, and ensure content is thoroughly checked before it reaches your agents.
...
Once your content has been published, it’ll be available to the agent (provided the display condition is met/the display condition is scored). Note that browser caching may take up to 10 minutes.
Editing after publishing
After a piece of content has been published, you’ll need to Copy to draft in order to make changes, and send the content through the review process again.
...
Hovering over the variation will show the previous (published) version.
...
Next steps
That’s it! Your content library should be up and running. Want to see it in action?
...