Install SophMate

Requirements

SophMate is installed like a normal WordPress plugin, but the site should meet the baseline requirements before the team starts using AI workflows. Confirm WordPress version, PHP version, OpenSSL, outbound HTTPS, and administrator access before uploading the package. If an agency manages the site, decide who owns provider billing and who reviews site-changing work before the plugin is activated.

Installation flow

Upload the plugin package in WordPress, activate it, and open SophMate from wp-admin. Review the settings screen before adding keys. The practical installation tutorial walks through the first provider test, while the diagnostics feature explains what to capture when hosting blocks outbound requests.

Verification

After activation, confirm that Copilot, settings, diagnostics, approvals, and docs links are visible to the expected administrator role. Do not invite editors, support users, or marketers until roles and permissions and approval behavior are mapped.

Owner and cadence

• Primary owner: site administrator or agency implementation lead.
• Review cadence: during initial setup, after hosting changes, and before adding new SophMate users.
• Escalate when setup cannot be repeated, diagnostics are unclear, or the team cannot identify rollback and support owners.

Production checklist

• Install from the release package, activate only on the intended site, and verify the SophMate admin menu appears for the expected administrator.
• Run the first provider connection test before enabling team access or automation.
• Record the setup owner, production site URL, staging site URL, SophMate version, WordPress version, PHP version, and active theme before rollout.
• Confirm the team can reach diagnostics and support and knows where to pause high-risk activity.

Acceptance checks

• SophMate loads in wp-admin without PHP errors, missing assets, or permission warnings.
• Diagnostics can identify environment status without exposing provider credentials.
• A trusted administrator can repeat the setup path without relying on private notes or one person's memory.
• The team has a documented rollback or support path before any write-capable workflow is enabled.

Common mistakes

• Activating on production first when staging, backup, or restore ownership is still unknown.
• Inviting the wider team before provider, diagnostics, permissions, and rollback ownership have been verified.
• Treating a successful admin page load as proof that hosting, outbound HTTPS, backups, and support routing are ready.

Related operations

• Continue with Connect an AI Provider.
• Follow the installation tutorial for a practical setup walkthrough.
• Use First-Run Checklist before inviting non-administrator users.
• Use Copilot Prompting and Context before team members rely on chat output.
• Use Environment and Hosting Checklist when provider or fetch tests depend on host behavior.
• Use Staging Test Data and Demo Hygiene before testing with production-like records.
• Use Operator Training and SOP Rollout before broad team adoption.