Customer Centric Information Architecture
In the past and also present, Architecture companies have used software that enables them to create accounts for each customer they deal with and normally for only things such as handling and invoicing. An actual customer could have more than one account and has made this type of customer handling somewhat of a problem with its limitations. Well, not limited to solely these issues is the fact that this type of data may not give you all of the answers you need when going through your records. It seems useless to carry out an account balance when you may only be getting one of the accounts draw up by your database. For this reason alone it seems a great advertisement to having an enterprise information architecture program with the capability of linking accounts.
When dealing with the word of web information architecture you will want a sufficient way to keep all of your customers as well as your prospects in line. It can also be very helpful to design a small instruction manual to help customers who may be newer to the web understand all about information architecture.
In having a program that will help you merge accounts and even prospective accounts it can become increasingly important to manage your accounts more properly so as to not overload the same customers again and again with the same information. This will be much appreciated by veteran users who will appreciate the lack of spam generated by your business as well as by the newer user who may become confused at understanding why they keep being peppered with the same information.
Hopefully a program that will help to provide a sort of customer tree will help to identify services and handling charges so that individuals can be assessed of all they owe on each of their accounts.
In: Information Architecture · Tagged with: about information architecture, enterprise information architecture, web information architecture