# The signal that came back

> A system event becomes a resolved human loop when its acknowledgement returns through a signed outgoing webhook.

- Published: 2026-09-03
- Author: PingRoom
- Theme: Better work
- Topics: incoming webhooks, outgoing webhooks, human response
- Canonical: https://pingroom.io/stories/the-signal-that-came-back
- Cover image: https://pingroom.io/stories/the-signal-that-came-back.webp
- Cover description: A red signal travels from an abstract server to a human hand and returns as a sealed response

An incoming webhook turned a system event into a Ping.

But delivery was only half the loop.

A confirmation request stayed open while a person responded.

A signed outgoing webhook returned the acknowledgement with the same correlation ID.

Software rang the room.

A person confirmed it.

Software knew what happened next.

The useful path was never only from a server to a phone.

It was from an event to a human response—and back.