Outcome
You can explain every Today queue, preserve its scope when drilling in, and distinguish empty data from a loading failure.
Navigation path
CRM > Today
Access
Active CREBuilder subscription with CRM entitlement
On this page
Before you start
Data, sources, and access to prepare
- At least one permitted CRM record for a meaningful populated view
Set the correct operating context
- 1
Choose scope
CRM > Today > page controls
Select Mine or Whole team when your role offers both.
Expected result: Every queue and trend reloads for the selected role scope.
If this does not happen: If Whole team is absent, your role is own-scoped. Ask an authorized colleague for a company-wide review instead of changing the URL.
- 2
Choose the Deal pipeline
CRM > Today > Deal pipeline selector
When more than one Deal pipeline exists, choose Property or Business Sales.
Expected result: Deal queues and deal totals follow that pipeline; task and lead queues remain cross-pipeline.
If this does not happen: If expected deals disappear, return to this selector before clearing destination filters.
Understand every queue
| Queue | Included work | Best first action |
|---|---|---|
| Overdue tasks | Incomplete tasks before the current time | Complete, reschedule, or clarify ownership. |
| Tasks today | Incomplete future tasks before local midnight | Work them in priority order. |
| Stale deals | Open deals whose activity has aged past the current threshold | Open the deal and record a real update or next action. |
| Missing next action | Open deals without a clear outstanding task | Create a dated task tied to the responsible person or deal workflow. |
| New leads | First qualifying lead facts for canonical contacts | Review source context and assign a follow-up. |
| Unread inquiries | Inquiry activity not yet marked read | Read, qualify, and respond before bulk cleanup. |
| Expiring grants | Access grants nearing expiry | Review whether access should continue or end. |
Queue drill-through preserves intent
Today links carry the relevant due, scope, pipeline, or lead filter into the destination page.
Today queue
Filtered deep link
Destination records
Return to Today
- Today queueFiltered deep linkopen
- Filtered deep linkDestination recordsreview
- Destination recordsReturn to Todaycomplete
Process the queue and read the trend
- 1
Open the highest-risk queue
CRM > Today
Select the queue card with overdue, unread, or stale work.
Expected result: The destination opens with the relevant filter already applied.
If this does not happen: If the destination count differs, verify scope, Deal pipeline, time zone, and any filters that were changed after arrival.
- 2
Record the next durable action
Destination record
Complete, assign, reschedule, or add the action that reflects what will happen next.
Expected result: Returning to Today shows the item resolved or updated after data refresh.
If this does not happen: If save fails, keep the record open, copy any unsaved note, and retry. Do not assume the queue changed.
- 3
Review pipeline summary
Today > Pipeline card
Compare open count, value, and weighted value for the selected Deal pipeline.
Expected result: The totals provide context for the queue, without modifying deals.
If this does not happen: If totals look wrong, inspect stage probability and deal values in the selected pipeline.
- 4
Read the 12-week trend
Today > Trend
Review new leads, deals opened, advanced, won, and lost, plus win rate and median days to close.
Expected result: You can identify movement worth investigating in Deals or Reports.
If this does not happen: Use Reports for deeper context. Today is an operating summary, not a record-level export.
Handle empty, loading, and failure states
Today says nothing needs attention
Likely cause: The selected scope genuinely has no qualifying queue items.
- Confirm scope and Deal pipeline.
- Open Tasks or Leads without the Today filter if you need broader planning.
- Do not create placeholder records merely to populate the dashboard.
A queue shows an error or partial warning
Likely cause: One or more CRM requests failed.
- Select Retry.
- Keep the current scope and pipeline selected.
- Treat displayed counts as incomplete until the warning clears.
A task appears under the wrong day
Likely cause: Task grouping uses the resolved workspace time zone.
- Check the user time-zone override.
- Then check the company default.
- If neither is set, expect configured fallback and finally UTC.
End-of-review check
- No overdue item was silently ignored.
- Every active opportunity has a named next action.
- Unread inquiries were read before deletion or bulk action.
- Scope and pipeline are included in any shared summary.
- Errors were retried rather than reported as zero.