What happens when an automated workflow needs a person?
Hi everyone, I’m Ed, the maker of Wotcha 👋
Wotcha started with a simple interaction: you ask someone to do something, they tap “I’ve got it”, and you both know who’s taken it on and when it’s done.
While preparing for our Product Hunt launch, I’m exploring a question:
What if a person didn’t always have to start the handover?
A few examples:
A website enquiry arrives. Someone needs to contact the customer.
An AI agent finishes a proposal. Someone needs to review it before it goes out.
An equipment alert fires. Someone needs to check the problem.
The idea is that each event could initiate a Wotcha with the details of what needs doing. A person would still explicitly accept it, and completion would stay visible.
I’m calling this Connected Routines. It’s in early development, not part of the publicly released app yet.
The bit I’m interested in isn’t generating another notification. It’s what happens afterwards. Has somebody actually taken this on, or has the system simply told several people and hoped for the best?
Automation tools already create tasks and send alerts. I want to explore whether the human handover can feel simpler and clearer, without asking people to manage another project.
From the recipient’s point of view, it would still be an ordinary Wotcha. Different starting point, same “I’ve got it”.
What’s a real situation where software notifies you about something, but you still end up chasing someone to deal with it? Which system does it start in?
I’d love to understand the actual workflows before deciding which connections to build first.
Ed

Replies