Reference · built on requestOperator by FibricSales, quotes & revenue

Win-Loss Record

When a deal closes, assembles the reason from calls, quotes, and support threads and proposes a win or loss record for the owner.

Request accessPricing ↗

About

Most lost-reason fields hold a guess typed weeks later. Win-Loss Record starts when the CRM marks a deal won or lost. It gathers the calls logged on the deal and the calls the phone system holds for the contact, the quotes sent and their state, and any support tickets the same company opened in the deal's window.

From those it drafts the reason in a few lines, each tied to the call, quote, or ticket that supports it, and proposes the reason field value and a note on the deal. The owner confirms or corrects the reason. The CRM is written only after that.

This is a reference listing. It documents what Fibric would read from Win-Loss Record and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • HubSpot deals whose Is closed won or Is closed lost property turns true, with any Closed won reason or Closed lost reason the rep entered
  • Pipedrive deals whose status turns won or lost, with won_time, lost_time, and lost_reason
  • Calls logged on the deal: HubSpot call engagements with hs_call_direction, hs_call_duration, hs_call_disposition, hs_call_body, and hs_call_recording_url
  • Calls in the phone system: Aircall calls through GET /v1/calls/search with direction, duration, tags, comments, transcription, and missed_call_reason
  • Amazon Connect contact records with Channel, InitiationMethod, Agent, DisconnectReason, and ContactLens output where it is enabled
  • The quotes behind the deal: HubSpot quotes with hs_status and hs_quote_amount, or Business Central salesQuotes in Sent, Accepted, or Expired
  • Support threads for the same company: Zendesk tickets through GET /api/v2/search with their satisfaction ratings, or Intercom conversations with conversation_rating

Proposed actions

  • Target capability: propose the win or loss record as a note through POST /crm/v3/objects/notes, listing the reason, each piece of evidence, and any competitor named
  • Target capability: propose the Closed lost reason or Closed won reason on the HubSpot deal, or lost_reason on the Pipedrive deal, for owner confirmation
  • Target capability: propose one question to the owner as a task through POST /crm/v3/objects/tasks when the evidence does not settle the reason
  • Target capability: propose a Slack message to the deal team through chat.postMessage with the outcome and the reason, after the owner approves the record

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • HubSpot loss with the calls attached

    When Is closed lost turns true, search Aircall by the contact's number, read the calls' tags, comments, and transcription, and propose the Closed lost reason with a note quoting the evidence.

    With HubSpot, Aircall

  • Pipedrive win from the contact-center record

    On won_time, read the Amazon Connect contact records for the customer endpoint, their Agent, Queue, and DisconnectReason, and propose a win note the owner confirms.

    With Pipedrive, Amazon Connect

  • A loss with a support thread behind it

    Search Zendesk for the company's tickets and satisfaction ratings in the deal's window, and propose a loss record that names the ticket when a bad rating preceded the close.

    With HubSpot, Zendesk

  • Tell the deal team

    After the owner approves, post the outcome, the reason, and the note link to the deal channel through chat.postMessage.

    With Slack

Requirements

  • A CRM that marks deals won or lost with a timestamp: HubSpot or Pipedrive
  • A phone system whose calls carry notes, tags, or transcripts: Aircall, Amazon Connect, or calls logged in HubSpot
  • A service desk searchable by requester or organization: Zendesk or Intercom
  • A deal owner who confirms every record before the CRM is written
Authentication
A CRM OAuth app or private-app token with deal, note, and task write scopes, a phone-system API key with call read access, and a service-desk token with ticket and rating read access.

Limits

  • A reason is assembled from what was recorded. A call with no transcript, comment, or note contributes only its time and duration.
  • Amazon Connect delivers a contact record at least once and may deliver it again with new information. The record is built from the latest copy.
  • Zendesk search returns at most 1,000 results per query. A long ticket history is read through the search export endpoint instead.
  • The owner's own reason takes precedence. The proposal sits beside the rep's choice as evidence, and never overwrites a reason already entered without approval.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Win-Loss Record ↗

Questions and answers

What does the owner approve?
The reason and the record. The proposal shows the outcome, the reason it drafted, the calls, quotes, and tickets it read, and the line from each that supports the reason. The owner edits the reason or the evidence, approves, or rejects. Until then the deal's reason field is untouched.
Does it listen to call recordings?
It reads what the phone system exposes as text: Aircall transcription and comments, Amazon Connect ContactLens output where enabled, and hs_call_body on HubSpot calls. A recording with no transcript is listed by time and duration only. Audio is not transcribed by the operator.
What record is left?
One entry per closed deal: the deal id, the outcome and its timestamp, each call, quote, and ticket read with its id, the reason proposed, the reason approved, who approved it, and when. The note written to the CRM carries the same list.
Ask about Win-Loss Record

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy