Install SophMate and Complete the First Provider Test

Outcome

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

Scenario

A store owner has installed SophMate from CodeCanyon and wants to verify that the AI provider works before editors start using Copilot.

What the image shows

The tutorial image focuses on the SophMate Settings provider tab, where the AI provider, encrypted API key status, connection test, and first-run setup controls are visible.

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

Do not share provider keys in prompts, screenshots, or support requests. Use Diagnostics for status evidence and keep budget changes owned by an administrator.

Common mistakes to avoid

• Testing provider setup with a shared personal API key instead of a site or client-owned key.
• Skipping the connection test and discovering outbound HTTPS or extension problems during a live workflow.
• Sending diagnostics screenshots that expose secrets instead of using the support-safe report.

Step 1: Confirm server requirements

Check WordPress version, PHP version, OpenSSL, DOM, iconv, and outbound HTTPS access. SophMate uses encrypted provider keys, so extension and connectivity checks should pass before live use.

Step 2: Open SophMate settings

Go to SophMate > Settings, choose the AI provider, paste the provider API key, and save the configuration. Use a provider key created specifically for this site or client account.

Step 3: Run the provider test

Use the Test Connection control and read the result. A successful test proves the WordPress server can reach the provider and that the key is accepted.

Step 4: Set budget limits

Configure the monthly site budget and daily per-user limits before inviting more users. Start conservative, then raise caps once real usage patterns are visible.

Step 5: Record the setup state

Keep a note in your launch checklist with provider, budget, and administrator owner. If support is needed later, include the diagnostics report rather than exposing secrets.

Review checklist

• Settings show the provider you expect.
• The connection test passes.
• Budgets are set before non-admin users start using Copilot.

Success signal

The setup is working when the provider test passes, diagnostics show expected connectivity, budgets are configured, and no support-ready evidence exposes the provider key.

What to document

Document provider ownership, budget owner, connection-test result, diagnostics status, and who may change settings later.

Owner and cadence

A site administrator should own this setup and revisit it after provider, budget, hosting, or team-access changes.

Escalate when

Escalate when diagnostics continue to fail after provider, budget, and hosting checks are verified.

Related SophMate paths

• Features/Copilot
• Features/Diagnostics

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.