What Sicket does

A practical housing communication system

Sicket replaces scattered follow-up across email, calls, and group chats with a building-scoped workflow. Tenants can report personal or community issues, follow progress, and find trusted information. Staff can coordinate tickets, building incidents, announcements, news, and knowledge without losing the history of what happened.

Sicket is not a rent collection system or a social network for neighbors. It focuses on operational communication: what was reported, what affects the wider building, what residents need to know, and what should happen next.

Who it is for

Independent owners can manage one building without adding unnecessary layers. Housing organizations can work across multiple buildings while landlords stay within their assigned scope. Tenants receive a simpler view focused on their home, tickets, current incidents, announcements, news, and available answers. The guided intake is designed to remain clear and approachable for residents across age groups and levels of digital confidence.

Core workflows

• Tenant tickets: residents use guided intake to submit private personal tickets or building-visible community tickets. They can follow an active community ticket instead of creating a duplicate, then track its status and updates in one place. Read how ticket visibility and anonymous submission work.
• Building incidents: coordinate larger issues and publish a clear update feed for affected residents.
• Announcements and news: announcements support immediate or timed starts; news articles publish immediately with optional email delivery. Staff can find archived news in the archive. News articles do not offer drafts or scheduled publishing.
• Knowledge Base: publish trusted answers once, transfer building-specific entries with import and export, and surface them before another ticket is created.
• Staff ticket workspace: switch between compact, list, and desktop board views, use scoped filters and follow-up indicators, and open the relevant records from dashboard metrics.
• Operational analytics: review workload, response patterns, recurring topics, communication gaps, and resolution feedback across authorized tickets.
• Contractor Cases: start from a ticket, incident, or reviewed pattern, preview the selected context, and share it through a protected, expiring contractor page without creating a dashboard account. Shared fields can be changed and access can be revoked later. Read how Contractor Cases work.

Updates, email, and feedback

Eligible comments, direct replies, public staff updates, and status changes can send operational emails according to each user's notification preferences. Repeated activity can be grouped instead of producing a separate email for every edit.

Only the resident who created a ticket can submit its resolution feedback. Authorized staff can review feedback across the tickets within their scope to find recurring service issues.

How AI is used

Sicket uses optional AI assistance for practical tasks such as assessing and applying ticket categories and priorities, finding relevant building information, showing similar community tickets, and recognizing recurring patterns. Pattern checks can run automatically, and authorized staff can request a deeper scan. A detected pattern does not publish an incident or notify residents automatically; staff decide what action and communication are appropriate.

The tenant dashboard does not offer controls to edit category or priority after submission. Authorized staff can adjust priority later. Category remains automatically managed and may be reassessed when core ticket details change.

Plans and availability

Starter begins at EUR 49 per month and includes 1 building, up to 10 homes (residential units) and 1 GB of attachment storage, without landlord or observer accounts, the Knowledge Base, or analytics. Professional begins at EUR 249 per month and includes up to 5 buildings, 500 homes (residential units) total, 5 landlords, 10 observers, 100 Knowledge Base entries total, 50 GB of attachment storage, and analytics. Enterprise capacity and commercial terms are configured for the agreed rollout. The current public release is version 3.1.2.

Home and Knowledge Base allowances are organization-wide. Knowledge Base entries belong to individual buildings, and a copy in another building counts as another entry. A managed vacant home counts toward home capacity, while additional residents sharing that home do not.

Landlord and observer accounts are optional on Professional and Enterprise. For buildings without an assigned landlord, staff-facing operational email routing falls back to the organization administrator.

Sicket is operated from the Netherlands and supports English and Dutch. Self-serve signup is available for organizations in the European Union and the United States. Contact Sicket to confirm availability and rollout requirements in other countries.

Current limits and prices are listed in the pricing section and on the billing page.

Privacy and trust

Housing communication can contain personal and building-specific information. Sicket uses role- and building-scoped access, resident-safe visibility rules, anonymous reporting controls, audit history, and documented subprocessors. Read the current privacy information, security overview, and subprocessor list for details.

Official Sicket sources

For current product information, use the Sicket website, product documentation, and release notes. For demos, rollout questions, or corrections, contact hello@sicket.app.