From spreadsheeted references to Salesforce + Calendly with consent?tracked approvals

Overview

An enterprise software firm’s customer reference program stalled because requests and approvals were buried in spreadsheets and long email threads. Intelligex implemented a Salesforce custom object to manage references end to end, automated consent tracking tied to privacy records, and integrated a scheduling tool to coordinate briefings. Requests moved through clear stages with accountable approvers, availability was visible without back-and-forth, and the team stopped firefighting to meet last-minute analyst and sales needs.

Client Profile

• Industry: Enterprise software
• Company size: Global B2B vendor serving regulated industries
• Stage: Scaling go-to-market operations and analyst relations
• Department owner: Marketing & Customer Engagement (Customer Advocacy/AR/PR)
• Other stakeholders: Sales, Customer Success, Legal/Privacy, Product Marketing, RevOps, IT

The Challenge

Reference requests arrived from sellers, analyst relations, and PR with varied urgency. The advocacy team tracked prospects in spreadsheets, including who could speak, what topics were allowed, and whether consent was current. As the pipeline grew, spreadsheets fell behind reality. Approvals from Account Executives and Customer Success Managers arrived at different times, and Legal needed assurance that consent covered the requested use. Scheduling calls turned into long coordination chains with customers and account teams.

Operationally, Salesforce was the system of record for accounts and contacts, but references lived outside it. Consent dates, restrictions, and red lines lived in cells that no one trusted. When a request came in, the team hunted for status across files and email, re-asked for the same approvals, and learned about support escalations too late. There was no reliable dashboard for leadership, no consistent aging view of requests, and no audit trail that tied a reference use back to the contact’s permissions.

Replacing core systems was out of scope. Sales and Success stayed in Salesforce, the marketing automation platform handled email, and the team used a scheduling app to coordinate calls. They needed to formalize the reference process inside Salesforce, standardize consent tracking, and automate handoffs—without asking teams to switch where they worked.

Why It Was Happening

The reference program lacked a structured object and workflow. Without a shared record in Salesforce, each request was treated as a one-off project. Owners changed midstream, and approvals sat in inboxes without visibility. Consent management was treated as a note rather than a governed status tied to privacy records. As a result, the team revalidated the same information repeatedly and still missed constraints.

Scheduling was disconnected from status. Even when a customer had agreed to act as a reference, meeting logistics were manual. The advocacy team played intermediary between calendars and time zones. Meanwhile, there was no automated check against account health or open escalations, so requests sometimes reached customers at the wrong moment.

The Solution

Intelligex implemented a Salesforce-based reference program with clear stages, automated checks, and integrated scheduling. A custom Reference object linked accounts, contacts, and opportunities to specific reference uses. Consent status synchronized with privacy records, and the workflow enforced approvals from Sales, Customer Success, and Legal before outreach. Scheduling integrated with the team’s calendaring tool, exposing only eligible, available customers for the request type. The process stayed inside Salesforce for owners, with email templates and scheduling links sent through existing tools.

• Salesforce custom object for References with fields for use case, allowed activities, consent status, expiration, regions, industries, product versions, and restrictions. Reference: Salesforce Custom Objects.
• Consent tracking tied to Salesforce privacy records using the Individual object, so permissions and expirations were authoritative and reportable. Reference: Salesforce Individuals (Privacy).
• Automated gating for account health: checks for open escalations, renewal windows, and support severity before the request advances.
• Approval processes inside Salesforce for Sales, Customer Success, and Legal before external outreach. Reference: Salesforce Approvals.
• Scheduling integration with Calendly meeting templates for “reference briefing” and “analyst inquiry,” pre-filtered to eligible customers. Reference: Calendly API.
• Email templates in the marketing automation tool populated from Salesforce fields for outreach, reminders, and thank-you messages, with suppression rules aligned to consent.
• Dashboards for request pipeline, aging, bottlenecks, customer availability by region/industry, and consent renewals coming due.
• Change log on each Reference record capturing approvers, consent updates, and scheduling history.
• Permissions aligned to roles: Advocacy manages references, Sales and Success approve participation, Legal controls redlines and term limits.

Implementation

• Discovery: Mapped request types, approval chains, and consent rules. Cataloged attributes the team needed to filter eligible customers. Reviewed current scheduling flows and customer touchpoints. Identified where misfires happened, such as contacting accounts under escalation.
• Design: Defined the Reference object schema and relationships to Accounts, Contacts, Opportunities, and Cases. Designed stages—intake, vetting, approvals, scheduled, completed, and archived—with entry/exit criteria. Specified automated checks for consent validity, account health, and regional limitations. Outlined email templates and scheduling flows.
• Build: Created the Salesforce custom object, fields, page layouts, and validation rules. Configured approval processes and automated checks. Integrated the Individual privacy records for consent status. Built the Calendly integration to create and update events tied to Reference records and contact preferences.
• Testing and QA: Ran sample requests end to end in a sandbox, including edge cases like expired consent, open support cases, or restricted topics. Verified that approvals and notifications routed correctly, and that scheduling respected time zones and availability. Confirmed audit logs and dashboards reflected reality.
• Rollout: Launched with analyst and PR requests first, then enabled sales references. Kept the spreadsheet as a read-only backup during the first cycle. Feature flags allowed the team to relax certain validations temporarily while training completed.
• Training and hand-off: Delivered short, role-based sessions for Advocacy users, approvers in Sales and Success, and Legal reviewers. Provided quick-reference guides for creating requests, approving, and scheduling. Established a shared support channel for questions and adjustments.
• Human-in-the-loop review: Approvals were mandatory at defined gates. Automation proposed eligible contacts and times; humans confirmed final selections and any exceptions, with reasons captured on the record.

Results

Requests progressed predictably from intake to briefing because the workflow enforced the right sequence of checks. Advocacy tracked status in Salesforce instead of emailing for updates. Sales and Success approved within the app, and Legal saw the exact use, consent term, and redlines before sign-off. Scheduling moved from long threads to templated links that only exposed compliant options.

Rework dropped as the system filtered out ineligible candidates and flagged issues before outreach. The team saw fewer last-minute cancellations due to support escalations or expired consent. Leadership gained a reliable view of pipeline and availability by segment, and customer goodwill improved because outreach respected preferences and timing.

What Changed for the Team

• Before: Spreadsheets and email chains; After: A Salesforce Reference record with stages, owners, and a clear audit trail.
• Before: Manual consent checks; After: Consent status synced to privacy records with automated expirations and renewals.
• Before: Surprise conflicts with support or renewals; After: Automated health checks that block risky requests.
• Before: Back-and-forth to schedule; After: Scheduling links mapped to eligible contacts and meeting types.
• Before: Unclear approver responsibility; After: Built-in approvals for Sales, Success, and Legal with visible timestamps.
• Before: No reliable reporting; After: Dashboards for pipeline, bottlenecks, and availability by region and industry.

Key Takeaways

• Make references a first-class CRM object so requests, approvals, and outcomes live where teams already work.
• Tie consent to privacy records and automate expirations and renewals to avoid risky outreach.
• Gate eligibility with signals from support and account health to prevent avoidable cancellations.
• Integrate scheduling so only compliant, available options are presented to requesters and customers.
• Use staged workflows and approvals to clarify ownership and reduce rework without slowing momentum.
• Start with a subset of request types, run in parallel with the old tracker briefly, then retire it once trust is established.

FAQ

What tools did this integrate with?
Salesforce for the Reference object, approvals, and reporting; Salesforce privacy records (Individual) for consent; a scheduling tool such as Calendly for briefing coordination; and the existing marketing automation platform for outreach and reminders using CRM-driven templates.

How did you handle quality control and governance?
Validation rules and approval processes enforced consent, account health, and topic restrictions before outreach. Consent status flowed from privacy records, and changes were logged with approvers and timestamps. Any exception required a documented rationale on the Reference record, visible in reports and audits.

How did you roll this out without disruption?
We piloted the process with analyst and PR requests while keeping the spreadsheet read-only for reference. Feature flags allowed gradual enforcement of checks. Training was role-based and short, and teams kept their existing email and calendar tools while the backbone moved into Salesforce.

How were customers’ preferences respected?
Contact preferences and consent terms lived in privacy records and drove eligibility. Outreach templates pulled only allowed topics and regions. Scheduling links were available only after approvals, and customers could reschedule or decline without losing track of the request state.

What reporting became available to leadership?
Dashboards surfaced request volume by source, stage aging, win rates for fulfilled requests, available references by region and industry, and upcoming consent renewals. Leaders saw bottlenecks and capacity at a glance, enabling more realistic commitments to sales, analysts, and PR.