Scheduling Posts

For most customers, the Scheduler, available at Tracy Social AI -> Configuration -> Scheduler in the left nav, is the optimal way to setup and maintain a regular cadence of Social Posts

Schedule Rules allow you to configure one or more rules that periodically automatically generate a Social Post record. Schedule Rules are configurable to provide a great deal of flexibility and variety in your Social Post content and timing.

The Schedule Rule form is organized into sections to simplify configuration:

• Main Form: Core configuration information about the Schedule Rule

• Post Content: Configuration affecting the resulting Social Post content

• Run Schedule: Details about when to run the Schedule Rule

• Post Schedule: Details about when to post the resulting Social Post

Main Form

Post Content

Run Schedule

Post Schedule

Main Form

• AI connector: AI Connector to be used for Social Post content generation
• AI model: AI Model against which the Social Post content will be generated
• Social platforms: The Social Platforms to which the Social Post will be sent
• Skip draft: If enabled, the resulting Social Post will skip the 'Draft' state

• Approval group: Default group to approve content of the Social Post before posting. If left blank, the approval stage will be skipped

• Last run: Indicator of the last time the Schedule Rule was run

All configurations on the Schedule Rule can be overridden on the resulting Social Post record, if desired. The Schedule Rule is the ideal place for the 'default' settings that are typically used.

Post Content

Prompt

• Prompt type: Determines how to select the AI Prompt used for the Social Post

  • Static: Use a specified AI Prompt

  • Random: Use a random active AI Prompt from the AI Prompt table

  • Filtered: Use the first AI Prompt returned from a filtered list of active AI Prompts

  • Random Filtered: Use a random active AI Prompt from a filtered list

  • Scripted: Define an AI Prompt via script. This can be a new text AI Prompt or the SysID of an existing AI Prompt record.

Persona

• Persona type: Determines how to select the AI Persona used for the Social Post

  • Static: Use a specified AI Persona

  • Random: Use a random active AI Persona from the AI Persona table

  • Filtered: Use the first AI Persona returned from a filtered list of active AI Persona

  • Random Filtered: Use a random active AI Persona from a filtered list

  • Scripted: Define an AI Persona via script. This can be a new text AI Persona description or the SysID of an existing AI Persona record.

Context Statements

• Context statement type: Determines how to select the Context Statements used for the Social Post

  • Static: Use one or more specified Context Statements

  • Random: Use a random active Context Statement from the Context Statement table

  • Filtered: Use the first Context Statement returned from a filtered list of active Context Statements

  • Random Filtered: Use a random active Context Statement from a filtered list

  • Scripted: Define an array of Context Statements via script. These can be new text Context Statements or SysIDs of existing Context Statement records.

Instruction Statements

• Instruction statement type: Determines how to select the Instruction Statements used for the Social Post

  • Static: Use one or more specified Instruction Statements

  • Random: Use a random active Instruction Statement from the Instruction Statement table

  • Filtered: Use the first Instruction Statement returned from a filtered list of active Instruction Statements

  • Random Filtered: Use a random active Instruction Statement from a filtered list

  • Scripted: Define an array of Instruction Statements via script. These can be new text Instruction Statements or SysIDs of existing Instruction Statement records.

If you need to use highly dynamic data within your Prompt, Persona, Context Statement, or Instruction Statement scripts to best inform the content of your Social Post, you can do so by creating a scratchpad variable as part of the Run Condition script explained in the Run Schedule section below.

This allows you to dynamically gather information at run-time, which can then be used in each of the scripts above.

Post Options

• Social options script: Optionally, a script to generate a JSON object defining additional options to be added to the request payload sent to the Social Platform

Run Schedule

• Run: On what cadence to run the Schedule Rule

  • Once: Run only once, at the time specified

  • Periodically: Run periodically, starting on the date specified and repeating at the specified interval

  • On Demand: Run only when the Run Now button in the form header is clicked

• Run conditionally: Use server script to set 'answer' to true/false. If answer=true, the rule will proceed to generate a Social Post. If not, the rule will cancel.

Within the Run condition script, you can add content to a scratchpad object, similar to a workflow or business rule. This scratchpad can then be reference within any of the scripts listed in the Post Content section above. For example:

scratchpad.nowDate = new GlideDateTime();

This powerful capability allows you to programmatically gather and/or generate data to be used within your Schedule Rule and resulting Social Post.

Post Schedule

• Post: When to send the resulting Social Post to the Social Platforms

  • Immediately (Upon Approval): Send immediately upon approval of the Social Post. If no Approval Group is specified, the Social Post will be submitted immediately with no approval step.

  • At Specific Time: Send at the time specified

  • Within Schedule: Post at a random time within the provided Schedule

  • On Demand: Post only when the Post Now button in the form header is clicked