Follow-ups and daily briefings

In most tools, an unanswered message just sinks until the customer gives up. In työ, every request is a unit of work that knows it isn't finished. It resurfaces in your daily briefing, escalates to a teammate when it waits too long, and only goes quiet when someone actually closes it.

What it does

Every customer request in työ has an identity of its own: it knows what it's about, who it's waiting on, and whether it's done. Until it's resolved, it keeps itself visible — in your daily briefing each morning, alongside everything else that still needs a decision.

If something waits too long, työ doesn't just wait with it. The work escalates to a teammate — in their language — so a question doesn't stall because one person had a busy afternoon. When it's handled, it closes out cleanly and stops asking for attention.

Why it matters

In a small business, the owner is the safety net. You're the one lying awake wondering whether anyone answered the catering inquiry from Tuesday. A shared inbox doesn't help with that — it shows you a pile of threads that everyone watches and no one owns.

An unanswered message has a real price. The customer who asked about a table for twelve doesn't write again; they book somewhere else, silently. Follow-ups turn that silence into something you can see: every open item has a place, an owner, and a way back to the surface.

How it works

When a request comes in, it becomes a work unit routed to the right person, with an AI draft ready for review. From that moment the unit tracks its own state — drafted, waiting for sign-off, waiting on the customer, resolved.

Anything unresolved appears in the daily briefing: a short, plain summary of what's open and what's stuck. If a draft sits unapproved past the limit you've set, the work escalates to the next teammate. Nothing depends on someone remembering to check — the work remembers for you.

Frequently asked questions

What's in the daily briefing?

The open items: requests waiting for a reply, drafts waiting for sign-off, and anything that has been quiet too long. One short summary instead of an inbox to scroll.

What happens when something waits too long?

It escalates to a teammate, in their language, with the context attached. The customer doesn't have to write twice for their question to move.

Does an escalation send anything to the customer?

No. Escalation moves the work inside your team. The customer only ever receives messages a person has reviewed and signed off.

Can I just ignore the briefing on a quiet day?

Yes — it's a summary, not a siren. But the items in it don't disappear when the briefing does; they come back until someone closes them.

See for yourself how työ handles your customers.

See it live — open the demo workspace