01 / Product team automation
Turn shipped engineering work into clear product updates, resolved tickets and informed customers.
Explore each part of the workflow.
The gap
Customer reports become tickets. Engineers implement the work. But keeping the product team informed and following through with customers still needs coordination. A ticket status alone does not explain what changed, or confirm that it is live.
Explore each part of the workflow.
What I built
I built a workflow that waits for confirmed rollout, gathers the released work and uses an LLM to create a clear product summary. It then updates the related tickets, connecting team communication and customer resolution to what is actually live.
Explore each part of the workflow.
The system
Start with customer feedback or select Engineering ticket to begin with internal work. Advance one step at a time.
Customer feedback received
The story can begin with a customer support report. Linking it to an engineering ticket preserves the relationship needed to notify the affected customer when the fix is live.
What changed
Engineering activity becomes a non-technical summary with links back to the source work.
Related tickets get the released version, a comment and an automatic move to Done.
Customers with linked reports hear when their fixes have been resolved and released.