Module

Smart Mentions

Tag teammates with @, reference records with #, and keep follow-up inside the record where work actually happens.

Smart Mentions is the contextual collaboration layer for operational records. Teams can @mention people and #reference related records directly inside notes, comments, and posts so ownership, context, and follow-up history stay connected to real business work.

Request a demo View pricing

Explore modules → Read guide →

What this module helps you control

@ mentions for users

# references for business records

Mentions inside notes, comments, and posts

Record-linked collaboration history

Direct ownership requests and accountability

Escalation handling when work is blocked

Cross-team handoffs with contextual traceability

Response discipline and closure behavior

Mention usage governance and clarity rules

Operational review outputs for coaching and process improvement

Business outcomes teams expect

Speed up internal coordination by tagging the right owner on the exact record that needs action.

Improve follow-up ownership with explicit @mentions instead of vague requests in side conversations.

Reduce context loss by keeping requests and replies attached to operational records, not disconnected chats.

Strengthen record-level collaboration across projects, sales, finance, support, and operations.

Escalate blockers faster with contextual requests that include linked dependencies and expected decisions.

Build a clearer audit trail showing who was tagged, what was requested, and when response happened.

Improve multi-team handoffs by preserving decision context in the source record.

Increase response discipline on urgent requests through explicit owners, urgency, and due-date language.

Cut time spent searching across the ERP by referencing related objects directly with #.

Keep communication connected to actual business execution instead of fragmented side channels.

What teams use most in this module

Practical capabilities that make day-to-day execution faster, cleaner, and easier to govern.

@ Mentions for People

Mention specific users while writing to assign clear ownership for an action in context.

Tag users directly with @mention syntax

Select teammates while typing

Create direct ownership requests

Improve follow-up speed for pending actions

Keep responsibility contextual to the record

# References for Business Records

Reference related records inline so discussions stay tied to the right objects and dependencies.

Reference projects, invoices, customers, estimates, contracts, expenses, leads, and proposals

Link the right business object directly in collaboration text

Reduce ambiguity around the intended record

Navigate from discussion to source object faster

Preserve cross-record context in one thread

Notes, Comments, and Posts

Use mentions in record activity where teams already collaborate, instead of shifting context to detached messaging.

Mentions supported in notes, comments, and posts

Contextual request-and-response history

Decisions remain visible in the working record

Clearer decision history and accountability

Improved continuity during handoffs

Record-Linked Collaboration

Maintain conversations in the source record so people can review full context before acting.

Conversation anchored to source record

Less ambiguity before execution

Faster understanding of dependencies

Stronger cross-functional handoff quality

Better continuity across lifecycle stages

Mention Visibility and History

Track mention activity over time for clearer accountability and operational reviews.

See who was tagged

Review when each mention happened

Capture what action was requested

Retain linked history over time

Support higher-quality handovers and audits

Follow-up Reliability

Use mention discipline to reduce dropped requests and improve closure behavior.

Direct action requests to owners

Fewer missed or dropped responses

Clearer closure expectations

Stronger accountability in execution cycles

Escalation path when work remains blocked

Cross-Team Coordination

Coordinate dependencies between sales, finance, operations, projects, and support from one contextual thread.

Multi-team collaboration in shared records

Clear dependency handling between departments

Cleaner escalation than disconnected channels

Aligned updates without copying context repeatedly

Better operational continuity across teams

Quick Reference to Related Objects

Use linked references to move quickly from discussion into the affected record and next action.

Reference links to related business objects

Faster jump from discussion to execution

Less searching across modules

Preserved context for reviewers

Cleaner collaboration in complex cases

Governance and Usage Rules

Define mention standards so teams use the module for actionable collaboration, not noise.

When to use mentions and when not to

Message clarity expectations

Urgency and due-date guidance

Owner accountability discipline

Team-level coaching and adoption standards

Reports and Review Outputs

Review mention behavior and response quality to improve collaboration discipline over time.

Mention volume by team and user

Open vs resolved mention threads

Mentions by module or record type

Response-time trend reviews

Operational coaching packs for managers

Start with this workflow

Follow these structured steps to launch one controlled process first, then expand.

Mention a teammate on a record

Open the target record.

Add a note, comment, or post.

Type @ and select the teammate.

Write the action request and priority.

Save the update.

Follow up inside the same record until closure.

Reference a related business object

Open the current note or comment area.

Type # to start object reference.

Choose the related project, invoice, customer, estimate, contract, expense, lead, or proposal.

Insert the selected reference.

Keep discussion tied to the right object.

Escalate blocked work

Identify the blocker in the current record.

Mention the responsible owner.

Reference the affected record or dependency.

Add required decision, deadline, and next action.

Review thread progress until closure is confirmed.

Run a multi-team handoff

Add a contextual handoff note in the source record.

Mention the receiving owner or team.

Reference linked records needed for execution.

Clarify expected action and due date.

Preserve handoff history in the same thread.

Resolve a mention follow-up

Open the mention context from the related record.

Review the linked record details before acting.

Complete the requested action.

Reply with a status update and decision outcome.

Treat the thread as resolved according to team practice.

Run weekly operations review of mentions

Review open mention threads.

Identify overdue follow-ups by owner or team.

Review team and user response patterns.

Coach teams on clarity and usage discipline.

Update governance rules where needed.

Who this module is for

Operations teams that need reliable follow-up on live records

Project teams managing dependencies and blockers

Sales and finance teams coordinating record-level actions

Support teams escalating internal requests in context

Team leads and managers reviewing response discipline

Organizations that need contextual collaboration tied to real records

Common problems this module helps solve

Action requests get lost in chat conversations

Discussions become disconnected from the source record

Ownership of follow-up requests is unclear

Internal escalations move slowly when context is missing

Teams repeatedly search for related records during discussion

Handoffs lack traceability and decision history

Cross-team dependencies create coordination gaps

No clean history of who was asked to do what and when

Connected records across modules

CRM and Sales teams can tag finance or operations directly on live customer records for faster execution.

Projects teams can mention owners and reference blockers while preserving full project context.

Core Accounting teams can reference invoices, contracts, and customers inside finance follow-up discussions.

Support Desk teams can mention internal owners on service records instead of splitting context into side channels.

People Records helps teams identify and involve the right internal owners in cross-functional follow-up.

Smart Mentions acts as a cross-module collaboration layer rather than a standalone chat system.

Built-in Reports & Analytics

Mention volume by user and team for adoption review

Open vs resolved mention threads for follow-up reliability

Mentions by module and record type for process analysis

Response-time trends by team and workflow

Escalation hot spots by department or operational flow

Collaboration review packs for operations managers and team leads

FAQ

Can we mention teammates directly inside records?

Yes. Teams can use @mentions inside notes, comments, and posts to tag owners where work is happening.

Can we reference related business objects with #?

Yes. Smart Mentions supports # references so teams can point to related records directly in collaboration text.

Which records can be referenced?

Common references include projects, invoices, customers, estimates, contracts, expenses, leads, and proposals where enabled in your workflows.

Can Smart Mentions reduce reliance on side-channel chat?

It helps teams reduce context loss by keeping requests and updates in the source record, while still allowing other communication tools when needed.

How do we keep mention requests clear and actionable?

Use message standards: define owner, action, urgency, due date, and expected outcome in the same record thread.

Can teams review overdue or unresolved mentions?

Yes. Managers can review open vs resolved threads and response-time trends to enforce follow-up discipline.

How should this module differ from chat tools?

Smart Mentions is for contextual collaboration tied to business records, not broad team chat.

How should this module differ from Support Desk?

Support Desk manages service tickets and customer support workflows; Smart Mentions focuses on internal record-linked collaboration and ownership.

Who should own mention usage guidelines?

Collaboration Admins and operational leaders should define usage standards and coach teams.

When should we use a mention versus a task or ticket?

Use mentions for contextual requests and quick ownership prompts; create tasks or tickets when formal lifecycle tracking is required.

Plans that include this module

Confirm commercial fit before rollout planning.

Business Plan

Enterprise Plan

View pricing

Ready to evaluate Smart Mentions with your team?

We will map this module to your current process, owners, controls, and rollout timeline.

Request a demo View pricing Explore modules

User guide

How to use Smart Mentions

Setup checklist, key workflows, reports, and troubleshooting.

Open user guide

Talk to our solution team

Tell us what you need and we will reply with a rollout plan and recommended modules.

Fields marked with * are required.

Platform

Modules

Customer stories

Use cases

Guides

Product guide