What Is Tracked?
Tracked is a system for organizing and monitoring the things that matter to your business. Create object types for different categories—like commitments, requests, or releases—then populate them as these items emerge from customer conversations, internal meetings, and other data sources.Business Objects
Track commitments, requests, problems, ideas, releases, use cases, objections, and more
Custom Properties
Add properties like owner, status, priority, account, initiative, or any custom field
Conversation Links
Connect objects to extracted signals showing where they were mentioned
Multiple Views
View objects in table or kanban layouts, filtered and sorted your way
What Can You Track?
Tracked is designed for business objects that emerge from conversations and need ongoing monitoring:Commitments & Promises
Things you’ve committed to customers or stakeholders:- “We promised Acme Corp we’d have SSO by Q2”
- “Told the enterprise team we’d prioritize bulk import”
- “Committed to fixing the sync issue by next week”
Requests & Feature Asks
What customers and users are asking for:- Feature requests from discovery calls
- Enhancement suggestions from support tickets
- Integration requests from sales conversations
Problems & Issues
Pain points and challenges surfaced in conversations:- Recurring customer complaints
- Workflow blockers mentioned in calls
- Technical issues affecting multiple accounts
Ideas & Opportunities
Concepts and possibilities worth tracking:- Product ideas from customer conversations
- Market opportunities identified in sales calls
- Process improvements suggested by team members
Releases & Launches
Things you’re shipping or have shipped:- Product releases and their status
- Feature launches with rollout tracking
- Updates communicated to customers
Use Cases & Objections
Patterns from sales and success conversations:- How customers are using (or want to use) your product
- Common objections heard in sales calls
- Competitive situations and outcomes
Core Concepts
Object Types
Object types define what category of things you want to track. Examples:- Commitments: Promises made to customers
- Requests: Feature and enhancement asks
- Problems: Issues and pain points
- Ideas: Opportunities and concepts
- Releases: Product launches and updates
- Use Cases: Customer scenarios and applications
- Objections: Sales concerns and blockers
Properties
Properties are the fields you add to track details about each object. Common properties include:| Property | Type | Example Use |
|---|---|---|
| Status | Select | Open, In Progress, Done, Won’t Do |
| Priority | Select | High, Medium, Low |
| Owner | User | Who’s responsible |
| Account | Text/Object | Which customer it’s for |
| Due Date | Date | When it needs to be done |
| Initiative | Select | Which initiative it relates to |
| Quarter | Select | Q1, Q2, Q3, Q4 |
| ARR Impact | Number | Revenue associated |
| Source | Select | Sales, Support, Product, Internal |
Objects
Objects are the individual items you create—each commitment, request, problem, etc. Every object:- Belongs to an object type
- Has values for defined properties
- Can link to signals from conversations where it was mentioned
- Appears in views based on its property values
Key Features
Extraction Links
Connect objects to your conversation intelligence:- Link signals: Associate extracted signals with relevant objects
- See context: View the exact moments in calls where objects were discussed
- AI suggestions: Get recommendations for relevant extractions
- Build evidence: Accumulate mentions across multiple conversations
Multiple Views
Visualize your tracked objects:- Table view: Spreadsheet-style with sortable, filterable columns
- Kanban view: Board organized by status or other select properties
- My Objects: Filter to see only items assigned to you
- Saved filters: Create and share common filter combinations
Import & Export
Move data in and out:- CSV import: Bulk import objects from spreadsheets
- Export data: Download objects with all properties
- Bulk operations: Update multiple objects at once
Getting Started
1
Create an Object Type
Go to Settings → Features → Tracked and click Create Object Type. Start with something common like “Commitments” or “Requests.”
2
Add Properties
Define properties like Status, Owner, Priority, and Account. Start simple—you can add more properties later.
3
Create Your First Objects
Navigate to Tracked in the sidebar and start adding objects as they surface from conversations.
4
Link to Conversations
Connect objects to relevant signals to maintain context and evidence.
5
Review Regularly
Use views to monitor open items, track progress, and ensure nothing falls through the cracks.
Common Object Types by Team
- Product
- Customer Success
- Sales
- Leadership
Requests
- Properties: Status, Priority, Requester Count, Account, Initiative, Effort
- Track: Feature requests, enhancements, integration asks
- Properties: Status, Severity, Affected Accounts, Owner, Root Cause
- Track: Customer pain points, workflow blockers, UX issues
- Properties: Status, Category, Potential Impact, Source
- Track: Product concepts, improvement opportunities, innovation ideas
Property Design Tips
Essential Properties
Most object types benefit from these core properties:- Status: Track lifecycle (Open → In Progress → Done)
- Owner: Who’s responsible for this object
- Priority: How important or urgent it is
- Source: Where it came from (Sales, Support, Product, etc.)
Context Properties
Add context to understand each object better:- Account/Customer: Which customer it relates to
- Initiative/Project: What larger effort it connects to
- Quarter/Timeline: When it’s relevant
- Notes: Free-form details and context
Measurement Properties
Track impact and outcomes:- ARR/Revenue: Financial impact
- Frequency/Count: How often it’s mentioned
- Effort/Size: Implementation complexity
- Outcome: What happened (Won, Lost, Shipped, etc.)
Integration with BuildBetter
From Signals to Objects
Tracked objects connect to your conversation intelligence:- Signals are extracted from calls and data
- Create objects for important items (commitments, requests, etc.)
- Link relevant signals to each object
- Build up evidence and context over time
- Track resolution and outcomes
With Knowledge Pages
Use Knowledge for process documentation, Tracked for the items themselves:- Knowledge: “How we handle customer commitments” (the process)
- Tracked: Individual commitments you’ve made (the items)
With Documents
Generate reports and summaries from tracked objects:- Create documents summarizing open requests by account
- Generate commitment reports for QBRs
- Build release notes from tracked releases
Tracked is available with the appropriate feature flag enabled. Contact your workspace admin to enable object tracking.