---
title: "Customer Reference Request Matching With AI Agents | Kylon"
description: "How a reference program matches sales requests to customers within fatigue limits, builds a weekly call slate and handles pauses in one Kylon room, with people deciding."
url: "https://kylon.io/use-cases/customer-reference-requests"
language: "en"
---
[HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Customer Reference Requests: A Weekly Call Slate That Respects Every Customer's Limits
Use Case8 min read
# Customer Reference Requests: A Weekly Call Slate That Respects Every Customer's Limits
Reference requests from reps are matched to eligible customers by industry and segment, fitted under a weekly call cap and re-matched when a customer pauses. The reference manager approves every slate before a customer is asked.
[Get started](https://app.kylon.io/sign-up)
Kylon TeamProduct
November 6, 2026
## 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
People
- Reference program manager
Owns the program policy, approves every match and weekly slate, and signs the close-out
- Customer success managers
Pause a customer when the relationship needs it and confirm who can be asked
- Account executives
Request references for late-stage deals and join the calls that get booked
- Reference coordinator
Builds the draft slate sheet each week and corrects it after review
Agents
- MycoReference matcher
Matches each request to an eligible customer by industry and segment, fits the slate under the weekly cap and re-walks requests when eligibility changes
PipedriveAttioGoogle Drive
- NovaSlate checker
Checks the coordinator's draft slate line by line against the approved matches
Google DriveAttio
- RyanCustomer outreach
Drafts the asks to customers and the notices to reps for a person to send, and follows rep replies in Slack
[Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack)
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.
```mermaid
flowchart TD
match["Myco matches each request to a
customer inside the fatigue limit"]
ok1["Reference manager
approves the matches"]
slate["Myco fits the calls under the
weekly cap by deal close date"]
ok2["Reference manager approves the
slate before any customer is asked"]
ask["Ryan drafts each ask
for a person to send"]
review["Nova checks the coordinator's
draft slate line by line"]
pause["CSM pauses a customer
in Attio"]
rewalk["Myco re-walks requests hit by a
pause or a lowered limit"]
fix["Coordinator corrects it, the
reference manager confirms"]
ok3["Reference manager
approves each new match"]
closed([A deal closes in Pipedrive])
withdraw["Myco proposes to withdraw the
request and release its call slot"]
notice["Ryan drafts the notice
for a person to send"]
close["Myco writes one close-out
record per segment"]
sign["Reference manager
signs off the week"]
match --> ok1 --> slate --> ok2 --> ask
ask --> review & rewalk
pause --> rewalk
review --> fix
rewalk --> ok3
fix & ok3 --> withdraw
closed --> withdraw
withdraw --> notice --> close --> sign
class match,slate,ask,review,rewalk,withdraw,notice,close agent
class ok1,ok2,pause,fix,ok3,sign person
class closed event
classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712
classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712
classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42
```
| Stage | What happens | Who acts | Who decides |
| --- | --- | --- | --- |
| Matching | Each of the 30 requests is matched to an eligible customer by industry and segment, inside the fatigue limit | Myco, from Pipedrive deals and Attio customer records | The reference manager approves the matches |
| Weekly slate | Matched calls are ordered by deal close date and fitted under the weekly cap, and each approved call is counted against its customer in Attio | Myco | The reference manager approves before any customer is asked |
| Draft review | The coordinator's slate is checked line by line for wrong customers, unmatched requests, out-of-batch lines and duplicates | Nova | The coordinator corrects it and the manager confirms |
| Pauses and limit changes | Requests matched to a newly paused customer, or pushed over a lowered limit, are re-walked from the top of the matching order | Myco | The CSM confirms the pause; the manager approves each new match |
| Deal closures | Requests on deals that closed in Pipedrive are withdrawn and their call slots released | Myco, then Ryan for the notices | The manager approves; a person sends each notice |
| Close-out | Six close-out records, one per segment, written from the current requests into the close-out table | Myco | The reference manager signs off the week |
Stages of a weekly reference cycle. Requests, customers and limits in this example are illustrative.
## 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](https://kylon.io/integrations/gmail)
- Google Drive
- Pipedrive
- [Slack](https://kylon.io/integrations/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.
Set-up prompt
Set up our customer reference request desk in this Room. Take it one step at a time and wait for my OK before you move on.
1. Connect Attio, Gmail, Google Drive, Pipedrive and Slack. Tell me which ones still need connecting.
2. Ask me who works this desk: the reference program manager, the customer success managers, the account executives and the reference coordinator. Help me invite them to this Room.
3. Build a Reference Slate App with columns Requested, Matched, Customer asked and Call booked, one record per request. Pull each open request from Pipedrive and Attio.
4. Match each request to an eligible customer by industry and segment, inside that customer's fatigue limit. Check the coordinator's draft slate line by line for wrong customers, unmatched requests, duplicates and slots held for closed deals. Show me everything that fails.
5. Hold every customer ask and rep notice as a draft in Gmail until the reference program manager approves the slate. Hold each re-walked match until the CSM confirms the pause and the reference program manager approves the new match. Hold the close-out records until the reference program manager signs off the week.
6. Write our matching order, fatigue limits, the weekly cap and our approval rule into this Room's guideline so every week follows the same order.
7. After one clean week, offer to turn the slate thread into an Automation.
Before you start, ask me for our rules one at a time.
[Get started](https://app.kylon.io/sign-up)
Your first company harness. Where humans and agents run your business together.
[Get started](https://app.kylon.io/sign-up)
## More Use Cases
[View all](https://kylon.io/use-cases)
[
### Warranty Claims: Decisions, Repairs and Payouts That Hold Up to Corrections
Claim decisions, repair partner routing, the disbursement file and every correction or recall bulletin run through one Kylon room. Agents read HubSpot, Notion and Stripe, and the warranty manager approves each decision before it is written.
ManufacturingSupport & customer success
](https://kylon.io/use-cases/warranty-claims)[
### Backorder Communications: Customers Hear the Latest Date, Not Last Week's
Customers hear the latest supplier date, an approved substitute or a cancellation offer, line by line. Agents work Pipedrive lines against Outlook notices and the Notion substitution table in one Kylon room, and every notice is a draft a rep sends.
Logistics & supply chainEmail operationsSupport & customer success
](https://kylon.io/use-cases/backorder-communications)