Skip to content

Planning the week with the Social Operator

How the Social Operator gathers evidence from your own recorded activity, proposes at most six things to do this week, and why it never acts on its own.

Updated

The Social Operator reads what your workspace has actually recorded over the last four weeks and proposes what to do this week. It suggests; it never acts. Nothing it produces publishes, sends or schedules anything.

Each proposal names what it was based on: how many records, from which source, at what scope, over what dates. There is no default plan, no filler suggestion and no advice that no record supports. A week with nothing wrong in it produces nothing, and the page says so.

BEFORE YOU START

  • The "administer" or "moderate" permission to plan, cancel or retry a week. Reading the page needs workspace access only.
  • Access to the workspace, and active membership of the organisation.
  • Some recorded activity. With nothing recorded, the run finishes with the reason that no signals were recorded.

STEPS

  1. Open Social Operator for the workspace, or go to /app/workspaces/{workspace}/operator.
  2. Read the note at the top: the Operator suggests, and it never acts on its own.
  3. Choose "Plan this week". The run is keyed to this workspace and this week, so pressing it twice does not plan twice.
  4. Read the status line. It gives the run's state and its autonomy level, and a reason where there is one.
  5. Read each proposal and the evidence line beneath it, which names the records it counted and the limitations on them.
  6. Work through "Proposals waiting on you" underneath, which lists the approvals the Operator raised.
  7. If a run failed or was cancelled, choose "Retry week of ..." to run it again.

WHAT YOU SHOULD SEE

Up to six proposals, ordered by what is blocking most: accounts to reconnect, failed publishes to investigate, an approval backlog to clear, open conversations to answer, an empty week to fill, and recorded results to review. Each carries the count it came from.

WHAT THIS WILL NOT DO

  • It will not publish, send, schedule or reply. Every proposal is something for a person to do.
  • It will not tell you the best time to post. That signal is deliberately absent from what it gathers.
  • It will not say a week is empty unless your own posting history supports the comparison. The "nothing is scheduled" proposal is raised only when there is enough history to say so, and its wording states that it is the absence of scheduled rows, not a prediction that posting would perform better.
  • It will not charge credits. Every proposal is estimated at zero and nothing about a plan calls a provider.
  • It will not show run history. Only the most recent week is on the page.

WORTH KNOWING

The mobile app has a screen at the same name that is a different thing: a triage list of approvals, publishing problems and connection problems, with no weekly plan and no proposals. The weekly Social Operator exists on the web only.

IF IT DOES NOT WORK

  • "No week has been planned for this workspace yet." means nothing has been run.
  • "Nothing to suggest for this week." is a real result. There is no failed publishing, approval backlog, connection problem or open conversation recorded.
  • "administer or moderate permission required." means your role cannot plan, cancel or retry.
  • "Only a queued or running run can be cancelled." and "Only a failed or cancelled run can be retried." are the two lifecycle refusals.
  • "The plan could not be prepared." and "The week could not be retried." are the fallbacks when the server gave no message.
  • A run whose reason is that no signals were recorded is not a failure. There was nothing to read.

COMMON QUESTIONS

Can I let it act for me?

There is an autonomy setting, and the level that would let a proposal execute routes every action through the action gate first. The default is to suggest only, and nothing on this page changes that for you.

Why at most six?

Because it proposes what is blocking, in order, and stops. A longer list would be padding.

Does it learn my preferences?

No. It reads your recorded activity each time it runs and holds nothing between runs except the run record itself.

  • What needs you, on your phone

    The mobile triage screen that gathers approvals waiting on you, publishing that failed, and connections that will stop a post, and how it tells you when it could not check something.

  • What your recorded results support

    Reading the performance recommendations, the sample size every claim must clear, and the list of questions the recorded data cannot answer.

  • Working through the publishing queue

    Reading the real state of every scheduled, in-flight, published and failed post, what retrying does, and which networks can actually receive a post today.