Have something to say?

Tell us how we could make the product more useful to you.

Maps by Product Type and Contact Roles

Product-Specific Roles Need: Assign product-specific roles within a single relationship map. Goal: Reflect Semperis's multi-product business model, where different people often make decisions for different products. Example: Label contacts as "Decision Maker: ADFR" and "Decision Maker: DSP." Solution: Add a product-specific label field to contacts and enable filtering/reporting on it. Maps by Product Type and Contact Roles: The final point addressed was the need to designate contacts as decision makers or champions for a specific product within the relationship map. Since there is currently a rule allowing only one relationship map per account, the team agreed that within that map, it would be useful to add an additional label to designate the contact's role (e.g., decision maker) for a specific product (e.g., ADFR or DSP) (00:24:17). This added label would then be used to build a report and enable filtering capabilities (00:25:09).

Nick Campion about 11 hours ago

Idea

Linking Maps to Salesforce Opportunities

Linking Maps to Salesforce Opportunities Need: Link the Decision Maker from a relationship map to the corresponding open Salesforce opportunity. Goal: Ensure sales opportunities are always associated with the correct decision-maker contact. Status: Sasha Selimotic will provide more details via email. Connecting Decision Makers to Open Opportunities (Sasha's Item): Mark Beebe briefly raised an item from Sasha Selimotic, who was no longer on the call, about tying the decision-making contact identified in the relationship map to an open opportunity in Salesforce. The goal is to ensure that decision makers, especially for specific products, are associated with the relevant sales opportunities, moving away from siloed information. Mark Beebe noted they would follow up on this item via email (00:26:03).

Nick Campion about 11 hours ago

Idea

Alert managers when a contact is changed in a relationship map.

Alerting on Decision-Maker Changes Need: Alert managers when a Decision Maker is changed in a relationship map. Goal: Proactively manage risk, especially for large accounts with upcoming renewals. Solution: Log the change as a Salesforce activity or create a dedicated report. An email alert is a less preferred option. Alerting to Decision Maker Changes in Tier Zero Accounts: A key risk management objective is flagging when the decision maker or economic buyer has changed in a Tier 0 account map (00:14:47). Mark Beebe explained that a change in the decision-making contact alerts management to the need to build a relationship with the new person, especially if a renewal is approaching (00:15:38). Nick Campion clarified that the desired outcome is for a manager to be notified when an employee changes the decision maker internally within the relationship map (00:21:44). Mechanism for Alerting to Decision Maker Changes: The preferred mechanism for alerting managers to a change in the decision-making contact is through a Salesforce report, which would allow them to see which accounts had this event occur, rather than relying on an email alert that might become noise (00:22:45). Madhava Kotte proposed creating a task or activity to keep track of the change event (00:21:44). Mark Beebe reiterated the value of the report, particularly when related to large accounts and renewal dates (00:23:34).

Nick Campion about 11 hours ago

Idea