Reference · built on requestOperator by FibricSales, quotes & revenue

RFQ Intake

Reads inbound RFQs from mail, tickets, and sheets, matches lines to your item master, and drafts a quote with unmatched lines flagged.

About

RFQ Intake watches the places a request for quotation lands: a shared mailbox, a service-desk ticket, or a spreadsheet dropped into a shared drive. It reads the message and its attachments, pulls out the line items, and matches each line to your ERP's item master by item number, name, or GTIN.

Matched lines become a draft quote in the ERP with the item master's unit and price. Lines that match nothing are flagged at the top of the draft with the closest candidates. You open the draft, fix the flags, and send it yourself. The operator never sends a quote.

This is a reference listing. It documents what Fibric would read from RFQ Intake 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

  • New mail in a shared inbox, through Gmail API watch notices and history, or Microsoft Graph change notifications on the Inbox folder
  • Attachments on those messages: spreadsheets and PDFs fetched through users.messages.attachments.get or the message's attachments relationship
  • RFQs filed as tickets: Zendesk ticket comments and their attachments with a content_url, Freshdesk tickets, Front conversations
  • Request sheets in shared storage: a Google Sheets range through spreadsheets.values.get, or a file in a SharePoint document library
  • The item master in your ERP: Business Central items with number, displayName, gtin, baseUnitOfMeasureCode, unitPrice, and blocked
  • Prior quotes for the same customer: salesQuotes with status Draft, Sent, Accepted, or Expired and their validUntilDate
  • The customer record behind the requester: number, currencyCode, and paymentTermsId, so the draft carries the right terms

Proposed actions

  • Target capability: propose a draft quote in your ERP, one salesQuoteLine per matched item with quantity, unit of measure, and item master price
  • Target capability: propose a flag on each unmatched line, listing the nearest item numbers, for a person to pick one or drop the line
  • Target capability: propose an acknowledgement to the requester as a mail draft, naming the lines that still need a part number
  • Target capability: propose a private note or label on the source ticket that points to the draft quote number

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

What you can build

  • Draft a quote from a mailbox RFQ

    Watch a shared inbox through the Gmail API, pull the attached spreadsheet, match each line to a Business Central item, and open a draft salesQuote with the unmatched lines listed first.

    With Gmail API, Microsoft Dynamics 365 Business Central

  • Quote an RFQ that came in as a ticket

    Read the attachments on a Zendesk ticket's comments, match the lines against the NetSuite item master, and propose both the draft quote and a private ticket note linking to it.

    With Zendesk, NetSuite

  • Match a request sheet in a shared drive

    When a customer's request sheet lands in Google Sheets, read the range, match the lines, and propose the draft in Acumatica with the flagged lines on top.

    With Google Sheets, Acumatica Cloud ERP

  • Tell the requester what is missing

    Propose an Outlook reply draft that lists the matched lines and asks for a part number on each flagged one, ready for the rep to send.

    With Microsoft Outlook, Front

Requirements

  • A mailbox or service desk where RFQs arrive: Gmail API, Microsoft Outlook, Zendesk, Freshdesk, or Front
  • An ERP whose item master and quotes are readable and writable by API, such as Business Central, NetSuite, or Acumatica
  • Read access to the drive or library where request spreadsheets land: Google Drive, Google Sheets, or SharePoint
  • One named approver for every draft quote before it is sent
Authentication
Mailbox and drive access through OAuth 2.0 with the Gmail or Microsoft Graph scopes you grant, a service-desk API token, and an ERP API user permitted to create quotes.

Limits

  • It never sends a quote. The draft waits in your ERP until a person edits, approves, and sends it.
  • Matching uses the item numbers, names, and GTINs in your item master. A line that fits none is flagged, not guessed.
  • Scanned or photographed line lists need legible text. A poor scan comes back as unmatched lines for a person to type.
  • A customer portal is read only where it exposes an API or forwards the RFQ to a mailbox it can watch.

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 RFQ Intake ↗

Questions and answers

What does a person approve?
The draft quote. Each line shows the RFQ text, the item it matched, the quantity, the unit, and the item master price. Flagged lines sit at the top with candidate items. The rep edits, approves, or rejects. Until then the customer receives nothing.
What record is left after an RFQ is handled?
One entry per RFQ: the source message or ticket id, the attachment read, each line and the item it was matched to, the lines flagged, the draft quote number, who approved it, and when. The entry also says how to delete the draft.
Does it ever set a price or add an item on its own?
No. Prices come from the item master or price list in your ERP. It never invents a price, never creates an item, and never edits the item master. A new item is a flag for a person.
Ask about RFQ Intake

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.