Reference · built on requestOperator by FibricCustomer support

Noise Filter

Finds auto-replies, bounces, vendor mail, and spam among inbound conversations. Proposes closing or tagging them without an agent.

Request accessPricing ↗

About

Some of what lands in a support inbox is not a customer. Out-of-office replies, delivery failures, invoices from vendors, newsletters, and spam each open a conversation that an agent then has to look at and close. Noise Filter reads the inbound stream, the bounce events from your mail provider, the suspended queue in your help desk, and your staff directory. From those it sorts each item into a kind: auto-reply, bounce, vendor, internal, or spam.

It then proposes a batch: close these, tag those, block this sender, recover that one because it is a real person. An agent approves the batch, or pulls lines out of it, before anything is written. Every closed item keeps a tag naming why.

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

  • Suspended tickets in Zendesk with the cause field: Detected as spam, Failed email authentication, Anonymous request, and the other causes Zendesk records
  • Conversations in Kustomer carrying the spam attribute, and the addresses on the Spam Filters block list and allow list
  • The spam flag and channel on each Gorgias ticket
  • Bounce webhooks from Postmark with Type, TypeCode, Inactive, and CanActivate for the address
  • Event Webhook events from Twilio SendGrid: bounce, dropped, deferred, spamreport, and unsubscribe
  • Users and groups in Google Workspace, so a message from your own staff or an internal alias is recognized as internal
  • Sender addresses and subjects on inbound messages in the support tool, so repeat automated senders can be counted

Proposed actions

  • Target capability: propose closing a conversation as noise: Mark as Done in Kustomer, or a Zendesk status change with a tag naming the kind
  • Target capability: propose a tag on each item naming its kind, so agents can hide it and reports can exclude it
  • Target capability: propose adding a sender to the Kustomer Spam Filters block list, or a wildcard entry for a whole domain
  • Target capability: propose recovering a suspended Zendesk ticket that is a real customer through PUT /api/v2/suspended_tickets/{id}/recover
  • Target capability: propose a note on the customer record when Postmark reports the address Inactive, so agents stop replying to it

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

What you can build

  • Close out-of-office replies without an agent

    Auto-replies from customers and from your own staff open conversations in Kustomer overnight. The operator proposes Mark as Done with an auto-reply tag on each, checking senders against Google Workspace so internal mail is labelled internal.

    With Kustomer, Google Workspace

  • Recover a real customer from the suspended queue

    A Zendesk ticket was suspended as Failed email authentication but the sender is a known customer with open orders. The operator proposes recovery; an agent approves before the 14-day deletion.

    With Zendesk

  • Stop replying to a hard-bounced address

    Postmark reports a HardBounce with Inactive true for a Gorgias ticket's requester. The operator proposes a note on the customer and a tag on the ticket so no further replies go to that address.

    With Postmark, Gorgias

  • Tag vendor mail so it leaves the queue

    Invoices and shipping notices from vendor domains you listed arrive as Zendesk tickets. The operator proposes a vendor tag and solved status; SendGrid spamreport events on your own sends are shown alongside.

    With Zendesk, Twilio SendGrid

Requirements

  • A support connector: Zendesk for suspended tickets, Kustomer for the spam attribute and Spam Filters, or Gorgias for the spam field
  • An email delivery connector with bounce events: Postmark or Twilio SendGrid
  • A directory connector for internal senders: Google Workspace
  • Your own list of vendor and notification domains, since no support tool publishes one
Authentication
Uses the credentials of the support, email delivery, and directory connectors you attach. It holds none of its own and closes nothing unapproved.

Limits

  • Zendesk's cause on a suspended ticket is read-only. The operator reads why a ticket was suspended and cannot change the filter that did it
  • Zendesk deletes a suspended ticket after 14 days if no one reviews it. Recovery is proposed inside that window or not at all
  • Kustomer's block list holds email addresses and wildcard domains. Marking a chat or social conversation as spam does not block that sender
  • A bounce belongs to one address. A customer with a second address is still reachable, and the operator says so rather than closing the case

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 Noise Filter ↗

Questions and answers

What does an agent approve?
A batch, one line per item: the sender, the kind the operator assigned, the evidence (a bounce Type, a Zendesk cause, a directory match), and the proposed action. The agent approves the batch or removes lines from it. Nothing is closed, tagged, or blocked before that.
What is recorded for each item?
Each item keeps its kind as a tag and a note naming the evidence. Block list additions are recorded with the sender, who approved, and when. A recovered ticket carries a note saying it was recovered from suspension and why.
Does it delete anything on its own?
No. It proposes closes, tags, block list entries, and recoveries. It never proposes deleting a suspended ticket, and it never sends a reply to an address it has classed as a bounce or an auto-reply. A person approves each batch.
Ask about Noise Filter

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