Product Overview
What Sicket is
Section titled “What Sicket is”Sicket is a building operations and resident support platform for organizations that manage one or more buildings.
Its main job is to structure communication and issue handling between:
- organization admins
- landlords or building managers
- tenants or residents
In practice, Sicket is used for:
- reporting issues in a building or unit
- keeping communication around those issues organized
- publishing building announcements
- inviting the right people into the right building scope
- giving staff analytics and operational visibility
- surfacing organization-specific answers through the knowledge base and AI support flows
Core model
Section titled “Core model”Sicket is organized around a clear hierarchy:
- organization
- building
- residential unit
- user access inside that scope
This is important because almost every permission in the product depends on scope:
- organization admins act across the organization
- landlords are restricted to the buildings they are assigned to
- tenants are restricted to their own unit and building
Main feature areas
Section titled “Main feature areas”Tickets
Section titled “Tickets”Tickets are the operational core of Sicket.
Residents can create tickets for issues in their building or unit. Staff can manage status, add internal notes, and respond through the dashboard.
Announcements
Section titled “Announcements”Announcements let staff publish organization-wide or building-specific communication, such as maintenance notices or urgent updates.
Invitations and onboarding
Section titled “Invitations and onboarding”Users are brought into Sicket through scoped invitations so access is attached to the correct organization and building from the start.
Knowledge base
Section titled “Knowledge base”Organizations on eligible plans can maintain FAQ and support content for tenant self-service and staff assistance.
Analytics
Section titled “Analytics”Sicket provides analytics at organization and building level so staff can understand ticket volumes, issue types, and operational trends.
How people usually use Sicket
Section titled “How people usually use Sicket”Tenant flow
Section titled “Tenant flow”- receives an invitation
- creates an account
- is linked to one residential unit
- creates or follows tickets in the building
- reads announcements and tenant-visible support content
Staff flow
Section titled “Staff flow”- receives an invitation or is created by an admin
- accesses one building or an entire organization
- reviews tickets and announcements
- uses analytics, notes, and knowledge-base content to manage operations
Product boundaries
Section titled “Product boundaries”Sicket currently focuses on web-based building operations.
It is not a mobile-app-first product, and the current backend model does not implement assignment-based routing workflows. AI features are advisory and assistive rather than fully autonomous.