Owl & Kestrel Night Atlas · Enquiry handling

Speculative demonstration · Fictional data · Local only

A clear path from enquiry to follow-up.

A small interaction model showing how an enquiry can be accepted by a CRM while a separate notification is still waiting, delivered, or in need of an explicit retry.

Every action runs in this page only. No data is saved or sent to a real CRM or email service.

Ready. Choose a scenario to begin.

Incoming enquiry

FICTIONAL
Contact
Alex Example
Email
alex@example.test
Enquiry ID
ENQ-2048
Idempotency key
form-ENQ-2048-v1

“I’m exploring support for a small product launch and would like to understand the next step.”

CRM record

NOT SUBMITTED
CRM status
Not submitted
Record ID
—
Accepted rows
0

The local simulation has not processed this enquiry yet.

Notification

NOT ATTEMPTED
Delivery status
Not attempted
Simulated attempts
0
Delivered count
0

Notification delivery is tracked separately from CRM acceptance.

What this illustrates

SIMULATED

The same enquiry and key resolve to one CRM row. A duplicate replay reports that row and never silently retries a failed notification or repeats a delivered one.

0Process calls
0Duplicate replays
0Explicit retries
  1. 1. AcceptThe CRM result is recorded as its own status.
  2. 2. NotifyDelivery has a separate result and counter.
  3. 3. Retry deliberatelyOnly the retry button attempts a failed notification again.

Preview boundary: this is a speculative interface demonstration. It has no live CRM or email integration, makes no external submissions, and does not imply an Owl & Kestrel client result or endorsement.