How Sales Rep Agent works ​

This page explains how Sales Rep Agent processes completed calls, gathers account research, applies CRM changes, evaluates alert rules, and organizes its project folders.

How the call completion workflow works ​

When a call ends, Sales Rep Agent retrieves the recording and transcript from the application set in the CallRecording.Application project property. Calls shorter than the Minimum.Call.Duration threshold are skipped.

It then summarizes the transcript against the fields in the Agentic Selling Methodology Fields | Definition data table. Each row specifies a Salesforce field, its associated object, and the criteria to assess how thoroughly the transcript addresses that field. The same workflow supports a MEDDPICC deployment and a value-selling deployment without changes to the skills.

Sales Rep Agent presents a before-and-after comparison of the proposed field updates for the rep to review, then updates the Salesforce opportunity once the rep approves the changes.

It then creates the following records based on the enabled project properties:

Project propertyWhen enabled, Sales Rep Agent creates
PostCall.Create.NoteA note on the opportunity.
PostCall.Create.TasksA follow-up task.
PostCall.Send.EmailA follow-up email, sent after the rep approves the draft.

How account research works ​

Sales Rep Agent reads your project properties to determine which applications your organization has configured, then routes each part of the research to the matching connected application. You don't specify which systems to check or in what order.

Each configured system contributes a different part of the account picture:

SystemContribution
CRMAccount summary, related contacts, contracts, and cases.
IT service management (ITSM) applicationOpen and high-priority issues tied to the account, narrowed by the filters in the JiraServiceDesk.filters project property.
Document repositoryRelated internal documentation and notes.
Customer support platformSupport tickets matching the company name, narrowed by your configured filters.
Enrichment platformExternal company details such as industry, size, and key personnel.
Call recording applicationSummaries of recent calls with the account.
Calendar applicationUpcoming and past meetings associated with the account.
Knowledge baseArticles relevant to the account or its industry.
Web searchRecent news mentions.

Sales Rep Agent merges these results into one summary.

Proactive pre-meeting research ​

Sales Rep Agent can prepare account research before customer meetings without being asked. It checks each covered rep's Google Calendar and, for each meeting with an external attendee, identifies the customer's company and prepares account research for that rep.

  • Schedule: Set by the FetchEvents.Interval project property.
  • Covered reps: Reps in the Agentic SalesExecutives data table with is_active set to TRUE.
  • External attendee: An attendee whose email domain differs from the Domain project property.

The following limits apply to proactive research:

  • Only Google Calendar is supported.
  • Only meetings with Zoom conferencing are included.
  • Meetings with no external attendee are ignored.

How CRM self-service operations work ​

Sales Rep Agent first searches the CRM for the record you referred to, which can be an account, contact, lead, opportunity, or task. It asks which record you meant instead of guessing when a request matches more than one, such as two opportunities with similar names.

Sales Rep Agent shows you the exact change it plans to make and waits for your confirmation before it creates or changes anything. You can correct a wrong record or a wrong value before it reaches the CRM. It applies the change and returns a direct link to the record after you confirm.

Sales Rep Agent acts with your own CRM permissions. It can search, read, summarize, create, and update records. It has no skills that delete, archive, cancel, merge, or unassign anything.

How CRM alerts work ​

Three independent processes generate alerts, and none of them requires a prompt from a user:

  • Scheduled checks: On the cron schedule set in the CRM.Health.Time.Interval project property, Sales Rep Agent reviews your opportunities and leads against the alert rules configured by your administrator. Each alert type has its own trigger recipe, and the agent sends an alert for every record that meets a rule.
  • Real-time stage-change checks: An opportunity's stage change in Salesforce triggers an immediate check of fields required at the new stage, instead of waiting for the next scheduled check.
  • Email monitoring: Sales Rep Agent watches incoming email and links messages related to an opportunity to the right record.

Supported alert types ​

Administrators enable each alert type and set its threshold in the Agentic Opportunity | Alert Configurations data table. Enter the alert type exactly as shown below.

Alert typeApplies toWhen it fires
IncomingEmailOpportunityAn email related to the opportunity has arrived.
DealStuckOpportunityThe opportunity has stayed in its current stage longer than the configured number of days.
MissingFieldsOpportunityFields required for the opportunity's current stage are empty. Checked on a schedule and also as soon as the stage changes.
OverDueCloseDateOpportunityThe opportunity's close date has passed and the opportunity is still open.
RenewalOpportunityCloseDateRenewal opportunityThe renewal opportunity's close date is within the configured number of days.
InactiveLeadLeadThe lead has had no activity for longer than the configured number of days.

How stage change checks work ​

The TRIGGER | [Salesforce] Start Genie Process for Opportunity Stage Change recipe watches Salesforce for updated opportunities and acts only when the update is a stage change. It then:

  • Looks up the active MissingFields rules for the opportunity's new stage in the Agentic Opportunity | Alert Configurations table.
  • Checks each required field in those rules on the opportunity.
  • For each empty field, collects the opportunity, account and owner details, and sends a MissingFields alert to the right people.
  • Records the alert, so the cooldown and escalation rules below apply to it.

If the recipe hits an error it can't recover from, it notifies the configured administrator with the error details.

Delivery, escalation, and cooldown ​

Alerts arrive through Sales Rep Agent's chat interface. If an alert isn't addressed within the rule's EscalationThreshold, Sales Rep Agent escalates it to the EscalationRecipients.

Two settings limit how often alerts repeat:

  • NotifyOnFirstInstance: Controls whether Sales Rep Agent notifies on a record's first appearance against a rule.
  • SnoozeDays: Sets the number of days before the same rule can notify again for the same record.

How knowledge retrieval works ​

Sales Rep Agent answers questions from the knowledge bases added to it. Knowledge ingestion syncs content from each source system at the frequency set in the Agentic Data Ingestion | Scheduler data table.

Knowledge gap logging ​

Sales Rep Agent records any question it can't answer in the Agentic KB Gap User Conversations data table. Each row holds the conversation ID, the user, the question they asked, the response it gave, a category, and a Not in KB flag. Sales Rep Agent sets Not in KB to TRUE when it can't resolve the request, including when no knowledge base article matches, a skill fails after a retry, or the request stays ambiguous after a clarifying question.

Sales Rep Agent sends the admins listed in the KBGap.digest.admins project property a weekly digest of the questions it couldn't answer in the previous seven days. To close a gap, add or update the content in the source system, run ingestion again, then ask the same question to confirm Sales Rep Agent now answers it.

Folder structure ​

The Sales Rep Agent project is organized into the following top-level folders:

  • Config: Connections and metadata required to run Sales Rep Agent.
  • Core: Foundational skills maintained by Workato. You can't modify or clone these skills.
  • Extensions: Additional app skills and functions maintained by Workato and updated during release cycles. You can use these as-is or as a reference when you build custom integrations.
  • Custom Extensions: Custom assets that you maintain. Clone Extension assets into this folder before you modify them. Assets in this folder remain intact across upgrades.
  • Runtime Data: Data tables that store the data Sales Rep Agent generates during runtime.
View folder structure
text
Agentic | Sales Rep Agent
├── Config
│   ├── Metadata
│   └── Connections
├── Core
│   ├── Apps
│   │   ├── Confluence
│   │   ├── Freshdesk
│   │   ├── Gmail
│   │   ├── Gong
│   │   ├── Google Calendar
│   │   ├── Jira Service Desk
│   │   ├── Salesforce
│   │   ├── Zoom
│   │   └── ZoomInfo
│   ├── Functions
│   └── Skills
├── Extensions
│   ├── Apps
│   │   ├── Freshdesk
│   │   ├── Google Calendar
│   │   ├── Jira Service Desk
│   │   └── Salesforce
│   ├── Functions
│   ├── Knowledge Ingestion
│   │   ├── Confluence
│   │   ├── Freshdesk
│   │   ├── Gong
│   │   ├── Google Drive
│   │   ├── Jira Service Desk
│   │   ├── Salesforce
│   │   ├── Salesforce Service Cloud
│   │   ├── Sharepoint
│   │   └── Slack
│   └── Skills
├── Custom Extensions
└── Runtime Data

CORE AND EXTENSIONS ARE MANAGED BY WORKATO

Don't modify the skills, functions, or data table schemas in the Core and Extensions folders. Make all customizations in Custom Extensions.

Working with Extensions and Custom Extensions ​

You can activate Extension skills and add them to Sales Rep Agent as-is. You can also clone them into Custom Extensions to customize them or build support for apps that aren't available in the Extensions folder.

Customizations in Custom Extensions are isolated from platform updates and remain intact across upgrades. You can't clone or modify core skills.

Last updated: