Casavi projects

Time: 2022

Tools: Figma, MUI Design library, Token studio

Medium: Web, Android & IOS - Phones

My Role: Senior product designer for 2 value teams and Design system contributor

Casavi is a central platform for all aspects of digital property management. It enables efficient communication across all properties, with owners, tenants, and service providers, while streamlining operations and business processes.

As a leading platform in the real estate industry, Casavi automates process management, communication, and service provider coordination.

With Casavi, all processes are digitized, and properties, including customer communication, can be managed anytime, from anywhere, thanks to cloud technology.

Service providers and contracts are centrally organized in the cloud, with orders seamlessly integrated into process management.

Over the past three years, I have completed several major design projects. In addition to these, I have also carried out multiple feature-upgrade designs.
The following are selected work samples. Due to privacy agreements, they may not appear in perfect resolution.

Smattask - Emails

User problem:
Integration with General Email Addresses: Allow for the integration of general email addresses with the casavi inbox, enabling the direct transfer of emails to casavi without the need for forwarding, while still displaying the original recipient.

Comprehensive Email Integration: Enhance the overall email integration within the platform to increase usability, allowing customers to primarily use casavi without the need to switch to other systems for email management.

SmartTask Integration: Integrate email traffic and calendar functionality into the smarttask ticket system, enabling the creation and assignment of tasks and tickets from emails, as well as centralizing correspondence within casavi.

Smattask - Ticket management - Overview

User problem - Tickets overview :

  • Users are experiencing difficulty navigating the ticket cards due to excessive information being displayed in each one.

  • The interface appears overcrowded and lacks adequate spacing, making it visually overwhelming and hard to scan quickly.

  • Users are struggling with ticket cards due to accessibility and readability issues. Each card contains too much information, leading to visual clutter and cognitive overload.

  • The lack of space and overcrowded appearance of elements , making it difficult to focus, scan, or comprehend content, especially for users with visual or cognitive impairments.

Smattask - Ticket management - Details

User problem - Ticket details :

  • Overcrowded interface with excessive information displayed at once, leading to cognitive overload.

  • Poor navigation structure, making it difficult for users to understand where they are or how to get back. Inefficient use of right panel cards, causing important information to be hidden or overlooked.

  • Pages were overloaded with features and actions, creating complexity and slowing down user workflows.

  • The History section was inconsistently placed or blended with other content, confusing users. 

  • Enhance the usage and features of checklists, attachments, assembly and time tracking

Workflow automation

User problem :

  • A growing customer need for deeper process automation.

  • The current API enables the creation of individual workflows (Smartflows), serving as an important first step. However, to remain competitive and meet market expectations, we need to evolve this into a scalable, robust solution.

  • Need of template based workflows and Self-Service Workflow

Complex filters

User problem :

  • Applying filters requires too many clicks, making the process slow and tedious.

  • There is no clear overview of which filters are currently active.

  • Users cannot save their preferred filter combinations for quick access later.

  • Selecting multiple filters involves excessive vertical scrolling, which reduces efficiency.

  • Users can select individual filter items, which are applied and saved automatically upon selection.

  • There is no option to save and manage multiple sets of filters, making it inconvenient for users who frequently apply the same combinations.

Custom app

Customer app

Design solutions:

Two-Way Communication Platform

The application serves as a two-way communication platform between property managers and tenants, facilitating effective interaction and easy access to essential services.

Tenant Experience

Dashboard Overview:
Tenants are presented with a dashboard that displays key features as cards, each with indicators for new updates or actions required. The goal is to provide a quick and intuitive overview of all important information.

Support Features:

  • Notifications, Bulletin Board, Important Contacts, Service Requests, Bookings, House Chat

App features:

  • Home, Community, Services, My Account, My Place, Settings

Property Manager Experience

Dashboard as a Communication Hub:
Property managers can use the dashboard as a communication tool to send updates and messages to tenants.

  • News & Advertisements: Managers can share updates, promotions, or information relevant to tenants.
  • Bulletin Board Announcements: Used to post important notices to the tenant community.
  • Displays latest announcements from the community and property managers.
  • Users (managers or tenants, depending on permissions) can create and post new announcements.
  • If there are no current announcements, a message indicating this is shown.
  • The latest announcement is intentionally excluded from the main dashboard view, encouraging users to check the Bulletin Board section for updates.
App Interface Mockup
App Interface Mockup
App Interface Mockup
App Interface Mockup
App Interface Mockup
App Interface Mockup

User problem :

  • Customer app provides individual access accounts for each tenant or flat owner, which can be customised branding.

  • Features covered are, notifications and appointment scheduling, essential contact information, links to external content

  • Digital document transmission, such as utility bills, with email alerts for updates, all optimised for use on smartphones and tablets.

  • I was responsible for designing the app to include all essential user flows while minimizing development effort.

Smattask - Ticket management - Time tracking

Time tracking

Design solutions:

To be displayed in individual ticket details:

  1. Components to be tracked include dates, duration (in days), and the people involved at each stage of the ticket’s lifecycle.
  2. Components to be tracked include the time spent on the ticket (in hours and minutes) and the people involved at each stage.

Information considered for Design Goal

  1. Opening Stage
    1. Person who opened the ticket
    2. Date the ticket was opened
    3. Time the ticket was opened
    4. Time spent opening the ticket
  2. Changes / Actions Stage
    1. Person who made the change or took an action on the ticket
    2. Date the change/action was made
    3. Time the change/action was made
    4. Time spent on the change/action
  3. Closing Stage
    1. Person who closed the ticket
    2. Date the ticket was closed
    3. Time the ticket was closed
    4. Time spent closing the ticket
App Interface Mockup
App Interface Mockup
App Interface Mockup
App Interface Mockup

User problem :

  • The user wants to outline a timeline of the ticket’s journey—from the ticket's creation to its closure or reopening, measured in days.

  • The user wants to track the actual time spent on each ticket, from its opening to its closure, measured in hours and minutes.

  • The managers should get a single glance result for Database for a property- Days, time, and people involved in individual tickets and the total number of tickets.

Arrow Up 1 Arrow Up 2