Customize an iDialogue Agent in Agent Studio
Use iDialogue AI → Agent Studio to review and customize a current iDialogue v2 agent. This guide does not apply to legacy v1 Rooms or private-beta XP Experiences.
If setup is incomplete, follow Getting Started. To add a Gallery agent, first follow Install an Agent from Agent Gallery.
Open the intended agent
- Open iDialogue AI.
- Open Agent Studio.
- Search for the agent by name.
- Open it and confirm that its name and purpose match the agent you intend to change.
- Review the current Stage, settings, instructions, skills, and Quick Starts before editing.
To create an original agent, select Create New Agent and complete the browser prompts. A new agent starts in Draft. Creation does not publish it or approve it for production use.
Know the Agent Studio surfaces
| Surface | Use it to |
|---|---|
| Agent Builder | Work with the guided builder for the selected agent. |
| Settings | Review and edit the main agent configuration. |
| Instructions | Define the agent's purpose, rules, and response behavior. |
| Skills | Select capabilities and set where each skill is available. |
| Agent Ops | Review dialogues, feedback, and memory records for the selected agent. |
| Releases | Review package information and separately controlled package actions. |
| History | Review recent changes and field history. |
| Quick Starts panel | Maintain suggested prompts that users can select. |
Controls can vary by package version, permissions, and agent configuration. If a documented control is absent, stop and report the gap. Do not substitute a different control.
Review settings by task
Review the agent's identity, purpose, audience, Salesforce record context, and Data Context Definition. Then review the separate Chat and Background settings, model limits, working-status messages, and AI Assistant console display.
Use these references for detailed contracts instead of inferring behavior from labels:
- System and Local Agents
- Data Context Definition
- Skills Catalog
- Run Agent Action for Salesforce Flow
- AI & Agent Governance
Keep the two Quick Start concepts separate
Installation Quick Start is the guided connection process in iDialogue Admin. Agent Quick Starts are suggested prompts for one agent. Editing an Agent Quick Start does not reconnect Salesforce or install a package.
Configure instructions and skills deliberately
Write instructions that state the agent's purpose, allowed work, required review, and expected response. Add only the skills required for that purpose. Select each skill's Run Context in Agent Studio and verify it against the intended Chat or Background workflow. Skill availability does not expand Salesforce permissions or remove an approval step.
For a background file workflow, use the canonical Run Agent file-processing guide.
Change one area and verify it
- Record the current value and expected result.
- Change one focused area in Settings, Instructions, Skills, or Quick Starts.
- Save in Salesforce and read the confirmation or error.
- Refresh or reopen the agent.
- Confirm that the saved value and intended Run Context persisted.
- Test a low-risk example in the browser and review the available runtime tooling and result.
If a save fails, keep the existing configuration. Capture the displayed error and ask an administrator to check the package version, permissions, record access, and required fields.
Treat Stage and console display separately
Stage is the agent lifecycle status. Display In AI Assistant Console is a separate setting. Changing one does not prove that the other is configured or that the agent appears in the intended record context.
Get separate confirmation before changing Stage or using Releases. After a Stage change, open the intended AI Assistant console and verify the agent there. Package creation, package install links, and add-on installation are not part of a normal settings save.
Finish with a human review
Confirm that:
- the correct agent is open;
- settings and instructions persist after refresh;
- skills use the intended Run Context and required permissions;
- the Data Context Definition exposes only the required data;
- Stage and AI Assistant console display were checked separately; and
- release, package, and add-on actions remain unperformed unless separately approved.
Use this guide with a coding agent
A coding agent can explain these browser steps and inspect authorized metadata or records when requested. For an approved record-level configuration workflow, use Manage iDialogue Agent Records. This browser guide is not evidence that a save, activation, release, or other connected-org change occurred; verify the resulting state in Salesforce.