Build your own Federation

With this article we intend to present a concrete example of how the proper organization of THRON platform, according to user roles that make up the company and all the entities around it, favors the triggering of a content-management workflow that will result not only in the maximization of the content value, with the benefit of centralization and removal of duplications, but will also allow each business unit to enjoy all the other benefits offered by THRON.

From the Marketing team, which thanks to the Content Marketing module will be able to monitor and control the interests of users and how these are combined with the topics covered by enterprise content; to the Sales team, which thanks to the Sales Insights module will be able to build an accurate and personalized communication with the customers; up to the Customer itself, which thanks to the Customer Experience will be able to always find content that espouse its interests, in a omni-channel experience.

This ideal ecosystem is what we call a Federation. In order to make things clear we will present you the organization of our own company, trying to enlighten you on how using our own product we are able to achieve the aforementioned results.

 

We will try to illustrate you some ideal configurations which are currently being used in our company so that you can easily understand how a proper setting of roles and workflow will enable you to gain the most from THRON advanced features.

 

Let's consider the following scenarios:

 

Support Portal

Content published in the Support Portal that you are currently visiting is created within a third-parties CMS, they are then synchronized into THRON thanks to Zendesk Connector. Correspondent content in THRON can then be enriched and tagged by other users so that it is ready to be used by a Recommendation application which is embedded into our company website; this way, most visited articles will be suggested to users into our website whenever their interest match covered topics.

 

A Technical Editor is part of our Technical Support group, from which he inherits the following permissions:

 

 

Articles, such as this one you are reading, are created within a third-party CMS from the Technical Editor himself; then, by means of Zendesk Connector they are imported into THRON in a specific "Support Portal" folder, which presents the following configuration:

 

 

Once content has been synced by the application and thanks to the permission inherited by its group, the Technical Editor can tag them with tags belonging to TOPIC and TARGET classifications, in order to identify their topics and the subjects for which the specific article is intended.

Then, Design group, which can access to the "Support Portal" folder with "write" access right over the content, can enrich those content with a proper thumbnail.

Once the content is completely set, the CTO, accessing the folder himself with full access rights, can take those content and publish them into the folder where the Omni-channel Recommendation has been configured, so that they will be available into THRON website.

 

Social Networks

The Design team within our company produces a series of media which are intended for customers and partners, such as videos and images. These contents are published by the members of the Design group, which has the following permissions:

 

 

Into the "Assets" folder, which presents the following configuration:

 

 

Then the Marketing Manager, or the Marketing Editor can tag such content and select those which must be published into social networks, hence drag those content into the "Social Network" folder where there is a "Social Connector" application which will automatically handle content publishing into pre-configured social networks (Facebook, Twitter, Youtube).

 

Application Brochure

Each Partner Developer collaborating with THRON is present within Dashboard with its own personal group which has the following permissions:

 

 

Moreover it has its own personal folder where he will find a document illustrating all the procedures and guidelines to create specific documentation for the application being developed along with all the contracts.

Once all the documentation is ready, the Partner Developer will have to provide it to the Marketplace Team which will review it, properly tag it and then publish it into the "Brochures" folder, which has the following configuration:

 

 

Here, the Marketing Team will have to review it and approve it, while the Design Team will have to enrich it with proper icons and screenshots. Once the content is ready, its contentId will be provided to the CMS managing the Public Marketplace in order to allow its download.

 

Sales Documentation

The Marketing Team, along with the Design Team are in charge of preparing official material and documentation for the Sales Team. Once this material is ready, it is published into the "Draft for Sales" folder, which has the following configuration:

 

 

This material is then revised and tagged by the Chief Technology Officer. Once the content is ready, the Marketing Manager will publish it into the "Sales" folder:

 

 

From this moment on, and thanks to their permissions, the Sales Team will be able to download this material or share it externally (via email or link):

 

 

Was this article helpful?
0 out of 0 found this helpful

Have more questions?

SUBMIT A REQUEST

Hai altre domande?

INOLTRA UNA RICHIESTA

Comments