Field · Messaging

The question lives on the thing.

Direct messages, project channels, and a comment thread on every expense, photo, and request — so “what was this $744 for?” is asked on the $744, and the answer is still there in November.

Start for free All field tools
What this replaces

A group text nobody can search.

Four jobs, eleven people, one thread. A photo of a leaking valve from March sits between a lunch order and a gate code, and the one answer you need is somewhere above six hundred messages. Nothing in that thread is attached to a dollar, a phase, or a date.

What you get instead

Conversation with an address.

Every message belongs to something: a person, a project, or a specific record. The White Cap charge that came in $18.40 high has one thread, on that charge, with the restocking-fee answer in it. Nobody asks twice, and nobody scrolls.

Three places to talk

Direct, project, or on the record itself.

Most tools give you the first two and call it done. The third is the one that stops the same question being asked every month.

1:1 messages

You and one person. The PM, the bookkeeper, a framer through the crew portal. No app to install on their end — the portal carries it.

Project channels

One channel per build, with the people on that build in it. Someone joining in week nine reads back the whole job instead of asking what they missed.

Threads on records

Every expense, photo, purchase request, time entry, inspection, and sub invoice carries its own thread. The context is the record. Nobody has to re-explain which one they mean.

Cedar Street · open threads
TUE 3:12pExpenseWhite Cap, $744.30 — “Statement is $18.40 high.” Answered: restocking fee on the returned anchors. Closed.2 replies
TUE 1:40pPhotoRoof deck, 7:12 a.m. — “Is that tie-off anchored to the truss or the sheathing?”3 replies
TUE 11:20aRequestPR 2219, flex duct $1,310 — “Can we use the 8" instead? Saves 240.” Waiting on the HVAC sub.1 reply
MON 4:55pInvoiceValley Electric 1187 — “Low voltage shows 40% but the drops aren’t pulled.” Percent corrected to 25%.4 replies
MON 8:02aScheduleDrywall hang — “Two days overlap with Birchwood.” Resolved by pulling siding forward.5 replies
Unread

A count is never red.

Red on this product means one thing: a number that has gone over, or a genuine safety flag. Twelve unread messages is neither. It is information, and it gets the same neutral treatment as any other count on the screen.

The orange button on any screen is the one next action. If messaging starts competing with it for your eye, messaging is doing something wrong.
Who can talk where

The crew, the office, the sub, the owner.

Four groups with four different views of the same build. Everyone gets to ask a question in the place the question belongs, and nobody sees a number they were not meant to see.

Inside the company

Full context, no gatekeeping.

  • PMs, managers, and admins message directly or in any project channel
  • Threads on expenses, invoices, and requests carry the amounts and the ledger line
  • Flagging an expense opens its thread and pings whoever submitted it
  • Search covers every message, every thread, and the record each one is attached to
Crew, subs, and owners

The right slice, nothing more.

  • Crew reach the PM and their project channel from the portal — no download, no password
  • Subs discuss their own scope, their own invoices, and their own dates
  • Owners comment on the client portal — on updates, change orders, and draw requests
  • Budget detail stays on the company side unless you share it deliberately
ExpenseThread PhotoThread Purchase requestThread Time entryThread InspectionThread Sub invoiceThread Change orderThread Schedule itemThread
See threads on expenses See the crew portal

Stop scrolling for the answer you already got.

Messages, channels, and a thread on every record. One project free, every feature, no card.