Name of Feature/Request: Email notification sent to the system administrator when a customer creates a discussion without tagging a specific person
What financial, time savings, or quality of life improvements will occur from this: Add Discussion as Trigger in a Workflow | Frequency: During Operations | 1. Visibility & AccountabilityDiscussions tied to records (like Sales Orders, Tasks, Customers, etc.) help ensure that Importsant conversations are documented in context. This promotes accountability—team members can see who said what and when.
2. Avoid Missed CommunicationIf a user adds a note or comment without using the “@” mention, others may not be notified. By tracking discussions, especially those not properly tagged, teams can catch Importsant messages that might otherwise go unnoticed.
3. Improved CollaborationCentralizing discussions within Striven helps keep everyone on the same page, especially in cross-functional teams. Instead of relying on scattered emails or external chats, all communication stays linked to the relevant record.
4. Easier Audits & HandoffsWhen reviewing a customer record, invoice, or task history, having a log of discussions gives complete context—crucial for audits, training, or team handoffs.
5. Supports Better Decision-MakingSeeing prior discussions on a transaction can help managers or team members make more informed decisions, avoid duplicate work, and identify trends or recurring issues.
6. Enhances Customer ServiceIf a customer reaches out with a concern, internal discussions tied to their account or orders can be quickly referenced, helping support staff respond more effectively and professionally.
Attempted Solutions So Far: Created report builder using discussions dataset then add the report as a LINK in Striven as a temporary solution for tracking discussions sent as comments or notes by his customer.
The alternative solution, instead of triggering a workflow based on discussions, is to have an email notification sent to the system administrator when a customer creates a discussion without tagging a specific person. We discussed this with Russell, and he agreed that this approach would help ensure such discussions aren’t missed.
Digging deep - Any additional Why behind this request / How was this accomplished before Striven in what system or software: Previously accomplished: Built a report using discussions dataset.
StrivenID: 5401789