Inbox

The Inbox is the surface you actually work. Ballad plans and drafts overnight; in the morning the Inbox holds what's going out today, the drafts waiting on a yes, and the decisions it wants from you. Reaching the bottom of it is the whole job most days.

It's a list on the left and one thing at a time on the right. Nothing stacks up in front of you.

What lands here

Sections appear in the order you'd act on them, and a section you have nothing in doesn't show at all:

Section	What it is
Today	What publishes or posts today, so nothing surprises you.
Approve	Drafts waiting on a yes: posts, threads, image posts, articles, issues, release notes.
Replies	Replies to your posts, each with an answer drafted.
Conversations	Threads in your buyers' communities worth joining, reply drafted.
Questions	Ballad's interview questions before it writes a depth piece.
Customers	A customer worth asking for a story, and their answers when they come back.
Launches	A proposed launch week for a release or an article.
Refresh	An older article that has started to slip.
Battlecards	A competitor changed their site; here's the proposed update.
Website	What the weekly site audit found and thinks you should fix.
Numbers	The two-day-later check for posts Ballad can't read numbers for itself.
Plan	A change Ballad wants to make to the plan, as a diff.

During setup there's one more, pinned above everything: Welcome to Ballad, holding the walkthrough for each thing you asked Ballad to run. It stays until it's empty. See Getting started.

Reviewing a draft

Select a row and it opens in the pane beside the list: the editor on the left, the finished piece on the right in the frame of wherever it's going — a LinkedIn post that looks like LinkedIn, a thread post by post with character counts, an article as the page it will become.

Edit anything before you approve it. Your edits are the training data: change a phrase often enough and Ballad stops writing it.

Approving and rejecting

• Approve publishes it on its slot, or now if that's what it was asked for.
• Approve all sits in a section header when you're happy to clear a batch. The filters beside it narrow that batch to one channel, format or voice first.
• Reject asks why in one line. That line isn't filed away — it goes into what the analyst reads, so the reason shows up in the next plan rather than in the next draft.

Nothing publishes, posts or sends without one of those.

Keyboard and deep links

• j and k — or the arrow keys — move through the list; Escape closes the detail on a phone.
• After a decision the next entry takes the old one's place, so a run of approvals is one key and one click each.
• Every entry has its own address: /inbox?focus=approve:<id>. That's what Slack cards and email nudges link to, so a notification opens the exact thing it's about.

On a phone the list is the page, and a row opens the detail over it with a back bar.

Next

• Content — the calendar behind what lands here.
• Loop — where plan decisions come from.
• Getting started — the setup walkthroughs.