Designing Contacts

Primary Use Case

The purpose of the contacts section in this application is to allow Building Manager Bob to manage how he receives notifications regarding his devices. As he is a busy man and may not have time to management the devices himself, he decides to hire someone, Employee Erin, who’s responsibility will be to respond to these notifications. The different types of notifications he can receive are when events are about to occur, when an opt out has been scheduled, and device communication statuses. Depending on which notification is received, Employee Erin will respond accordingly.

Before Employee Erin can receive notifications, Building Manager Bob needs to add her as a contact. The way the design is structured is for him to be able to easily browse through multiple contacts and their details similar to outlook. The list on the left are his contacts and the right side are the details regarding what devices that contact will receive notifications for and how he will receive them.

Above are draft wireframes of how a user would edit a contact. These wireframes were to demonstrate general placement of elements and to describe the interaction pattern. To edit a contact, user would click on the edit button to put the contact into edit mode. Once in edit mode, the user can check and uncheck subscribed devices on the subscription tab and contact methods which are shown below.

Building Manager Bob can choose by which method of communication his contacts should receive notifications. Some notifications were unavailable to be sent by voice call or text which is why they are greyed out. In the contact method table below, Bob would enter the contact’s information.

High fidelity prototypes