Skip to content
The WP Godmode Free plan is here!
Documentation
Start > Documentation > Client-Facing Agent UIs

Client-Facing Agent UIs

WP Godmode agents can be exposed to clients through a branded WordPress admin interface. Instead of giving clients access to the full WP Godmode workspace, agencies can build a focused plugin page or dashboard widget that triggers one approved agent workflow.

White label AI agent interface inside the WordPress admin dashboard
Example of a white label agent interface inside WordPress admin.

What it does

A client-facing agent UI turns a repeatable agency workflow into a simple WordPress admin tool. Clients can upload source material, fill in a few fields, and run a controlled process such as importing a blog post, creating content, updating products, or managing team profiles.

The interface can use the agency’s own branding, wording, colors, and permissions. The client sees a clean agency-built tool, while the agent handles the structured work behind the scenes.

Before you start

Make sure the godmode-agent-triggers skill is installed under Godmode > Skills. It enables custom code on the same WordPress site to trigger approved agents from a plugin, dashboard widget, snippet, integration, or site event.

Godmode agent triggers skill installed in the Godmode Skills screen
The agent trigger skill must be installed before custom UI code can call an agent.

How to build one

  1. Create the agent in WP Godmode. Define exactly what it should do, what input it needs, and what rules it must follow.
  2. Test the agent in chat until the workflow is reliable. For example: create Gutenberg drafts from Word documents, assign categories, add featured images, and suggest internal links.
  3. Ask WP Godmode to build the client UI, for example: Build a plugin or dashboard widget that triggers my agent “Blog Importer”.
  4. Add UI requirements such as fields, labels, helper text, agency branding, role access, and optional screenshot-based design direction.
  5. Restrict access to the right users or roles, such as editors, shop managers, or content teams.

Common use cases

  • Blog importers that turn client documents into Gutenberg drafts.
  • Content writers that create posts from a short client brief.
  • WooCommerce tools for product descriptions, metadata, and updates.
  • Team member managers for structured staff profile creation.
  • Documentation, FAQ, or page update workflows for recurring content work.

Access and branding

Agencies can decide who sees the interface and what each role can do. The UI can be shown only to selected WordPress roles, while technical settings remain hidden from the client.

This makes agent workflows easier to sell, easier to repeat, and easier for clients to use without exposing the underlying implementation.

Table Of Contents

Reset your password

Verify it is you

Enter your account email and we’ll send you a link to set a new password.

Enter the verification code for this account to finish signing in.