Structure and plan your content

Neelke Stadler Updated by Neelke Stadler

Drawing up an organogram and assigning a key (e.g. a unique number, emoji or keyword) to each piece of content before you start building your chat service in will make things easier down the line. 

Now that you understand how users typically engage with content on a service, you are ready to plan the first iteration of your content. A very basic structure for a chat service could look something like this:

If you look at the above example, you’ll see that the three items in the main menu each have its own number. If a user types “1”, they’ll receive the message titled “1. Why stories are important”; if they type “2”, they’ll receive the message on “How to read stories to kids”, and so forth. 

The third item in the main menu, “3. Five stories your kids will love”, contains another menu. When a user types “3”, they’ll receive a list of five children’s stories they can access on the app. Each of the stories has a unique number assigned to it. When a user now types “4”, they’ll receive the “4. Three little pigs” message, which includes text, illustrations and a sound clip. 

The important thing to notice here is that each message in the organogram has a unique number that identifies it. The number “1” has been used in the main menu and cannot be used again in one of the other menus as this number is linked to a specific message (“Why stories are important”).

Once you've structured your content it is now easy to create your first menu and start setting up automations.

Was this article helpful?

How to delete a message that a user sent?

How users engage with content