In useBuilt for business

Communications Center

One worklist of who a property-management office still owes a reply.

Illustration of the Communications Center: a “Waiting on us” list with overdue clocks and evidence badges, invented namesIllustration

This tool handles real client communications, so nothing from it is shown. Every picture of it is an illustration with invented names and numbers.

Why it matters

The Communications Center pulls in the office's phone system, CRM and email, then answers four questions every morning: who is still waiting on us and for how long, is anything about to escalate, are we keeping our promises, and is the data actually arriving. Every item on the list explains itself, including the evidence that is missing.

  1. 01

    Who is waiting on us

    Seven kinds of obligation, from unanswered texts and missed calls to overdue follow-ups and promises made, rebuilt from the raw messages every time.

  2. 02

    Any reply counts

    A text answered by a phone call is answered. Lateness is measured in business hours, not clock hours.

  3. 03

    Honest about certainty

    Every item is marked as confirmed, unverified identity or AI-detected, and the three never look alike.

  4. 04

    Privacy before AI

    Names and details are replaced with tokens before anything reaches a model, with daily and monthly spending caps.

The details

Open any part for the full story.

Features5
  • An owed queue covering unanswered messages, missed calls, unreturned voicemails, overdue follow-ups and tasks, open issues and promises.
  • Contact matching by phone and email, with careful handling of shared numbers and unknown senders.
  • Rule templates and owner text alerts that fire only on new activity, never on old backlog.
  • Accountability views (answer rate against a 90% target, promises kept) with the arithmetic shown.
  • Issues, @mentions, notes and scheduled follow-ups.
How it works
  • A privacy-first AI gateway: tokens replace names before text leaves the machine, the mapping is kept in an encrypted vault, and spending has soft and hard caps.
  • Runs as a single Docker container on the office's own hardware.
Technology
  • Next.js
  • React
  • TypeScript
  • Prisma
  • SQLite
  • Docker
Development notes

Why I built it

The office needed one list it could trust and work from top to bottom. That meant being honest about uncertainty: a guess made by a model must never look like a confirmed fact.

My part

Sole builder, working with the office's owner on what to measure and how to show it.
Status and context
Status
In useIn daily use · private
When
Jun 2026 — now
Kind
Built for business

Who it’s for

A property-management office with many staff phones, many channels, and residents and owners waiting on answers.

The problem it solves

Messages arrive on many channels and many staff phones. Nobody could say with confidence who was still waiting for a reply, or which promises had slipped.

Related projects