Sales daily and weekly report agent

[!NOTE] This guide separates content by role. Chapter 03 serves sales reps and managers. Chapter 04 serves system administrators.

01-Overview

1.1 Product positioning

• What did the sales rep complete during the period, and did the rep honor each commitment?
• Which accounts or opportunities are stalled, and what should the rep prioritize next?
• Is the team healthy, and which AEs or accounts are holding back results?
• Does the Pipeline show shallow growth, false progress, or commitment inflation?
• How do Markdown, HTML, and CRM logs support report delivery and retention?

1.2 Standard skills

1.3 Personal report capabilities

• “Generate my sales weekly report.”
• “Create my 2026-W26 personal weekly report in HTML.”
• “How did I perform against my monthly target? Which accounts should I prioritize next month?”
• “review this week’s accounts and opportunities, with emphasis on risks and next actions.”
• “Which follow-ups produced valid results today? What is tomorrow’s P0?”

1.4 Team report capabilities

• “Generate this week’s team report for Sales Team 1.”
• “review this month’s performance for the area team.”
• “Which AEs show abnormal performance this week? Which accounts need supervisor intervention?”
• “Is the team Pipeline healthy? Are there cross-AE risks?”
• “Convert this team monthly report from Excel into a polished HTML page.”

1.5 Core terms

1.6 Performance review process

1. Parse the user’s intent and determine the personal or team perspective.
2. Detect a daily, weekly, or monthly report and confirm the date range.
3. Confirm the personnel, team, area, or AE list.
4. Confirm object fields before reading CRM data in each batch.
5. Analyze targets, results, Pipeline, commitments, and risks.
6. Generate personal actions or supervisor management actions.
7. Display the full Markdown content in the conversation.
8. Generate an HTML page with the same file prefix by default.
9. Show a CRM log save preview.
10. Write the CRM log only after explicit confirmation.

1.7 Business value

• Reduce the time needed to write daily, weekly, and monthly reports.
• Move from activity lists to reviews of results, risks, and actions.
• Reconcile commitments automatically and keep plans aligned with actual work.
• Detect false progress and clarify priorities for the next period.

• Build a team performance dashboard quickly.
• View team averages and individual exceptions together.
• Detect competitor concentration, resource concentration, and inflated Pipeline.
• Produce specific management actions that require supervisor intervention.

• Standardize daily, weekly, and monthly reports.
• Retain standard operating procedures for personal and team performance reviews.
• Separate CRM facts, sales narratives, historical logs, and management judgments.
• Save periodic reports to CRM logs after users confirm them.

1.8 Roles and capability map

1.9 Current capability baseline

02-Quick start

2.1 Generate a personal weekly report

Completion conditions

[!IMPORTANT] - applicable role: You are an AE, account manager, or sales rep. - data permission: You can read your related CRM business data. - period definition: Weekly reports use ISO Monday through Sunday by default.

Steps

1. In the Sales Daily and Weekly Report Agent, enter “Generate my sales weekly report.”
2. To specify a period, add an ISO week or an explicit date range.
3. To specify output, request the concise, detailed, or HTML format.
4. Check the personnel and period detected by the Agent.
5. Check the coverage status for each data type.
6. View the weekly summary and key business signals.
7. Compare the prior commitment with the actual result.
8. View key accounts, opportunities, and risk alerts.
9. Check the P0, P1, and P2 actions.
10. Request changes when the content does not match the facts.
11. Reply “Confirm Save” only when the save preview is accurate.

Expected result

• The conversation displays the complete personal weekly report in Markdown.
• The Agent generates an HTML page with the same prefix by default.
• The weekly report includes commitment reconciliation, opportunity risks, and next week’s actions.
• The Agent does not write a CRM log without explicit confirmation.

2.2 Generate a team weekly report

Completion conditions

[!IMPORTANT] - applicable role: You are a sales supervisor, manager, area manager, or sales director. - scope information: Prepare a team, department, area, or AE list. - data permission: You can aggregate CRM data for team members and related records.

Steps

1. Include a clear team-management signal in the instruction.
2. Enter “Generate this week’s team report for Sales Team 1” or an equivalent request.
3. For an exact data range, provide an AE list or area name.
4. Check the team scope and data coverage description.
5. View team targets, closed business, and Pipeline status.
6. Check completion of last week’s management actions.
7. View AE performance, exceptions, and key opportunities.
8. Check competitor and resource concentration risks.
9. Confirm the owner and validation criteria for each management action.
10. Reply “Confirm Save” only when the save preview is accurate.

Expected result

• The report shows both team-wide status and individual exceptions.
• The team report does not concatenate personal reports.
• Each management action includes an owner, object, deadline, and validation criteria.
• The Agent does not write a CRM log without explicit confirmation.

03-User guide

3.1 Select a report type

Completion conditions

[!IMPORTANT] - data permission: confirm that you can read data for the target personnel or team. - scope information: A team report requires a team, area, or AE list. - Period information: Prepare a calendar day, ISO week, or calendar month date range.

Selection steps

1. To review your own work, use “I,” “personal,” or a specific sales rep name.
2. To review a team, specify a team, department, area, or multiple AEs.
3. To compare AEs or request supervisor guidance, state the team-management need.
4. Check the personnel or team scope returned by the Agent.

3.2 Select a reporting period

[!NOTE] Treat “daily and weekly report” as a weekly report, not a daily report.

3.3 Generate and interpret personal reports

3.3.1 Generate a personal daily report

[!IMPORTANT] - applicable role: You are an AE, account manager, or sales rep. - Date requirement: Specify today, yesterday, or a calendar date. - data permission: confirm that you can read your CRM data.

1. In the Sales Daily and Weekly Report Agent, enter “Generate my sales daily report for today.”
2. For another day, specify the date.
3. For a specific format, request concise, detailed, or HTML output.
4. Check the personnel and date detected by the Agent.
5. View the daily summary and execution signals.
6. Verify the day’s results, key follow-ups, and task status.
7. Check the day’s risks and tomorrow’s actions.
8. Ask the Agent to correct content that does not match the facts.

• Each daily activity produced a clear result.
• The daily plan and actual completion match.
• Tomorrow’s P0 identifies a specific account or opportunity.
• Each action has a target, deadline, and observable validation criteria.

3.3.2 Generate a personal weekly report

[!IMPORTANT] - applicable role: You are an AE, account manager, or sales rep. - period definition: Weekly reports use ISO Monday through Sunday. - historical data: Commitment reconciliation depends on the previous week’s CRM log.

1. In the Sales Daily and Weekly Report Agent, enter “Generate my sales weekly report.”
2. For a historical report, provide an ISO week or explicit date range.
3. For a specific format, request concise, detailed, or HTML output.
4. Check the personnel, period, and data coverage status.
5. View the weekly summary and key business signals.
6. Compare the prior commitment with the actual result.
7. Check factual progress for key accounts and opportunities.
8. View risk alerts and weekly review conclusions.
9. Check the P0, P1, and P2 actions for next week.
10. Ask the Agent to correct content that does not match the facts.

3.3.3 Generate a personal monthly report

[!IMPORTANT] - applicable role: You are an AE, account manager, or sales rep. - period definition: Monthly reports use a calendar month. - data requirement: Target, closed-business, payment collection, and opportunity data affect analysis completeness.

1. In the Sales Daily and Weekly Report Agent, enter “Generate my sales monthly report for this month.”
2. For a historical month, specify YYYY-MM.
3. Check the personnel and calendar month detected by the Agent.
4. View the monthly summary and target attainment.
5. Check closed business and Pipeline structure.
6. View the month’s key achievements and key account review.
7. Check major risks and loss reasons.
8. View monthly trends and the next-month strategy.
9. Check the data coverage description.
10. Ask the Agent to correct content that does not match the facts.

• Target and payment collection definitions follow enterprise rules.
• Pipeline coverage and the late-stage opportunity ratio are healthy.
• Account quality and loss reasons have factual support.
• The next-month strategy identifies specific accounts and opportunities.

3.3.4 Interpret commitment reconciliation and personal risks

1. Find the commitment reconciliation section in the report.
2. Check each completed, deferred, overdue, canceled, or pending-confirmation status.
3. Validate each conclusion against sales records, schedules, or opportunity facts.
4. Define a new action for each deferred or overdue item.
5. Keep “pending confirmation” when the Agent cannot determine a result.

[!NOTE] A meeting, communication record, or document send operation is not equal to sales progress. Valid progress requires a conclusion, budget, POC, or clear next action.

3.3.5 Apply personal action recommendations

1. Find the P0, P1, and P2 action list in the report.
2. Check P0 first and keep its quantity at three or fewer.
3. Keep P1 at five or fewer.
4. Keep P2 at three or fewer.
5. Confirm the account or opportunity for each action.
6. Confirm the key contact for each action.
7. Check that the action and target are specific.
8. Check that the deadline is explicit.
9. Check that the validation criteria are observable.
10. Ask the Agent to regenerate any vague action.

• object: The account or opportunity.
• contact: The key person to contact.
• Action: The specific task to perform.
• Target: The intended business result.
• deadline: A specific date or time range.
• Validation criteria: Observable facts that confirm effective completion.

3.4 Generate and interpret team reports

[!WARNING] AEs with data do not represent the complete team. Use the full team list as the coverage baseline and mark missing AEs explicitly.

3.4.1 Generate a team daily report

[!IMPORTANT] - applicable role: You are a sales supervisor, manager, area manager, or sales director. - scope requirement: Specify a team, department, area, or AE list. - data permission: confirm that you can read team members and related business data.

1. In the Sales Daily and Weekly Report Agent, enter “Generate today’s team report for Sales Team 1.”
2. For another day, specify the calendar date.
3. Check the team scope and date detected by the Agent.
4. Check the data coverage status for team members.
5. View the daily management summary and signals.
6. Verify the day’s key results.
7. Check AE exceptions and execution gaps.
8. View key account or opportunity changes.
9. Confirm the supervisor intervention items for today.
10. Check tomorrow’s team actions.

3.4.2 Generate a team weekly report

[!IMPORTANT] - applicable role: You are a sales supervisor, manager, area manager, or sales director. - period definition: Weekly reports use ISO Monday through Sunday. - historical data: Prior-action closure depends on the previous week’s team log.

1. In the Sales Daily and Weekly Report Agent, enter “Generate this week’s team report for Sales Team 1.”
2. For an exact scope, provide an area or AE list.
3. Check the team scope, ISO week, and data coverage status.
4. View the weekly business summary and key business signals.
5. Verify the week’s key results.
6. Check completion of last week’s management actions.
7. View AE performance, exceptions, and key opportunities.
8. Check the week’s playbook review.
9. View cross-AE and account-level risks.
10. Confirm next week’s team playbook and supervisor actions.

[!WARNING] A team weekly report must read the previous week’s team log. An older log cannot replace the previous week’s management actions.

3.4.3 Generate a team monthly report

[!IMPORTANT] - applicable role: You are a sales supervisor, manager, area manager, or sales director. - period definition: Monthly reports use a calendar month. - scope requirement: Specify a team, area, or AE list.

1. In the Sales Daily and Weekly Report Agent, enter “Generate this month’s team report for Sales Team 1.”
2. For a historical month, specify YYYY-MM.
3. Check the team scope and calendar month.
4. Check the data coverage status for each AE.
5. View the monthly business summary and target attainment.
6. Check closed business and Pipeline structure.
7. View AE performance tiers and trends.
8. Review key accounts and industries.
9. Check major risks and management issues.
10. Confirm next month’s resource allocation and management cadence.

• Target and payment collection attainment are healthy.
• Pipeline additions and consumption are balanced.
• High-risk accounts are not overconcentrated.
• Resource allocation matches key accounts and opportunities.

3.4.4 Analyze AE performance and cross-AE risks

1. View team targets and actual results.
2. Compare each AE’s Pipeline, closed business, and payment collection.
3. Check the risks and exceptions for each AE.
4. Separate short-term variation from a persistent issue.
5. Identify AEs who need supervisor intervention.

3.4.5 Apply team management actions

1. Find the P0, P1, and P2 management actions in the team report.
2. Check P0 actions that require immediate supervisor intervention first.
3. Set an Assigned Owner for every P0 and P1 action.
4. Identify the AE, account, or opportunity involved.
5. Check that each action is specific.
6. Check that each deadline is explicit.
7. Check that each validation criterion is observable.
8. Match each resource adjustment to the related business risk.
9. Ask the Agent to regenerate vague actions.
10. Review execution results in the next team report.

• owner: The person who performs or advances the action.
• object: The AE, account, or opportunity involved.
• Action: The specific supervisor measure.
• deadline: The explicit completion time.
• Validation criteria: Facts that confirm completion and effectiveness.

3.5 View Markdown and HTML reports

[!IMPORTANT] - You have generated a personal or team report. - The Agent has returned the Markdown content. - The request did not disable HTML output.

View the Markdown report

1. In the Agent conversation, view the complete Markdown content.
2. Check the role and period in the title.
3. Check the summary, results, risks, and actions.
4. Check the data coverage description.
5. Check the CRM save preview.

View the HTML page

1. Find the HTML file with the same prefix as the Markdown report.
2. View the page on the web.
3. Check the page on a mobile client.
4. For a team report, check the data range on each tab.
5. Confirm that HTML and Markdown show the same key conclusions.

[!NOTE] HTML is a report display format. It does not mean the report is saved successfully to CRM.

3.6 Confirm and save a CRM log

[!IMPORTANT] - You have generated a complete report. - The Agent has shown a Chinese-language save preview. - You have permission to write the CRM log.

1. Check the Record Type and date.
2. Check the Current Summary.
3. Check the Next Steps.
4. Check the lessons learned and reviewer.
5. Request changes before save when needed.
6. Send an explicit save instruction after the content is accurate.
7. View the save result returned by the Agent.

• “Confirm Save.”
• “Save to CRM.”
• “Write to the log object.”
• “Yes, save.”

• A daily report uses the same day’s date.
• A weekly report uses the ISO week’s Sunday.
• A monthly report uses the last day of the calendar month.

[!WARNING] The Agent cannot write the CRM log while confirmation, changes, questions, or team scope remain unresolved. HTML generation does not mean a successful CRM save.

04-Administrator configuration guide

4.1 Mount personal and team report skills

[!IMPORTANT] - You need Agent and Skill administration permission. - Confirm the applicable scope for personal and team reports. - Prepare personal and team test requests for routing validation.

1. In the Sales Daily and Weekly Report Agent’s Skill settings, add sfa-journal-personal-report.
2. In the same Agent, add sfa-journal-team-report.
3. Save the Agent-to-Skill relationship.
4. Test personal routing with “Generate my sales weekly report.”
5. Test team routing with “Generate this week’s team report for Sales Team 1.”
6. Confirm that each request reaches the corresponding Skill.

4.2 Configure intent routing

[!IMPORTANT] - The personal and team report Skills are configured. - You have defined personal and team business wording. - You have prepared test wording for boundary cases.

1. Configure personal-perspective and period keywords for the personal report.
2. Configure team, department, area, and management-role keywords for the team report.
3. Add multiple-AE and comparison signals to the team report.
4. Configure the personal report as the default without a team signal.
5. Configure “daily and weekly report” as a weekly report.
6. Save the routing rules.
7. Validate routing with personal and team test wording.

[!WARNING] “sales weekly report” must route to a personal weekly report without a team signal. “Daily and weekly report” must route to a weekly report.

4.3 Configure CRM data sources and field mappings

[!IMPORTANT] - confirm that each related CRM object is available in the tenant. - confirm each object API name and field definition. - Define the personnel filter for personal and team reports.

1. Configure the log object JournalObj.
2. Configure the sales records object ActiveRecordObj.
3. Configure the opportunity object NewOpportunityObj.
4. Configure order, payment collection, schedule, and fieldwork objects as needed.
5. Configure account, lead, contact, and personnel objects as needed.
6. Run a field description query for each object.
7. Use only confirmed fields.
8. Configure personnel or team filter fields.
9. Configure the time field, Confirmation Time range, and query limit.
10. Validate returned data by query batch.

[!WARNING] Do not guess an unconfirmed field. A failed query does not mean no data.

4.4 Configure query batches

• Query object.
• Time window.
• Personnel or team filter.
• Time field.
• Selected fields.
• Query limit.

1. Determine the personal or team data range.
2. Determine the daily, weekly, or monthly period.
3. Run batch A to confirm fields.
4. Run batch B to retrieve core facts.
5. Run batch C through batch E only when needed.
6. Record the data coverage status for each data type.

4.5 Configure data permission and CRM log write permission

[!IMPORTANT] - Define role boundaries for individual sales reps and sales managers. - configure personnel-to-team relationships. - confirm that the CRM log object is available.

1. Configure each sales rep’s visibility.
2. Cover accounts, opportunities, sales records, orders, payments, and logs.
3. Configure the supervisor’s team data range.
4. Cover team accounts, opportunities, and logs.
5. Configure CRM log write permission separately.
6. Validate the personal data range with a sales-rep account.
7. Validate the team data range with a management account.
8. Validate save restrictions with an account that lacks write access.

[!WARNING] The Agent cannot write a CRM log without explicit confirmation. It cannot claim save success when the user lacks write permission.

4.6 Configure period and metric definitions

[!IMPORTANT] - confirm whether the enterprise uses calendar weeks or custom sales weeks. - confirm definitions for targets, closed business, payment collection, and Pipeline. - confirm the sales stage range for late-stage opportunities.

Configure period definitions

1. Configure daily reports for a calendar day.
2. Configure weekly reports for ISO Monday through Sunday by default.
3. Configure custom start and end rules when the enterprise uses a sales week.
4. Configure monthly reports for a calendar month.
5. Use the same date range for the title, query, and save operation.
6. Configure log time: same day for daily, Sunday for weekly, and month-end for monthly reports.

Configure metric definitions

1. Confirm the numerator and denominator for target attainment.
2. Confirm the object and time field for closed business and payment collection.
3. Confirm the Pipeline amount and coverage-multiple definitions.
4. Define late-stage opportunities.
5. Configure extended dimensions such as product line, area, and industry.
6. Validate each calculation with real examples.

[!WARNING] Metrics with different date definitions can produce incomparable conclusions. Standardize them before publish.

4.7 Configure risk and action rules

[!IMPORTANT] - confirm the enterprise sales stage and Pipeline definitions. - confirm definitions for stalls, competitors, and key-contact risks. - Define responsibility boundaries for personal and supervisor actions.

Configure risk rules

1. Configure the opportunity-stall duration.
2. Configure risk escalation when a competitor reaches demo, POC, or quote.
3. Configure the Champion disengagement condition.
4. Configure the commitment-inflation condition.
5. Configure Pipeline concentration and inflation thresholds.
6. Configure the cross-AE risk aggregation condition.
7. Validate the results with real personal and team examples.

Configure action rules

1. Limit personal P0 actions to three.
2. Limit personal P1 actions to five.
3. Limit personal P2 actions to three.
4. Require each personal action to include object, contact, action, target, deadline, and validation criteria.
5. Require each team P0 and P1 action to include owner, object, action, deadline, and validation criteria.
6. Reject vague wording such as “Follow” as a complete recommendation.

4.8 Configure report output and HTML templates

[!IMPORTANT] - confirm the content structure for personal and team reports. - Prepare the required brand styles. - Define the applicable scope for concise and detailed output.

1. Display the complete Markdown content.
2. Configure an HTML page with the same file prefix.
3. Configure concise and detailed options.
4. Adjust brand colors and module order.
5. Configure team tabs for results, AE performance, and risks.
6. Adjust export styles.
7. Configure the personal file prefix as personal-report.
8. Configure the team file prefix as team-report.
9. Validate the HTML page on web and mobile client.

• Personal: personal-report-[period]-[date-or-range].md/html
• Team: team-report-[period]-[date-or-range].md/html

[!NOTE] HTML is a display format. A generated page does not mean the CRM log is saved successfully.

4.9 Test and publish a local custom Skill

[!IMPORTANT] - Prepare real personal weekly, team weekly, and monthly examples. - confirm data sources, fields, definitions, and permissions. - Retain the current validated version when a test does not pass.

1. Download the standard Skill locally.
2. Modify data sources, field mappings, or query definitions.
3. Modify period, risk, or action rules in rules.
4. Modify HTML template styles in assets.
5. Test real personal weekly, team weekly, and monthly examples.
6. Check data permission and data coverage status.
7. Check Markdown and HTML output quality.
8. Validate the CRM log save preview.
9. Validate that an unconfirmed request does not write a log.
10. Publish the custom Skill only after every check passes.

• Personal and team intent routing is correct.
• Daily, weekly, and monthly periods are correct.
• Queries do not use unconfirmed fields.
• Personal and team data range follows permission rules.
• Risk conclusions have factual support.
• Action recommendations follow quantity and field requirements.
• Save requires explicit confirmation.

[!WARNING] Do not publish a Skill after a failed test. Check data, rules, or permissions and continue using the current validated version.

05-Reference documents

5.1 CRM objects and query batches

Standard CRM objects

• Run a field description query before the first query for an object.
• Each log, sales record, and opportunity belongs to the core fact sources.
• Orders and payments supplement closed-business and payment collection metrics.
• Schedules and fieldwork supplement commitments, meetings, visits, and tasks.
• Accounts, leads, and contacts supplement business context.

Data query batches

5.2 KPI and risk thresholds

Personal report thresholds

Team report thresholds

Pipeline and competitor risks

[!NOTE] These numerical value thresholds are standard defaults. Each enterprise can adjust them to its own metric definitions.

5.3 Report structure, routing, and save fields

Six report output structures

Routing rules

Period rules

CRM save preview fields

5.4 Data coverage status and Usage limitations

Data coverage status

[!WARNING] A CRM result marked Is Null never equals no business activity. Keep no data, permission denial, untriggered queries, and failed queries separate.

Role limitations

• Personal reports cannot include team rankings, AE comparisons, or supervisor resource coordination.
• Team reports cannot concatenate personal reports.
• Team averages cannot hide individual exceptions.
• AEs with data do not represent the complete team list.

Period and fact limitations

• Weekly reports must use an ISO calendar week, not a rolling seven-day period.
• Do not guess unconfirmed fields.
• A team weekly report must read the previous week’s team log exactly.
• An older log cannot replace the previous week’s management actions.

Save limitations

• Do not write a CRM log without explicit confirmation.
• Do not claim saved successfully without write permission.
• HTML generation does not mean a completed CRM save operation.