Selection criteria

Provider and model choice should be based on the work SophMate will perform: read-only Copilot answers, WooCommerce summaries, Theme Assistant design review, Image Studio assets, agents, workflows, and support drafts may have different cost, latency, and capability needs. Do not choose a model only because it is the newest or cheapest.

Fallback planning

Document whether the team should pause work, retry, switch provider, reduce workflow scope, or escalate when a provider fails. Pair provider choices with budget and usage controls, security and key rotation, and troubleshoot provider connections.

Production review

Review provider behavior after billing changes, model deprecations, high-volume campaigns, agent launches, workflow failures, and latency spikes. The provider setup tutorial covers first connection testing, but production teams should keep a written model ownership note.

Owner and cadence

Primary owner: site administrator with provider, billing, and security responsibility.
Review cadence: after provider, mailbox, role, budget, security, WooCommerce, or integration changes.
Escalate when provider choice affects privacy, cost, latency, model access, workflow reliability, or customer-facing output quality.

Production checklist

Document model purpose, capability, budget, latency, privacy expectation, fallback behavior, and owner before team rollout.
Re-test provider behavior after billing changes, model deprecations, workflow failures, and high-volume campaigns.
Document who owns provider credentials, budget limits, role access, notification routing, and ongoing review.
Keep configuration changes behind administrator access and review them after plugin updates, staff changes, or incidents.

Acceptance checks

The team knows whether to pause, retry, switch provider, narrow scope, or escalate when provider behavior changes.
Provider/model choices are connected to budgets, key rotation, diagnostics, and support routing.
A second administrator can explain why each high-risk setting is enabled and who may change it.
No production credential, support mailbox, or notification path depends on an unmanaged personal account.

Common mistakes

Switching providers for cost without checking model access, quality, latency, privacy, and fallback behavior.
Using personal provider keys, personal mailboxes, or broad administrator access because it is faster during setup.
Changing budgets, roles, notifications, or integrations without recording the owner and review reason.

Start with Connect an AI Provider.
Troubleshoot failures with Troubleshoot Provider Connections.
Pair configuration work with Roles and Permissions.
Review Approval Controls before enabling write-capable modules.
Use Cost Allocation and Client Billing Review before client or team billing reviews.
Use Security and Key Rotation before changing provider credentials.
Use Cache Queue and Performance before scaling automation or alerts.
Use Scheduled Task and Cron Reliability before relying on recurring work.
Use Provider Models and Fallbacks before changing production model behavior.
Use Data Residency and Provider Policy Review before sending sensitive context.
Use Provider Rate Limits and Retry Planning before high-volume automation.
Use Source Freshness Review Calendar before teams depend on policy sources.
Use Email Deliverability and Domain Authentication before operational mail matters.

Provider Models and Fallbacks