Customer Reference Requests: A Weekly Call Slate That Respects Every Customer's Limits

Willing customers, hidden limits and a slate built from memory

Account executives ask for a reference when a deal gets close: a customer in the same industry, about the same size, ideally one who went through the same rollout. The request arrives in Slack with a Pipedrive deal link that carries the prospect's industry and segment. The reference program keeps its customers in Attio, each with a fatigue limit on calls per quarter and a pause flag that customer success sets during a renewal or an escalation.

Matching thirty requests by hand means switching between both tools for every one. The weekly call slate is a sheet that a coordinator builds from memory of last week's calls. A customer paused on Tuesday still appears on Thursday's slate, the same advocate gets three calls in one week because nobody counted across requests, and a request whose deal closed last week still holds a call slot.

Who works in the room

Requests land in one Kylon room, and an automation opens the week's slate thread every Monday morning. Myco is the default agent, so a rep who writes that they need a logistics reference gets Myco without naming it. Nova takes anything about the draft slate, and Ryan owns every email to a customer. Myco reads Pipedrive and Attio through lasting grants the sales operations lead approved for the room. When the reference manager approves a slate, Myco hands the confirmed matches to Ryan in the same thread, each with the customer, the contact and the call window.

The weekly reference cycle

The program policy sits in Google Drive: matching order, fatigue limits, the weekly call cap and what counts as the same segment. The room guidelines point at it, and every match carries the rule that made it.

A customer pauses, a limit drops

A CSM posts in Slack that two customers are entering renewal talks and should take no reference calls this month, then sets the pause in Attio. Myco finds the ten requests matched to those two customers and re-walks exactly those ten from the top of the matching order. Requests matched to anyone else keep their matches, so calls already arranged do not move.

A lower fatigue limit reaches further. When the program drops the limit from three calls a quarter to two, Myco re-counts every customer near the limit across the whole quarter, not only this week, and re-walks any match that now goes over. Corrections go into one revised slate the reference manager approves, so reps never work from two versions of the same week.

What the checks catch

• A request still matched to a customer whose CSM paused them after the first pass
• A match that takes a customer over the fatigue limit once the quarter's earlier calls are counted
• Draft slate lines that name the wrong customer, an unmatched request, last week's request or the same request twice
• A call slot still held for a deal that has closed in Pipedrive
• Close-out notes written onto the request records instead of into the close-out table

What stays with people

• Approving the matches and the weekly slate before any customer is asked
• Pausing a customer, which the CSM decides from the relationship
• Sending each ask and notice that Ryan prepares as a draft
• Signing off the week's close-out

Integrations in this workflow

Kylon is not a reference management tool and does not stand in for one. It works alongside Pipedrive, Attio and the team's inboxes, and the matching and follow-through happen in the room.

• Attio
• Gmail
• Google Drive
• Pipedrive
• Slack

• Pipedrive holds the requesting deals, with the industry, segment and stage each match depends on
• Attio holds the reference customers, each one's calls this quarter and any pause
• Gmail carries asks to customers and notices to reps, sent by a person from Ryan's drafts
• Slack is where reps post requests and CSMs announce a pause
• Google Drive keeps the program policy and the coordinator's draft slate

Where to start

Pick one week's requests. Connect Pipedrive and Attio to the room, add a small App for the request queue and the close-out table, and write the rule that matters most into the room guidelines: no customer is asked for a call until the reference manager approves the slate.

“Every customer on the slate said yes once. Counting their calls correctly is how they keep saying yes.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.