Skip to content

Feature Catalog

If you want the simpler customer introduction first, start with Customer Overview. This page is the structured feature reference.

This is the operational core of Sicket.

It includes:

  • tenant ticket creation
  • personal and community ticket visibility
  • status management
  • public comments
  • internal staff notes
  • activity history
  • attachments
  • realtime updates

This area is what most day-to-day users interact with most often.

Announcements are Sicket’s broadcast communication layer.

They are used for:

  • maintenance notices
  • urgent building messages
  • organization-wide communication
  • scheduled operational updates

This keeps broad communication separate from ticket conversations.

Sicket uses invitations to place users into the correct scope from the start.

This includes:

  • inviting landlords
  • inviting tenants
  • invitation acceptance
  • tenant unit linking during onboarding

This is a core safety feature, not just an email workflow.

Sicket models real operational structure:

  • organizations
  • buildings
  • residential units
  • building assignments

This structure controls what users can see and what actions they can take.

Organizations on eligible plans can maintain their own support content.

This includes:

  • FAQ entries
  • policy explanations
  • maintenance guides
  • building-scoped support material

This content supports both tenant self-service and staff-assisted support.

Sicket includes AI-assisted product behavior, but it is designed to stay assistive rather than fully autonomous.

Current capabilities include:

  • advisory duplicate detection
  • suggested self-service answers
  • staff draft replies
  • suggested ticket priority
  • suggested ticket category

The user or staff member remains in control of final actions.

Sicket includes operational analytics for:

  • a single building
  • an entire organization
  • a landlord’s assigned building set

This helps staff understand workload, repeated Ticket patterns, and activity trends.

Sicket plans influence:

  • feature availability
  • capacity limits such as units
  • which advanced workflows can be used

This is important for rollout planning and long-term operations.