We are exploring a product direction for ANKK and would value feedback from people who regularly report social media work to clients, teammates, or partners.

The problem we keep seeing is not a lack of metrics. It is the work required to turn multiple dashboard screenshots into a result someone else can understand. The recipient still needs the date range, the content that was published, and an explanation of why a number matters.

We created five concept formats:

1. Big Number one result that represents the period.

When a scheduled social post looks wrong, did the API return success? is usually the least useful recovery question.

Before retrying, I want five fields in one place:

1. the channel and exact account;

2. the scheduled time and timezone;

A recent Make Community case reported one scenario run, one input bundle, and one returned Facebook post ID but two public Facebook posts.

The first recovery question is not should I rerun it? It is could the provider already have accepted a write that my execution log does not fully explain?

Before any replay:

1. freeze the scenario and export the execution;

One launch-day reconciliation rule became very concrete today: a provider accepting a request or even marking it scheduled does not prove that the post is live.

For every channel, we keep three pieces of evidence separate:

1. the terminal publication state,

2. the provider-original post URL,