Tracked actions

Overview#

Tracked Actions is the worklist of everything you have committed to. Anything you decide to act on lands here and stays until it is done: content suggestions you kept, PR placements you took on, fixes proposed against a topic, sentiment work, customer stories to collect after a competitor published theirs, and whatever came out of a conversation with the Advisor.

It is not a diary you fill in. Almost everything here arrives because you accepted a proposal somewhere else in Seerly, and the screen exists so that those decisions live in one place instead of scattered across the screens that produced them.

Two tabs: Active for what is outstanding, Completed for what is finished. Marking something complete moves it across rather than deleting it, which is what leaves you with a dated record at the end of a quarter.

The attribution problem#

AI visibility moves slowly and from several causes at once. Three months in, visibility is up and you have done six things. Which one worked?

Without a record, the honest answer is that nobody knows, and the answer people give is whichever thing they advocated for. The Completed tab is that record: a dated list of what was actually done, which you can read against the trends on Visibility and Analytics.

That is the difference between "AI visibility improved" and "these two changes moved it, and these four did not", which is what decides where the next quarter goes.

Interpreting results#

Comparing the dates here against a trend is something you do yourself; completed actions are not drawn onto the charts. Movement following an action is suggestive rather than proof either way. Several things are always in flight at once, and AI answers vary on their own without anybody's help, so a dated list narrows the field of plausible causes rather than settling the question.

Lag is expected, and it varies quite a lot by the kind of action. A technical fix can surface within a cycle or two. A published page has to be discovered and indexed before anything can happen at all. A directory listing can take a good while to be picked up. Reading a two-week window and concluding that the directory listing did nothing is a mistake people make regularly.

An absence of movement is a finding in its own right, and a useful one. An action that produced no effect after several cycles is worth knowing about precisely because it stops you doing more of the same thing next quarter.

Panels and controls#

Actions arrive from several places and the screen groups them by source, covering Agent Suggestions, Content suggestions, Brand reputation actions, Advisor Chat and Competitor intelligence. This is not purely a manual log, then: work that Seerly proposed for you lands here alongside whatever you added yourself.

Mark Complete closes an action and Reopen brings it back. Tracked and Untrack control whether something counts toward your timeline at all, and Dismiss action removes a proposal you have no intention of doing. Focus Keyword and Secondary Keywords attach the terms an action was aimed at, which is what makes it possible to connect it to movement weeks later rather than eyeballing two charts side by side. Create Content starts a draft from an action, and View content or View conversation opens whatever produced it. No tracked actions yet is the empty state on a new project.

A tracked content suggestion has an Edit button until content starts generating from it. It opens the same form as View on the Suggestions screen, so the title, brief, rationale and both sets of keywords can be corrected before you use Create Content.

Create Content always shows what the draft will start from before anything is created. For a content suggestion that is the same form, where Generate confirms. For other actions it is a summary of the title, brief and keywords that you confirm or Cancel.

Tracked action

Publish a comparison page for agency project management

Source

Content suggestions

Focus Keyword

project management for agencies

Secondary Keywords

agency time tracking, client onboarding

Status

Tracked

Collecting customer stories#

When a competitor pushes customer stories (testimonials, transformation stories or success stories), Collect customer stories on the Competitor intelligence page, under Competitors, adds an action here and opens it. Seerly doesn't write stories like these for you, since that would mean inventing customers and results; it helps you ask your own customers instead.

In the list the row reads Collect customer stories, with the competitor's name and the source Competitor intelligence. Its detail starts with what the competitor published: the title, how many pages, a few sample titles, and the topics they cover.

Draft the kit then writes what you need to ask for a story: a WhatsApp message, an email (subject and body), four to six questions to ask the customer, shaped by what the competitor's stories covered, a consent line asking permission to publish that offers first name only or anonymity, and up to three tips. The kit never invents a customer, a result, a quote or a number. Where one belongs it leaves a placeholder such as [Customer name] for you to fill in.

Every part is editable and has its own Copy button, and Save edits keeps your changes. Regenerate writes a fresh kit in place of the current one and shows how many regenerations are left: each action gets two, after the first draft. Once you have your stories, Mark Complete moves the action to Completed, where the kit stays readable and copyable, and Dismiss removes it if you decide not to ask. If you complete or dismiss the action before drafting a kit, its detail simply says no kit was drafted for it.

Best practices#

• Logged as you go. Reconstructing three months afterwards produces a fiction with convincing dates on it.
• Specific rather than general. "Published comparison page for X" is worth something later; "content work" is not.
• Everything relevant, not only content. Technical fixes and third-party listings frequently move more than publishing does.
• Enough separation to attribute anything. Six changes made in one week cannot be told apart afterwards by any method.

Next steps#

1. Log it at the moment you do it. Thirty seconds then is worth more than an hour of reconstruction later.
2. Include the non-content actions. Getting listed on a directory that already gets cited is often the highest-impact thing anybody does in a given month, and it is the thing least likely to get written down.
3. Review against trends monthly rather than weekly, since weekly is too short for most of these to have surfaced.
4. Use it in reports. A brand report connecting actions to movement is far more useful to a reader than one showing numbers on their own.

What to keep in mind#

Tracked Actions records what you tell it and nothing else. It does not detect changes automatically, so anything left unlogged is simply invisible to the timeline.

Correlation is also not proof. It narrows the field of plausible causes; it does not settle which one was responsible.