Account briefing agent user and configuration guide

Overview

Applicable roles and business value

Value for AEs

• Quickly understand meeting goals, key stakeholders, and risks before a visit.
• Build a complete account view automatically from multiple CRM objects.
• Use the Account 360 profile to understand the decision chain, pain points, and competitors.
• Spend less time repeatedly preparing materials before an executive visit.
• Preserve relationships, commitments, and history during an account handover.

Value for sales managers

• Quickly determine whether an account requires executive involvement.
• Review account preparation quality with a standard template.
• Reduce account churn risk with a handover briefing.
• Give executives a clear role, boundary, and follow-up plan for each visit.

Value for the organization

• Preserve long-term account memory.
• Turn personal experience into an organization asset.
• Standardize account insights, pre-meeting preparation, and handover process.
• Surface budget, competitor, delivery, and relationship risks early.
• Support the account details page, stored briefings, and manual refresh.

Scenario selection

Skill list

Basic workflow

1. Identify the account.
2. Retrieve CRM data for the selected business scenario.
3. Retrieve sourced account memory.
4. Separate facts, inferences, and unknown items.
5. Present the conclusion first, followed by risks and actions.

[!NOTE] Insufficient permission does not mean no data. The briefing preserves the actual data coverage status.

Recent updates and maintenance

1. When you update scenario capabilities, also update the steps and output structure.
2. When you update CRM fields, also update data sources and coverage status.
3. When you update Agent routing, revalidate the quick-start workflow.
4. When you update a template, verify all three briefing modes.

Quick start

Generate a briefing as a business user

[!IMPORTANT] Confirm that you have Read Only access to the intended account and its associated records.

1. In Agent conversation, enter an account name, Account No., or ID.
2. Describe the current business scenario.
3. Add meeting, opportunity, or handover context.
4. Select the required briefing mode.
5. View the conclusion summary and data coverage status.
6. Follow the risks and recommended actions to move account tasks forward.

Complete the minimum configuration as an admin

[!IMPORTANT] Confirm that you have Agent configuration permission.

1. In Agent configuration, create an Account Briefing Agent.
2. Mount all four skills in Skill mounting.
3. Configure scenario trigger phrases in Intent routing.
4. Assign read-only access for account-related objects to business roles.
5. Validate fields for accounts, opportunities, contacts, and sales records.
6. Use a test account to validate all four routing paths.

Expected results

• The request matches the correct briefing scenario.
• The briefing displays the conclusion and data coverage status first.
• Insufficient permission is not labeled as no data.

Account briefing scenarios

Standard Account 360 profile

Capabilities

Typical triggers

• Help me understand this account.
• Generate an Account 360.
• Generate an account profile, complete account view, or account overview.
• Generate an HTML account briefing or a web page account briefing.

Generation steps

1. In Agent conversation, enter an account ID, Account No., or name.
2. Ask for a “standard Account 360” or an “account profile.”
3. Specify full mode when you need the complete history.
4. Review the conclusion summary and information completeness.
5. View the account profile, relationships, opportunities, competitors, and risks.

Processing SOP

Output structure

Expected results

• The output separates facts, inferences, and unknown items.
• Each data category retains its actual retrieval status.
• full mode adds cooperation and financial history.

Information completeness

Pre-visit account briefing

Capabilities

Typical triggers

• Generate a pre-visit briefing.
• I am about to visit an account. Help me prepare.
• How should I approach today’s meeting?
• What is the current visit readiness score?
• What is the largest information gap?

Generation steps

1. In Agent conversation, enter an account name or ID.
2. Describe the meeting purpose and attendees.
3. Add the current opportunity stage.
4. Select lite, normal, or full mode.
5. Review the pre-meeting conclusion, risks, and primary goal.
6. Bring the P0 actions and key questions into the meeting.

Processing SOP

Output structure

Expected results

• The first screen displays the pre-meeting conclusion and primary goal.
• Each risk has a corresponding on-site response.
• Each action includes an object, goal, and validation criteria.

[!NOTE] A pre-visit briefing does not replace a complete business diagnosis. Switch to the relevant specialized skill for in-depth analysis.

Executive visit briefing

Capabilities

Typical triggers

• Write an executive visit briefing.
• I want a VP, director, or business leader to attend an account meeting.
• This opportunity requires executive escalation.
• Help me prepare an executive briefing.

Generation steps

1. In Agent conversation, enter an account name or ID.
2. Identify the requestor and the proposed executive attendee.
3. Add the customer executive, time, format, and current blocker.
4. Select the concise version, detailed version, or full mode.
5. Review executive involvement points and items that must not be promised.
6. Assign an owner to each post-meeting goal.

Processing SOP

Output structure

Concise and detailed versions

[!WARNING] An attending executive does not replace the AE’s basic follow-up. The executive must not promise an unconfirmed price or delivery scope.

Suitable scenarios

• A high-value strategic opportunity.
• Customer executives attend the meeting.
• Budget or approval blocks progress.
• A competitor is deeply involved.
• A renewal, expansion, or risk-recovery window exists.

Unsuitable scenarios

• A routine first visit before account needs are clear.
• The AE cannot explain what the executive should resolve.
• Key stakeholders, budget, competitors, and project value are all unclear.
• The only goal is to use an executive’s name to urge a customer response.
• The customer needs only product, quote, or implementation details.

Team account handover briefing

Capabilities

Typical triggers

• Hand over this account to a colleague.
• Generate an account handover briefing.
• What should I know before I take over this account?
• Organize account history when an AE leaves or changes roles.

Generation steps

1. In Agent conversation, enter an account ID, Account No., or name.
2. Describe the handover reason, new owner, and handover time.
3. Select normal or full mode.
4. Review the new owner summary and handover background.
5. Review key stakeholders, commitments, risks, and competitor history.
6. Schedule first-week actions based on the handover recommendations.

Processing SOP

Output structure

Expected results

• Facts and recommendations are presented separately.
• Each commitment includes a status and handover action.
• full mode adds cooperation and financial history.

Admin configuration and data preparation

General account identification SOP

1. First, query the CRM account _id with an exact match.
2. If the user provides an Account No., query it with an exact match.
3. Without an ID or Account No., query AccountObj.name LIKE <keyword>.
4. If an abbreviation returns no match, use query-by-name for name normalization.
5. If the query returns multiple candidates, ask the user to select the intended account.
6. If the name returns no match but the ID matches, use the ID result.
7. If nothing matches, state only that the current criteria returned no account.

[!IMPORTANT] Do not exclude account candidates yourself. Do not claim that the account does not exist in CRM.

General data query SOP

1. Confirm the primary account record and <account-id>.
2. Retrieve opportunities, contacts, and communication records.
3. Run baseline queries in normal mode.
4. Retrieve competitor details when competitor signals exist.
5. In full mode, retrieve contracts, sales orders, and payment collection.
6. Record the data coverage status for each object.
7. When permission is insufficient, do not mark the result as no data.
8. Do not duplicate a query for an object with an unrecoverable error.

Agent mounting and intent routing

1. Open the Account Briefing Agent in Agent configuration.
2. Mount all four skills in Skill mounting.
3. Configure trigger phrases in Intent routing.
4. Use all four request types to validate routing results.

Mounting list

CRM data sources and field validation

1. Confirm that each object exists in the object description API.
2. Confirm each API name and field definition.
3. Confirm that the account ID can associate core objects.
4. Confirm that time-related fields, such as Confirmation Time, support scenario filters.
5. Confirm that the user has object and field permissions.
6. Use a test account to validate the returned data.

[!NOTE] Account health, CSM warnings, and churn reasons may come from custom data. Retrieve these fields only after schema validation is completed.

Memory and briefing modes

1. Enable account memory in Account Briefing Agent configuration.
2. Define readable key events, relationship changes, and commitment status.
3. Configure allowed briefing modes for each scenario.
4. Keep the memory access area consistent with user permissions.
5. Use a test account to verify the source of historical events.

Output and HTML templates

1. Enable Markdown content in Output configuration.
2. Select the corresponding template for each scenario.
3. Keep the data coverage summary.
4. Check readability on the desktop and mobile client.
5. Confirm that Markdown and HTML use consistent facts.

General reference documents

Role tags

Relationship score

Visit readiness

Data coverage status

Permissions, limitations, and boundaries

• Retrieve only data that the current user can access.
• Industry benchmarks and competitor references cannot replace account evidence.
• Label inferred content as an inference or pending validation.
• By default, the briefing does not write to CRM automatically.
• Writing to CRM requires separate authorization and user confirmation.
• After an unrecoverable error occurs for an object, do not repeat the query in the same run.

FAQ