Reference · built on requestOperator by FibricSales, quotes & revenue

Lead Response

Watches each new inbound lead for a first reply inside your window and proposes a reply draft or a reassignment when time runs out.

About

Lead Response starts a clock when a lead arrives: a HubSpot contact created with lifecyclestage lead, a Salesforce Lead with IsUnreadByOwner true, a Pipedrive lead with its add_time, or a Meta lead ad delivered by the leadgen webhook. It watches for the first touch: an outbound call in Aircall or Amazon Connect to the lead's number, an email from the owner, or a logged activity.

The clock pauses outside the hours you set and on public holidays read from the Nager.Date holiday feed. When the window closes with no touch, it proposes a reply draft for the owner and, if the owner is away, a reassignment. A manager or the owner approves. The lead is not contacted by the operator.

This is a reference listing. It documents what Fibric would read from Lead Response 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 HubSpot contacts through the webhooks journal (objectTypeId, CREATE action, occurredAt), with lifecyclestage, email, phone, and createdate
  • Salesforce Leads with LeadSource, Status, OwnerId, CreatedDate, IsUnreadByOwner, and LastActivityDate
  • Pipedrive leads through GET /api/v1/leads with owner_id, add_time, and next_activity_id
  • Meta lead ads through the leadgen webhook (leadgen_id, form_id, ad_id, created_time) and GET /{lead-id} for field_data
  • Outbound calls to the lead's number: Aircall calls with direction, started_at, answered_at, and user; Amazon Connect contacts through SearchContacts with InitiationMethod and InitiationTimestamp
  • Public holidays for your country from GET /api/v4/Holidays/{CountryCode}/{Year}, with date and nationalHoliday, so the clock pauses on them

Proposed actions

  • Target capability: propose a first reply as a draft in the owner's mailbox, built from the lead's form answers, for the owner to send
  • Target capability: propose reassigning the lead by changing hubspot_owner_id, Salesforce OwnerId, or Pipedrive owner_id to the next available rep
  • Target capability: propose a call task: a HubSpot task with hs_task_type CALL and hs_timestamp, a Salesforce Task with ActivityDate, or a Pipedrive activity with due_date
  • Target capability: propose a Slack message to the owner and their manager through chat.postMessage with the lead, the elapsed time, 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 form lead, Aircall call check, Gmail draft

    On a contact CREATE event, watch Aircall for an outbound call to the phone number; if the window closes, draft a reply in the owner's Gmail and open a CALL task.

    With HubSpot, Aircall, Gmail API

  • Salesforce Lead with Amazon Connect

    For Leads with IsUnreadByOwner true, search Amazon Connect contacts by AgentIds and TimeRange; propose OwnerId reassignment when nothing was dialed in time.

    With Salesforce Sales Cloud, Amazon Connect

  • Meta lead ads into Pipedrive

    Receive leadgen webhooks, read field_data, match to the Pipedrive lead, and propose a follow-up activity with due_date and due_time for the owner.

    With Meta Marketing API, Pipedrive

  • Holiday-aware clock

    Pause the response window on dates from the Nager.Date feed and outside your hours, then post the overdue list to the sales channel in Slack.

    With Holidays & FX Reference, Slack

Requirements

  • A CRM that emits new-lead events: HubSpot webhooks, Salesforce Lead records, or the Pipedrive Leads API
  • A phone system whose call log names the agent and the number dialed: Aircall or Amazon Connect
  • Lead ad forms, if used: Meta leads_retrieval and pages_manage_ads permissions on the page
  • Your business hours, country code for holidays, and the response window in minutes or hours
Authentication
A CRM token with contact or lead read and write scopes, read access to call logs in your phone system, and a mailbox draft scope for the owner.

Limits

  • It measures the first touch it can see. A reply from a personal phone or an unlogged channel counts as no touch.
  • Reassignment changes the owner field only. It does not know who is on vacation unless the CRM or a roster says so.
  • Meta lead data is read through the leads endpoints and the webhook; if the page permissions lapse, those leads are not seen.
  • The holiday feed covers the national and regional dates it publishes. Company shutdown days must be added by hand.

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 Lead Response ↗

Questions and answers

What does the owner or manager approve?
The reply draft, the reassignment, or both. The proposal shows the lead, when it arrived, what was checked for a first touch, and how much of the window is left. The owner sends the draft or discards it. A manager confirms a reassignment.
Does it ever message the lead itself?
No. It drafts. The draft waits in the owner's mailbox or as a task. Sending, calling, and texting the lead stay with a person.
What record is left for each lead?
Lead id, arrival time, the window applied with pauses for hours and holidays, each source checked for a touch, the proposal made, who approved it, and when. If an owner was changed the entry names the previous owner so it can be put back.
Ask about Lead Response

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.