Run SophMate Slash Commands and Built-in Playbooks

Outcome

By the end of this tutorial, you will know how to use SophMate for SophMate slash commands while keeping the work reviewable inside WordPress.

Scenario

A store operator repeats the same weekly reporting, campaign, and support prompts and wants a faster, more consistent way to run them.

What the image shows

The tutorial image shows Copilot in wp-admin so the reader can connect the workflow to conversation history, slash commands, prompts, and the point where an answer may become a reviewed action plan.

Before you begin

• Confirm SophMate is active and the relevant module is available to your user role.
• Check provider, budget, and approval settings before asking SophMate to draft or execute work.
• Keep customer data, API keys, and private credentials out of prompts unless the workflow is explicitly designed to handle that context.

Guardrail

Keep read-only questions conversational. When Copilot suggests changing products, coupons, content, customers, or settings, turn the recommendation into a reviewed plan.

Common mistakes to avoid

• Starting with a broad command when a bounded read-only question would produce a safer answer.
• Saving order-specific or private customer details into long-term memory.
• Letting a recommendation turn into manual edits without a reviewed action plan.

Step 1: Type the slash trigger

In Copilot, type / to open the playbook autocomplete. Search by slug or title, then select the playbook that fits the task.

Step 2: Check the playbook type

Analytics and chat playbooks return answers. Action plan playbooks, such as coupon builders or bulk product updates, create reviewable change plans.

Step 3: Fill parameters deliberately

Use clear values for product IDs, time periods, discount amounts, order IDs, tone, or campaign goals. Parameter prompts keep templates reusable without making them vague.

Step 4: Review output before reuse

If a playbook output will be reused weekly, confirm that it includes the metrics, caveats, and internal links your team expects.

Step 5: Export proven custom playbooks

Agencies can export custom playbooks after they have been tested on a client site, then import them into similar sites with local adjustments.

Review checklist

• Users understand which playbooks can modify data.
• Required parameters are complete.
• Custom playbooks are tested before agency reuse.

Success signal

The workflow is successful when Copilot produces a bounded answer, the user can verify the context, and any site-changing next step becomes a reviewed plan rather than an untracked edit.

What to document

Document the prompt pattern, useful follow-up questions, source context used, and the point where the conversation should become an action plan.

Owner and cadence

The workflow owner should review this pattern after the first few uses, then promote stable prompts into playbooks when repeated work is clear.

Escalate when

Escalate when Copilot cannot access expected context, suggests unsafe changes repeatedly, or produces answers that cannot be verified from visible sources.

Related SophMate paths

• Features/Playbooks
• Features/Action Plans Approvals

Next action

Run this workflow on a low-risk example first. Once the result is easy to review and explain, decide whether it should become a repeatable playbook, workflow, watcher, agent, or documented team process.