Reference · built on requestOperator by FibricSales, quotes & revenue

Quote Follow-up

Finds sent quotes with no reply past your day limit, checks support threads first, and proposes the follow-up for the rep to send.

Request accessPricing ↗

About

Quote Follow-up reads the quotes your team has already sent and watches for silence. In HubSpot that is a quote in APPROVED or APPROVAL_NOT_NEEDED status with an hs_expiration_date still ahead. In Business Central it is a salesQuote whose status is Sent, with its sentDate and validUntilDate. When a quote passes the number of days you set with no reply, it looks up the customer in your service desk before doing anything else.

If an open ticket or a recent conversation explains the silence, the proposal says so and suggests waiting. Otherwise it drafts the follow-up in the rep's own mailbox and a task on the deal. The rep sends it or discards it. The customer hears nothing until then.

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

  • Published HubSpot quotes: hs_status APPROVED or APPROVAL_NOT_NEEDED, with hs_expiration_date, hs_quote_link, and the associated deal and line items
  • Business Central salesQuotes in status Sent, with sentDate, validUntilDate, customerNumber, and totalAmountIncludingTax
  • Pipedrive deals still open, with expected_close_date, owner_id, and last_activity_id, so a quote with recent activity is left alone
  • Support threads for the quote's contact: Zendesk tickets through the Search API, Intercom conversations through POST /conversations/search filtered by contact_ids and updated_at
  • Kustomer conversations for the same customer, with status and updatedAt, so an open complaint is seen before a nudge goes out
  • Replies already in the rep's mailbox thread, so a quote answered by email is not counted as silent

Proposed actions

  • Target capability: propose a follow-up as a Gmail draft through users.drafts.create in the original threadId, or an Outlook draft through POST /me/messages
  • Target capability: propose a task on the deal through POST /crm/v3/objects/tasks with hs_task_type EMAIL, hs_timestamp, and hubspot_owner_id
  • Target capability: propose waiting when an open ticket exists, with the ticket linked, instead of a follow-up
  • Target capability: propose a Slack message to the quote owner through chat.postMessage listing the quote, days silent, and the draft

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

What you can build

  • HubSpot quote, Zendesk check, Gmail draft

    When an APPROVED quote passes your threshold, search Zendesk for the contact's open tickets, then draft the follow-up in the rep's Gmail thread and open a task on the deal.

    With HubSpot, Zendesk, Gmail API

  • Business Central quote with Intercom history

    Read salesQuotes in status Sent that are approaching validUntilDate, check Intercom conversations for the contact, and draft the note as an Outlook message.

    With Microsoft Dynamics 365 Business Central, Intercom, Microsoft Outlook

  • Pipedrive deal gone quiet

    For open deals with no activity since the quote went out, propose a follow-up activity with due_date and a message to the owner in Slack.

    With Pipedrive, Slack

  • Kustomer first

    Before any nudge, read the customer's Kustomer conversations. An open one turns the proposal into a wait with the conversation linked.

    With Kustomer

Requirements

  • A CRM that records sent quotes with dates: HubSpot quotes, Business Central sales quotes, or Pipedrive deals with activities
  • A service desk to check first: Zendesk, Intercom, or Kustomer, with read access to tickets or conversations by customer
  • A mailbox where drafts can be created for the rep: Gmail API or Microsoft Graph
  • A day threshold and a named owner for each quote, since the draft lands in that person's mailbox
Authentication
CRM access through a HubSpot private app token or Pipedrive API token, a service-desk API token with ticket read scope, and a mailbox draft scope (gmail.compose or Mail.ReadWrite) for the rep's account.

Limits

  • It never sends. The draft sits in the rep's mailbox and the customer receives nothing until the rep sends it.
  • Silence is measured from the quote's sent date and the mailbox thread. A reply by phone that nobody logged still looks like silence.
  • Zendesk search returns at most 1,000 results per query, so a long customer history is read newest first.
  • One follow-up per quote per threshold. It does not chase the same quote again until a person resets it.

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 Quote Follow-up ↗

Questions and answers

What does the rep approve?
A draft follow-up in their own mailbox, with the quote, the days since it was sent, and any support thread found. They edit and send it, or discard it. If a ticket is open, the proposal is to wait, and approving it only records the decision.
What if the customer already replied somewhere else?
It checks the mailbox thread and the service desk before proposing anything. A reply in either turns the quote from silent to answered and no draft is made. A phone call that nobody logged is invisible to it.
What record does it leave?
One entry per quote checked: quote id, sent date, days silent, the tickets and conversations read, the draft created or the wait proposed, who decided, and when. Deleting the draft undoes the only change it made.
Ask about Quote Follow-up

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