Custom Agents

Build a purpose-built agent on top of the Unified Co-marketer, scoped to the data you choose, and told exactly what to look for.

Overview

The Unified Co-marketer provides a conversational experience for campaign, journey, and segment analysis. A custom agent uses the same underlying intelligence for a specific, recurring analysis and follows a defined set of instructions.

A custom agent can be configured with a specific role, selected data domains, and instructions that define what to examine, what not to assume, and how to structure the response. This enables recurring activities such as weekly audits, monthly reviews, and pre-campaign checks to follow a consistent analysis format.

Custom agents are available in Agent Studio, within the full-screen Co-marketer experience.

  • 📘

    👍Start With a Ready-Made Agent

    Each panel includes a set of Netcore-built sample agents under Get started with these on the Agent Studio home. These agents can be used as starting points instead of building an agent from scratch.

    • Run an agent to review the type of output produced by a configured agent.

    • Clone and modify an agent to copy its setup and customise the name, description, domains, and instructions for the required business context.

      Cloning a sample agent provides a predefined structure and output format that can be adapted for a specific use case.

Custom Agent Data Access

A custom agent inherits the Unified Co-marketer data boundary. It can read campaigns, journeys, and segments available on the panel where the agent was created. It does not have access to CRM, order management, finance, or other external systems.

During agent creation, the data boundary can be narrowed further by selecting only the domains required for the intended analysis.

Create a Custom Agent

Follow the steps below to create a custom agent for your panel.

  1. Log in to the Netcore CE dashboard.
  2. Click Ask Co-marketer in the top navigation bar. The Co-marketer opens as a side panel.
  3. Click the Expand icon at the top right of the panel to open the full-screen experience.
  4. In the left navigation, click Agents.

📘### Note

The Agents section is available only in the full-screen experience. The side panel provides the chat experience only. Expand the panel to access Agent Studio.

The Agent Studio home displays:

  • Your agents — Agents already created on the current panel.
  • Get started with these — Netcore-built sample agents available as starting points.

Create an Agent

Click Create Agent at the top right of the Agent Studio home.

Existing agents appear as cards displaying the agent name, description, and selected domains.

Configure the Agent

The agent creation form includes the following fields:

FieldLimit / OptionsConfiguration
Agent Name50 charactersName of the agent. The name appears on the agent card and in the agent picker.
Description300 charactersBriefly describe the analysis performed by the agent and the information it surfaces. The description also appears on the agent card.
DomainsCampaigns · Journeys · SegmentsData domains that the agent is allowed to read. Select only the domains required for the intended analysis.
CapabilitiesDeep Research · Brand WikiDeep Research is required for PDF report generation. Brand Wiki adds configured brand context available on the panel.
VisibilityPublic / PrivatePublic makes the agent available to all users on the panel. Private limits access to the agent creator.

❗️### Enable Deep Research for PDF Reports

Deep Research must be enabled for the agent to generate a downloadable PDF report.

Domains and capabilities are unchecked by default. Deep Research can also be enabled later by editing Tools on the agent page.

Select Data Domains

Select only the domains required for the intended analysis. A narrower domain selection can produce a more focused response.

SelectionBest Suited For
Campaigns onlyBroadcast performance, deliverability, channel mix, content classification, and compliance audits.
Journeys onlyStructural audits covering cadence, silence gaps, dead branches, stage progression, and drop-off.
Segments onlyCohort sizing, recency banding, and coverage gaps.
All threeAnalysis that spans multiple domains, such as identifying which cohorts are covered by journeys and what messages they received.

Add Agent Instructions

After the agent is created, the agent-specific page displays Instructions and Tools in the right rail. Tools contains the configured domains, capabilities, and visibility settings.

  1. Click the Pencil icon next to Instructions.
  2. Enter the instructions in the 5,000-character field.
  3. Click Save Instructions.

A confirmation appears after the instructions are saved, and the saved content is displayed in the right rail.

📘### Configure Instructions

An agent without custom instructions can still respond, but the response remains general. The Instructions field defines the agent's role, analysis requirements, boundaries, and response format.

Most effective configurations use approximately 2,000–2,600 characters. The full 5,000-character limit is not required for most use cases.

Run a Custom Agent

A custom agent can be run from its own page or from a new chat.

From the Agent Page

The chat box on the agent home has the agent already attached. Enter the required prompt and send it.

From a New Chat

  1. Click New Chat.
  2. Click the + icon to the left of the chat box.
  3. Select Custom Agents.
  4. Select the required agent from the list.

The + menu also provides Deep Research as a per-chat option.

Write Effective Agent Instructions

Well-defined instructions help produce consistent and focused analysis.

PracticeWhy It Matters
Define the Role and Data BoundaryState the purpose of the agent and explicitly define the data it can and cannot access. For example: "Order management data is unavailable; order status must never be inferred."
Define Prohibited InferencesExplicitly state information that must not be inferred. Clear boundaries help prevent unsupported conclusions.
Use the Account Baseline as the Primary BenchmarkInstruct the agent to compare results against the account's own trailing median. External benchmarks should be treated as secondary context and presented as ranges where applicable.
Analyse Coverage GapsInclude instructions to identify cohorts, audiences, or areas that are not covered.
Define the Output StructureNumber the required sections and specify where headlines, tables, findings, and other elements should appear.
Define the Closing FindingSpecify the final conclusion or action-oriented finding required in the response.
Define Sensitive Scope ExplicitlyFor agents covering sensitive areas, place the scope boundary at the beginning of the instructions.

Agent Instruction Template

The following template can be adapted to a specific use case and remains within the 5,000-character instruction limit.

ROLE
Audit [what] across [campaigns / journeys / segments]. Work only
from campaign, journey, and segment data. [External system] data
is unavailable. Never infer or estimate [specific forbidden
inferences].

REFERENCE BENCHMARKS & DEFAULTS
Treat the following as conventions rather than measured values.
Verify against the panel and report deviations:

- [Structural convention, e.g. reminder contact commonly begins
  ~30 days before the due date, escalating at 15, 7, 3 and 1 days]

PRIMARY RULE
The account's own trailing baseline always overrides external
figures. Use published ranges only to place the account within a
wide band, never to declare underperformance.

WHAT TO EXAMINE
1. Inventory — identify every [X]. Report anything that could not
   be classified; never force it into a category.
2. Coverage gaps — identify [cohorts] served by nothing at all,
   with sizes. Look for these gaps deliberately.
3. Structure — [cadence / silence gaps / dead branches /
   stage progression].
4. [Domain-specific check].
5. [Domain-specific check].

OUTPUT
1. Headline — [single quantified finding], with the number.
2. [Table] — [columns].
3. Uncovered [cohorts], sized.
4. Closing statement — [required conclusion or finding].

RULES
- Every finding must cite a name and a number. If it cannot be
  evidenced, do not state it.
- Where [X] is well built, state this rather than manufacturing
  a finding.
- An empty finding is valid and valuable. Do not fill space.
- Use plain, factual, board-readable language. Avoid marketing
  language.

Agent Naming Configuration

The agent name and description appear on the agent card and in the agent picker. The name has a 50-character limit and should clearly communicate the business problem or analysis performed.

Useful names generally fall within 30–44 characters.

Naming ApproachExampleRationale
GenericCampaign Analysis AgentDescribes a broad category but does not communicate the specific analysis or output.
SpecificRepeat Purchase Journey Coverage AuditorIdentifies the business problem and indicates the type of analysis performed.

For the 300-character description, describe what the agent surfaces rather than the underlying processing.

Example:

Audits win-back journeys for cohorts entering no journey at all, sequences that stop before the reorder window, and dead branches.

Manage Custom Agents

TaskAction
Edit instructionsOpen the agent and click the Pencil icon next to Instructions in the right rail.
Change domains or capabilitiesClick the Pencil icon next to Tools. Domains can be added or removed, Deep Research or Brand Wiki can be enabled, and visibility can be changed after creation.
Share with the teamSet Visibility to Public. A private agent does not appear in the agent picker for other users on the same panel.
Clone a sample agentOpen a sample agent under Get started with these, then create a new agent using the same setup and modify it for the required business context.

👍### Important Points to Remember

  • Custom agents read campaigns, journeys, and segments only. No other data domains are available.
  • Deep Research must be enabled for PDF report generation.
  • An agent without custom instructions can still respond, but the response remains generic.
  • An empty result can be a valid finding. For agents designed to identify gaps, the absence of a matching result should be reported rather than treated as an error.
  • Agents are scoped to the panel where they were created and are not shared across panels.
  • Panel data refreshes on a scheduled cycle and is not real-time.
  • The Co-marketer is AI-powered and can make mistakes. Generated findings should be reviewed against the relevant business context before action is taken.

Troubleshooting

IssueResolution
The Agents section is missingThe Co-marketer is open in the side panel. Click the Expand icon to open the full-screen experience.
The agent returned no resultsFirst determine whether the absence is the intended finding. If not, check whether the selected domain is too narrow in Tools.
The output is genericThe Instructions field may be empty or insufficiently detailed. Define the role, data boundary, and required output structure.
No PDF option is availableDeep Research is not enabled. Edit Tools using the Pencil icon on the agent page.
Numbers appear stalePanel data refreshes on a scheduled cycle rather than in real time.
The agent reports information outside its configured scopeAdd an explicit data boundary to the instructions. For example: "[X] data is unavailable. Never infer [Y]." Save the updated instructions.
The agent is not available in the pickerCheck Visibility. A private agent does not appear for other users on the same panel.

Responsible AI And Transparency

Custom agents inherit the safeguards of the Unified Co-marketer.

Custom agents generate insights only from the configured campaign, journey, and segment data. Supporting metrics are presented with recommendations where applicable, and agent access remains isolated to the associated account.

Generated insights should be reviewed in the context of organisational goals and business requirements before strategic decisions are made.

For more details, refer to AI Security and Governance.


Did this page help you?