Tweetly Pro auto-publishes, schedules and recycles tweets from WordPress content. It writes per-post tweet templates, queue entries and send timestamps to its own tables and to postmeta keys (typical patterns include tweetly_tweet_template, tweetly_last_tweeted and a queue table for pending and recycled sends). The default Tweetly admin screen lists the upcoming queue and the recent send log, which is the right starting point and a poor place to stop. Editors want send cadence, account split and recycle-versus-fresh share at a glance, not as three different admin tabs.

SleekView Charts reads the same queue rows and send-log entries Tweetly Pro already maintains. A Number card pins tweets sent in the trailing 7 days. A Pie splits sends across the connected Twitter or X accounts so multi-brand operators see which handle the schedule actually serves. A Bar groups tweets by status (Sent, Queued, Recycled, Failed) so a failure cluster is one click away instead of buried mid-list. An Area trends sends per day so a content sprint or a recycle-rule change has measurable before-and-after numbers.

Because the cards read Tweetly's own data, no extra API calls hit Twitter and no second analytics store is needed. Filters carry across the queue table view and the chart view on the same dataset, so a filter for Recycled-only narrows both the row list and every chart card at once.

Tweetly Pro captures real signal: how many tweets actually shipped, which connected account they went out from, how the queue mix shifts between fresh posts and recycled evergreens, and whether the schedule is keeping pace with the editorial calendar. The default queue and history screens turn that signal into paginated lists, which work for spotting the next send and fail at almost everything else a social ops lead does with the data. A KPI card pins the weekly volume, a per-account pie corrects internal assumptions about which handle carries the schedule, a status bar separates Failed from Sent at a glance, and a daily-sends trend confirms whether a recycle-rule change moved the line.

Same queue rows, same send log, completely different reporting posture. The chart view renders the data Tweetly Pro already collects as a dashboard, which is the difference between knowing the queue is moving and knowing whether the schedule is actually working.