Skip to main content
HOME>Use Cases>Backorder Communications: Customers Hear the Latest Date, Not Last Week's
Use Case7 min read

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.

Get started
Kylon TeamProduct

Backordered lines, shifting supplier dates and a substitution table

A backorder desk decides, line by line, what each customer hears. If the supplier's date is inside the customer's wait limit, the line waits and the customer gets the new date. If not, the desk offers an approved substitute, or a cancellation when there is none. Each disposition has a reason code and a recording convention, and the customer notice follows from it.

Backordered lines are Pipedrive deals. Supplier ETA notices arrive in the purchasing mailbox in Outlook, often two or three per supplier in a week. The substitution table is a Notion page the product team keeps, the policy and a colleague's draft worksheet are in Google Drive, and the warehouse posts stock updates in Slack. A rep working from Monday's notice will promise a date the supplier withdrew on Wednesday.

Who works in the room

People

  • Backorder desk lead

    Owns the policy, approves every disposition and signs off the per-customer totals

  • Customer service reps

    Send customer notices and record each customer's answer

  • Purchasing

    Works with suppliers and confirms which ETA notice is current

  • Product manager

    Maintains the substitution table and approves each substitute

Agents

  • MycoLine disposition

    Disposes each backordered line from the latest supplier ETA and the substitution table, and re-derives lines after any change

    PipedriveOutlookNotionGoogle Drive
  • AdaWorksheet reviewer

    Reviews a colleague's draft worksheet against the policy and flags only the lines it covers

    Google DrivePipedrive
  • NovaCustomer notices

    Drafts customer notices in Outlook for a rep to send and writes the per-customer close-out notes

    OutlookPipedriveSlack

A forwarded supplier notice with no mention lands with Myco, the default agent, who owns the dispositions. Ada is mentioned only for worksheet reviews. Nova takes over once a disposition changes: Myco mentions Nova with the line ids and the new reason, and Nova drafts each notice through the rep's own Outlook account, checked on every call, so the draft sits ready for that rep to send.

One backorder cycle

The policy's rule order and recording conventions are written into the room guidelines. Nothing reaches Pipedrive or a customer without a person.

  • Agent works
  • Person decides
  • Arrives or gets recorded
Scroll sideways to see the whole flow.
StageWhat happensWho actsWho decides
Line dispositionEach in-scope line gets a disposition from the latest ETA notice for its supplier and from the substitution tableMyco, from Pipedrive, Outlook and NotionThe desk lead approves before Pipedrive is updated
Worksheet reviewA colleague's draft worksheet is checked under the policy's review section, and only the lines it covers are flaggedAdaThe colleague corrects the worksheet
Customer noticesCustomers whose line changed get a new date, a substitute or a cancellation offerNovaA rep sends each draft from Outlook
ETA revisionEvery line from that supplier is re-derived under the full rule orderMycoPurchasing confirms which notice is current
Substitution changeThe table entry is updated, then every line on that SKU is re-derivedMycoThe product manager confirms the substitute and the desk lead approves
Cancellations and close-outDeclined lines are recorded as canceled under the reassessment clause, then totals per customer are notedMyco, then NovaThe desk lead signs off the cycle
How a weekly cycle runs, using illustrative lines, SKUs and dates.

When the supplier's date moves twice in one week

Suppliers rarely send one date. A notice on Monday says the 18th, a revision on Wednesday says the 2nd of next month, and a forwarded copy of Monday's notice turns up on Thursday. Myco uses the latest notice per supplier, and when a revision arrives it re-derives every line from that supplier under the full rule order, because a later date can push a line past the customer's wait limit and into a substitute or cancellation offer.

A substitution change works across a SKU. When the product team swaps the approved substitute, the Notion entry is updated first, after the desk lead approves, and then every line on that SKU is re-derived, including lines that were simply waiting. A batch of customer cancellations is recorded under the policy's reassessment clause, so each canceled line carries the same reason and is counted the same way at close.

What the checks catch

  • An ETA taken from an earlier notice after the supplier has sent a revision
  • A worksheet flag on a line the draft worksheet never covered
  • A SKU-77 line left on the old substitute because only some lines were re-derived
  • A canceled line recorded outside the reassessment clause, which throws off the per-customer totals

What stays with people

  • Approving each disposition before Pipedrive changes
  • Sending every customer notice, which Nova prepares as an Outlook draft
  • Choosing an approved substitute, which stays with the product team
  • Signing off the per-customer totals at close

Integrations in this workflow

Kylon is not an order management system and it does not take the place of one. It sits across Pipedrive, Notion and the desk's mailbox and holds the coordination between them. The purchasing lead owns the mailbox connection and approved a lasting grant so Myco can read supplier notices in this room.

  • Pipedrive holds each backordered line as a deal, with disposition fields and per-customer notes
  • Outlook receives supplier ETA notices and carries customer notices as drafts a rep sends
  • Notion holds the substitution table the product team maintains
  • Google Drive keeps the backorder policy, the draft worksheet and supplier change notices
  • Slack is where purchasing and the warehouse post supplier and stock updates

Where to start

One supplier and one week of lines is enough to begin. Connect Pipedrive and the purchasing mailbox, share the Notion substitution table with the room, and add an automation that opens the review every Monday morning. Then write the rule the desk cares about most into the room guidelines: only the latest ETA notice per supplier is used, and no customer is contacted until a rep sends the draft.

“Customers hear one date per line, and it is the latest one the supplier sent.”

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

Your first company harness. Where humans and agents run your business together.

Get started

More Use Cases

View all

Carrier Damage Claims: Filings That Match the Tariff and the Paperwork

Thirty freight damage claims, the filing manifest, carrier acceptances, a disputed delivery receipt and a tariff revision run through one Kylon room. Agents read ClickUp and the Dropbox claim packets, and the claims manager approves every change.

Logistics & supply chainFinance operationsSupport & customer success

Constrained Order Allocation: Short Stock Shared by Priority, Walk After Walk

Short stock is shared by priority tier and walked again after every receipt, tier change and cancellation. Agents work the Salesforce orders in one Kylon room, report every order after each walk, and the planner approves the full result.

Logistics & supply chainSupport & customer success