Every Auto Scheduler run starts from somewhere — a default tone, a default prompt structure, a default sense of what “good” looks like for a given site — and knowing where those defaults actually come from matters the first time a scheduled batch doesn’t sound quite like what you expected.
Defaults Inherit From Site-Level Settings First
Before any individual scheduling job runs, Auto Scheduler pulls its baseline prompt structure and tone from the site-level content settings configured for that WordPress connection — the same tone setting (informative, persuasive, conversational) and any voice guide notes that apply to manually generated content also apply to scheduled content, unless something more specific overrides them.
Category and Workflow-Level Overrides
Above the site default, individual workflows or categories can carry their own tone and prompt overrides — useful when one part of a site (say, technical documentation-style posts) needs a different register than the rest of the site’s default voice. These overrides apply only within their scope, falling back to the site default everywhere else.
What Happens With No Explicit Settings at All
A brand-new site with no tone configured yet doesn’t generate with no direction — it falls back to a general-purpose informative default, reasonably neutral but not tuned to any particular brand voice. This is a fine starting point but not a substitute for actually configuring a voice guide once there’s a real house style to encode.
How Prompt Structure Differs From Tone
Tone governs register; the underlying prompt structure governs shape — how the post opens, how sections are organized, whether a “where to go next” style closing is included by default. This structural template is a separate, lower-level default from tone, and it’s shared across scheduled generation regardless of which tone is active.
Where Custom Instructions Fit In
Any custom instructions added at the workflow or individual scheduling job level layer on top of the site and category defaults rather than replacing them outright — a specific instruction (“always mention the free trial”) adds to the baseline prompt rather than requiring the whole prompt to be rebuilt from scratch each time.
Auditing Where a Specific Output Actually Came From
When a scheduled post’s tone or structure looks unexpected, tracing it back through this hierarchy — site default, then category or workflow override, then any job-specific instruction — usually locates exactly which layer produced the surprising result, rather than treating it as an unexplainable one-off.
Where to Go Next
For the complete Auto Scheduler and workflow picture, see the complete guide to scheduling and workflow automation.
