Configuring Docket's Multi-Agent Platform

Last updated: July 22, 2026

Use multiple Marketing Agents when your website has distinct visitor journeys that need different instructions, knowledge, CTAs, routing, or reporting. This guide shows how to plan the portfolio, configure each agent, test it, and compare results.

Before you begin, sign in to Docket and confirm that you can open Marketing Agent Configuration and Marketing Agent Dashboard.

1. Plan the Agent Portfolio

Give each agent one clear job. Separate agents are useful when the audience, page, source content, language, or desired next step changes.

Agent decision

Example

Visitor journey

Homepage education, pricing qualification, or event follow-up

Primary outcome

Answer a question, capture a lead, book a meeting, or hand off

Knowledge scope

Product overview, pricing content, or campaign-specific resources

Placement

A specific page, campaign, or standalone experience

Success measure

Interactions, leads acquired, meetings booked, or CTA engagement

Avoid creating two agents with the same job. If the intended audience, answer set, and next step are the same, use one agent and refine its configuration.

2. Create or Open an Agent

  1. Open Marketing Agent Configuration.

  2. Use Create Agent for a new visitor journey, or select an existing card from Your Agents.

  3. Give the agent a name that identifies its job, such as Pricing Guide or Website Concierge.

  4. Confirm you opened the intended agent before changing its configuration.

Agent cards keep each agent's status and recent metrics separate. Use Search agents when the list becomes difficult to scan.

3. Configure Each Agent

Complete the configuration tabs for the agent you opened:

Tab

Configure

Agent

Instructions, persona, greeting, interaction mode, CTAs, handoff, and Work Hours

Knowledge

The files, web content, slides, and videos this agent can use

Analysis and Actions

Post-call fields, actions, alerts, and supported CRM or marketing sync

Widget

Appearance, behavior, page targeting, and domain access

Deploy

Website installation, standalone-page access, and deployment validation

clipboard.png
  1. Confirm the agent identity and active state before changing settings.

  2. Configure the agent across the available tabs.

  3. Use Preview before launch.

Keep the configuration aligned with the agent's job. For example, a pricing agent should use approved pricing content and a pricing-specific CTA rather than every source and action available in the workspace.

4. Preview and Launch Deliberately

  1. Select Preview from the agent detail page.

  2. Ask expected questions and confirm the answers use approved information.

  3. Test the intended CTA, meeting-booking path, and handoff condition.

  4. Test an unsupported question and confirm the agent follows your fallback behavior.

  5. Review Widget behavior and Deploy access settings.

  6. Launch one changed agent at a time when possible, so you can attribute results and diagnose problems clearly.

Preview again after changing instructions, knowledge, actions, widget behavior, or deployment settings.

5. Compare Performance and Iterate

Open Marketing Agent Dashboard and use the agent selector to review one agent or the full portfolio. Keep the date range consistent when comparing agents.

clipboard.png
  1. Set the reporting scope with search, date-range, view, export, and filter controls.

  2. Compare the core performance metrics for the selected scope.

  3. Use the engaged-visitors table for conversation-level review.

Interpret results in the context of each agent's job. A product-education agent may optimize for useful interactions, while a pricing agent may optimize for qualified leads or meetings booked. Compare the outcome the agent was designed to produce, not a single metric across every use case.

Verify the Multi-Agent Setup

For every agent in the portfolio, confirm that:

  1. Its name and purpose are distinct from the other agents.

  2. Its Agent instructions and selected Knowledge match that purpose.

  3. Preview completes the expected visitor journey without using unrelated content.

  4. The intended CTA, booking flow, or handoff appears under the correct conditions.

  5. Widget and Deploy settings match the intended page or standalone experience.

  6. Marketing Agent Dashboard can isolate the agent's activity with the agent selector.

The portfolio is ready when each visitor journey can be tested independently and its outcome can be reviewed independently in the dashboard.

Troubleshooting

Issue

What to check

Two agents give conflicting answers

Narrow their instructions and selected knowledge so each agent has a clear audience and answer scope.

You edited the wrong agent

Return to Your Agents, confirm the agent name on the card, and reopen the intended agent before making changes.

A new agent cannot be created

Confirm you are in the correct workspace and have permission to create agents.

Preview behaves differently between agents

Compare their Agent, Knowledge, CTA, handoff, and Work Hours settings; those settings are scoped per agent.

The wrong agent appears on a page

Review the agent's Widget page-targeting rules, allowed domain, and deployment snippet or container.

Dashboard results are difficult to compare

Select the same date range and filter by one agent at a time before comparing the outcome tied to each agent's job.

Related Articles