Rep Cockpit: Tasks, Meetings, and Deals
The Rep Cockpit is where reps work in HockeyStack. It puts three things in one place: what's in the pipeline (Deals), what to do next (Tasks), and what's on the calendar (Meetings).
This isn't a standard CRM view. The cockpit is powered by HockeyStack’s unified data foundation (Atlas) and the Machine Learning-based reasoning layer that figures out what actually wins deals (Blueprints).
So every task, meeting brief, and deal action is grounded in real engagement data and patterns that have actually converted, not generic reminders or static templates.
Overview
When a rep opens the cockpit, they see three views:
Tasks: A prioritized queue of actions for the day, created by agents based on first-party data and winning sales pattern.
Meetings: Upcoming meetings pulled from the CRM, with one-click meeting prep.
Deals: Open pipeline with deal-level journey, context, and agent-powered insights.
All three views are connected to the same underlying data model (companies, people, deals, events, and activities), so context is consistent everywhere.
Tasks
What it is
A date-scoped queue of tasks assigned to the rep. Each task is tied to a specific contact, has a type (call, email, or LinkedIn), an action label, a reason explaining why the task exists, a due date, and a status.
How it works
Pick a date: today, yesterday, tomorrow, or a specific day. Tasks for that day show up in a queue, ordered by priority.
Click any task to open the Task Drawer. This shows full context: the contact's name, title, email, and account, the reason the task was created, and any supporting detail the agent included (talking points for a call, suggested email copy, a LinkedIn message draft).
Mark a task done or dismiss it with an optional reason. That feedback gets stored and used to improve task quality over time.
What makes it different
Tasks are not created manually or by static rules. They are created by HockeyStack Agents, continuously.
Agents use pattern-based recommendations to decide who gets a task and what the action should be. A task might say "Follow up: visited pricing page 3 times, opened last email 4 times" or "call champion - deal stuck in legal for 3 weeks." The reason is specific because the agent has the entire context of the deal.
Person-level details are added automatically. When tasks load, each contact is enriched with name, title, email, account name, and domain from the data layer. No separate CRM lookup required.
The end result is a task queue that reflects discovered process and real engagement, not a generic to-do list.
Meetings
What it is
A calendar view of meetings for the rep (or a selected owner), filterable by date range: today, this week, this month, this quarter, or next week. Each meeting shows the subject, time, duration, owner, attendees, and related records (accounts, opportunities, contacts).
How it works
Choose a date range and optionally filter by owner. For any upcoming meeting, click Prep with AI.
This kicks off a Meeting Prep agent, a workflow that pulls company context, deal status, contact intelligence, and previous interactions (emails, calls, prior meetings) from the data layer. It returns a brief, typically around 800 words, organized into sections like Overview, Deal Status, People in the Room, and Watch Outs.
The brief generates in the background. When it's ready, it shows up in a Meeting Prep modal. You can re-run it if the data changes before the meeting.
What makes it different
Meetings are sourced from the CRM and normalized so the cockpit works the same regardless of integration.
Meeting prep is not a fixed template. It's an agent whose contract defines what to gather and how to structure the output. The agent traverses the same unified data model that powers tasks and deal actions (company, deal, contacts, events, activities), so the brief reflects the full timeline of what actually happened, not scattered CRM fields.
Because it's agent-driven, the prep format and depth can be customized by editing the agent's contract. The cockpit is one surface that calls the workflow. The same Meeting Prep agent can be triggered from other entry points as well.
Deals
What it is
A list of open deals owned by the rep (or a selected owner), with deal name, amount, stage, account, close date, and owner. Each row links to a deal record with a Journey (timeline of events for that deal).
How it works
Scan or filter the pipeline. Click a deal to open the deal record and see the full journey.
What makes it different
The deal record is built around a timeline, not just CRM fields. It uses the same unified data model as tasks and meetings (deals, contacts, events, and activities), so everything is grounded in real engagement.
Deals are sourced from CRM, so the cockpit stays consistent regardless of CRM-specific field naming.
Summary
Tasks
Date-scoped task queue
Agents + first-party data + Blueprint signals
Tasks are created by agents grounded in real engagement and your winning patterns. Feedback (done/dismiss) closes the loop.
Meetings
Calendar meetings by range
CRM (Salesforce / HubSpot) + Meeting Prep agent
"Prep with AI" runs an agent on first-party data. The brief is decision-oriented, not a static template.
Deals
Open pipeline
CRM (Salesforce) + deal-action agents
Deal record built around a timeline view. Same unified data model as tasks and meetings.
Last updated