fluent_support_pro_file_storage_integration_settings

---

This filter hook allows you to retrieve file storage integration settings data and modify it.

Parameters

• '$settings' (array) File storage integration settings data

Usage

add_filter('fluent_support_pro/file_storage_integration_settings_' . $settingsKey, function ($settings) {
    // ...do something
    return $settings;
}, 10, 1);

Note: $settingsKey It contains the file upload driver name, such as Dropbox, Google Drive, etc.

Reference

apply_filters('fluent_support_pro/file_storage_integration_settings_' . $settingsKey, [ 'fieldsConfig' => null, 'settings' => null ])

This filter is located in
fluent-support-pro/app/Http/Controllers/UploadIntegrationController.php

fluent_support_pro_file_storage_integration_settings_save

---

This filter hook allows you to retrieve file upload related message and settings data and modify it.

Parameters

• '$message' (array) Message related to saving file upload settings
• 'settings' (array) Data for saving file upload settings

Usage

add_filter('fluent_support_pro/file_storage_integration_settings_save_' . $settingsKey, 
function($message, $settings) {
    // ...do something
    return $message;
}, 10, 2);

Note: $settingsKey It contains the file upload driver name, such as Dropbox, Google Drive, etc.

Reference

apply_filters('fluent_support_pro/file_storage_integration_settings_save_' . $settingsKey, [ 'message' => __('Sorry, upload driver not found') ], $settings)

This filter is located in
fluent-support-pro/app/Http/Controllers/UploadIntegrationController.php

fluent_support_search_doc_query

---

This filter hook allows you to retrieve the search query used for document and modify it.

Parameters

• '$search' (string) Search query used for document

Usage

add_filter('fluent_support/search_doc_query', function($search) {
    // ...do something
    return $search;
}, 10, 1);

Reference

apply_filters('fluent_support/search_doc_query', $search)

This filter is located in
fluent-support-pro/app/Http/Controllers/DocSuggestionController.php

fluent_support_search_doc_post_types

---

This filter hook allows you to retrieve the document types data and modify it.

Parameters

• '$docsPostType' (array) Document types

Usage

add_filter('fluent_support/search_doc_post_types', function($docsPostType) {
    // ...do something
    return $docsPostType;
}, 10, 1);

Reference

apply_filters('fluent_support/search_doc_post_types', $ticketConfig['docs_post_types'])

This filter is located in
fluent-support-pro/app/Http/Controllers/DocSuggestionController.php

fluent_support_doc_search_args

---

This filter hook allows you to retrieve the document search arguments and modify it.

Parameters

• '$searchArgs' (array) Document search arguments

Usage

add_filter('fluent_support/doc_search_args', function($searchArgs) {
    // ...do something
    return $searchArgs;
}, 10, 1);

Reference

apply_filters('fluent_support/doc_search_args', [ 'post_type' => $postTypes, 's' => $search, 'numberposts' => $ticketConfig['post_limits'] ])

This filter is located in
fluent-support-pro/app/Http/Controllers/DocSuggestionController.php

fluent_support_search_doc_result

---

This filter hook allows you to retrieve the document search result and modify it.

Parameters

• '$result' (array) Document search result

Usage

add_filter('fluent_support/search_doc_result', function($result) {
    // ...do something
    return $result;
}, 10, 1);

Reference

apply_filters('fluent_support/search_doc_result', $result)

This filter is located in
fluent-support-pro/app/Http/Controllers/DocSuggestionController.php

fluent_support_pro_email_piping_raw_data

---

This filter hook allows you to retrieve the payload and mailbox data and modify it.

Parameters

• '$data' (array) Payload data
• '$box' (object) Mailbox data

Usage

add_filter('fluent_support_pro/email_piping_raw_data', function($data, $box) {
    // ...do something
    return $data;
}, 10, 2);

Reference

apply_filters('fluent_support_pro/email_piping_raw_data', $data, $box)

This filter is located in
fluent-support-pro/app/Http/Controllers/EmailBoxController.php

fluent_support_pro_email_piping_data

---

This filter hook allows you to retrieve the payload, formatted payload and mailbox data and modify it.

Parameters

• '$formattedData' (array) formatted payload data
• '$data' (array) Payload data
• '$box' (object) Mailbox data

Usage

add_filter('fluent_support_pro/email_piping_data', function($formattedData, $data, $box) {
    // ...do something
    return $formattedData;
}, 10, 3);

Reference

apply_filters('fluent_support_pro/email_piping_data', $formattedData, $data, $box)

This filter is located in
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/ByMailHandler.php

fluent_support_all_doc_post_types

---

This filter hook allows you to retrieve the document post types and modify it.

Parameters

• '$postTypes' (array) Document post types

Usage

add_filter('fluent_support/all_doc_post_types', function($postTypes) {
    // ...do something
    return $postTypes;
}, 10, 1);

Reference

apply_filters('fluent_support/all_doc_post_types', get_post_types([ 'public' => true, 'publicly_queryable' => true ]))

This filter is located in
fluent-support-pro/app/Http/Controllers/TicketFormController.php

fluent_support_custom_field_types

---

This filter hook allows you to retrieve the list of custom field types and modify it.

Parameters

• '$fieldTypes' (array) List of custom field types

Usage

add_filter('fluent_support/custom_field_types', function($fieldTypes) {
    // ...do something
    return $fieldTypes;
}, 10, 1);

Reference

apply_filters('fluent_support/custom_field_types', $fieldTypes)

$fieldTypes is used here as an illustrative variable to represent the raw array value found in the main filter, demonstrating the custom form field types.

This filter is located in
fluent-support/app/Services/Integrations/FluentForm/FeedIntegration.php,
fluent-support-pro/app/Modules/CustomFields/CustomFields.php

fluent_support_render_custom_field_options

---

This filter hook allows you to retrieve the public field, customer data, and modify it..

Parameters

• '$publicField' (array) Public field
• '$customer' (object) Customer data

Usage

add_filter('fluent_support/render_custom_field_options_' . $fieldType['type'], function( $publicField, $customer) {
    // ...do something
    return $publicField;
}, 10, 2);

Note: $fieldType['type'] the type of field, whether it be text,email, user, etc.

Reference

apply_filters('fluent_support/render_custom_field_options_' . $fieldType['type'], $publicField, $customer)

This filter is located in
fluent-support-pro/app/Services/CustomFieldsService.php

fluent_support_custom_field_renders_type

---

This filter hook allows you to retrieve the field types and modify it..

Parameters

• '$fieldTypes' (array) Field types

Usage

add_filter('fluent_support/custom_field_renders_type', function( $fieldTypes) {
    // ...do something
    return $fieldTypes;
}, 10, 1);

Reference

apply_filters('fluent_support/custom_field_renders_type', $fieldTypes)

This filter is located in
fluent-support-pro/app/Services/CustomFieldsService.php

fluent_support_ticket_partial_match

---

This filter hook decides whether a piped email reply may be matched to an existing ticket by part of its subject when no ticket has the exact same title. It is off by default (`false`), because a few shared words would put new questions on old tickets. Return `true` to turn it back on.

When it is on, only subjects of six words or more get a partial match, on their middle three words. The match is limited to the customer's tickets that are not closed, in the same mailbox, and updated in the last 30 days (see fluent_support_pro/email_subject_match_days). New emails that are not replies are never matched by subject.

This filter is available in Fluent Support Pro only.

Parameters

• '$partialMatch' (boolean) Whether to try a partial subject match. Default false

Usage

// Turn partial subject matching back on for piped email replies
add_filter('fluent_support/ticket_partial_match', '__return_true');

Reference

apply_filters('fluent_support/ticket_partial_match', false)

This filter is located in
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/ByMailHandler.php

fluent_support_enable_custom_piping

---

This filter hook allows you to retrieve custom piping permission modify it..

Parameters

• '$enableCustomPiping' (boolean) Enable custom piping or not

Usage

add_filter('fluent_support/enable_custom_piping', function( $enableCustomPiping) {
    // ...do something
    return $enableCustomPiping;
}, 10, 1);

Reference

apply_filters('fluent_support/enable_custom_piping', false)

This filter is located in
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/ByMailHandler.php

fluent_support_slack_api_data

---

This filter hook allows you to retrieve Slack integration settings, message data, and modify them.

Parameters

• '$data' (array) Slack Integration Settings data
• '$message' (array) Data for slack message Usage

add_filter('fluent_support/slack_api_data', function($data, $message) {
    // ...do something
    return $data;
}, 10, 2);

Reference

apply_filters('fluent_support/slack_api_data', $data, $message)

This filter is located in
fluent-support-pro/app/Modules/Chat/Slack.php

fluent_support_advanced_filter_options

---

This filter hook allows you to retrieve the advanced filter options data and modify it.

Parameters

• '$groups' (array) Advanced filter options data

Usage

add_filter('fluent_support/advanced_filter_options', function($groups) {
    // ...do something
    return $groups;
}, 10, 1);

Reference

apply_filters('fluent_support/advanced_filter_options', $groups)

This filter is located in
fluent-support-pro/app/Services/ProHelper.php

fluent_support_outgoing_webhook_data

---

This filter hook allows you to retrieve the outgoing webhook data and modify it.

Parameters

• '$data' (array) Formatted Ticket data
• '$action' (object) Workflow action data
• '$ticket' (object) Ticket data

Usage

add_filter('fluent_support/outgoing_webhook_data', function($data, $action, $ticket) {
    // ...do something
    return $groups;
}, 10, 3);

Reference

apply_filters('fluent_support/outgoing_webhook_data', $data, $action, $this->ticket)

This filter is located in
fluent-support-pro/app/Modules/Workflows/Actions/OutgoingWebhook.php

fluent_support_workflow_ticket_created_supported_conditions

---

This filter hook allows you to retrieve the workflow ticket created supported conditions data and modify it.

Parameters

• '$supportedConditions' (array) Ticket created supported conditions data

Usage

add_filter('fluent_support/workflow_ticket_created_supported_conditions', function($supportedConditions) {
    // ...do something
    return $supportedConditions;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_ticket_created_supported_conditions', $supportedConditions)

$supportedConditions is used here as an illustrative variable to represent the raw array value found in the main filter, demonstrating the ticket created supported conditions data.

This filter is located in
fluent-support-pro/app/Services/Workflow/WorkflowHelper.php

fluent_support_workflow_response_added_by_customer_supported_conditions

---

This filter hook allows you to retrieve the response added by customer supported conditions data and modify it.

Parameters

• '$supportedConditions' (array) Response added by customer supported conditions data

Usage

add_filter('fluent_support/workflow_response_added_by_customer_supported_conditions', function($supportedConditions) {
    // ...do something
    return $supportedConditions;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_response_added_by_customer_supported_conditions', $supportedConditions)

$supportedConditions is used here as an illustrative variable to represent the raw array value found in the main filter, demonstrating the response added by customer supported conditions data.

This filter is located in
fluent-support-pro/app/Services/Workflow/WorkflowHelper.php

fluent_support_workflow_ticket_closed_supported_conditions

---

This filter hook allows you to retrieve the ticket closed supported conditions data and modify it.

Parameters

• '$supportedConditions' (array) Ticket closed supported conditions data

Usage

add_filter('fluent_support/workflow_ticket_closed_supported_conditions', function($supportedConditions) {
    // ...do something
    return $supportedConditions;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_ticket_closed_supported_conditions', $supportedConditions)

$supportedConditions is used here as an illustrative variable to represent the raw array value found in the main filter, demonstrating the ticket closed supported conditions data.

This filter is located in
fluent-support-pro/app/Services/Workflow/WorkflowHelper.php

fluent_support_workflow_ticket_reopen_supported_conditions

---

This filter hook allows you to change the conditions available to the "On Ticket Reopened" workflow trigger (`fluent_support/ticket_reopen`). This filter is available in Fluent Support Pro only.

Parameters

• '$supportedConditions' (array) Condition keys, for example customer.email, ticket.priority, ticket.source, ticket.tags

Usage

add_filter('fluent_support/workflow_ticket_reopen_supported_conditions', function($supportedConditions) {
    // ...do something
    return $supportedConditions;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_ticket_reopen_supported_conditions', $supportedConditions)

This filter is located in
fluent-support-pro/app/Services/Workflow/WorkflowHelper.php

fluent_support_workflow_response_added_by_agent_supported_conditions

---

This filter hook allows you to change the conditions available to the "On Agent Response" workflow trigger (`fluent_support/response_added_by_agent`). This filter is available in Fluent Support Pro only.

Parameters

• '$supportedConditions' (array) Condition keys, for example customer.email, ticket.priority, ticket.source, ticket.tags

Usage

add_filter('fluent_support/workflow_response_added_by_agent_supported_conditions', function($supportedConditions) {
    // ...do something
    return $supportedConditions;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_response_added_by_agent_supported_conditions', $supportedConditions)

This filter is located in
fluent-support-pro/app/Services/Workflow/WorkflowHelper.php

fluent_support_workflow_agent_assigned_to_ticket_supported_conditions

---

This filter hook allows you to change the conditions available to the "On Agent Assigned" workflow trigger (`fluent_support/agent_assigned_to_ticket`). This filter is available in Fluent Support Pro only.

Parameters

• '$supportedConditions' (array) Condition keys, for example customer.email, ticket.priority, ticket.source, ticket.tags

Usage

add_filter('fluent_support/workflow_agent_assigned_to_ticket_supported_conditions', function($supportedConditions) {
    // ...do something
    return $supportedConditions;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_agent_assigned_to_ticket_supported_conditions', $supportedConditions)

This filter is located in
fluent-support-pro/app/Services/Workflow/WorkflowHelper.php

fluent_support_workflow_agent_feedback_received_supported_conditions

---

This filter hook allows you to change the conditions available to the "On Customer Feedback" workflow trigger (`fluent_support/agent_feedback_received`). This filter is available in Fluent Support Pro only.

Parameters

• '$supportedConditions' (array) Condition keys, for example customer.email, ticket.priority, ticket.source, ticket.tags, feedback.rating

Usage

add_filter('fluent_support/workflow_agent_feedback_received_supported_conditions', function($supportedConditions) {
    // ...do something
    return $supportedConditions;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_agent_feedback_received_supported_conditions', $supportedConditions)

This filter is located in
fluent-support-pro/app/Services/Workflow/WorkflowHelper.php

fluent_support_workflow_conditions

---

This filter hook allows you to retrieve the Workflow conditions data and modify it.

Parameters

• '$conditions' (array) Workflow conditions data

Usage

add_filter('fluent_support/workflow_conditions', function($conditions) {
    // ...do something
    return $conditions;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_conditions', $conditions)

This filter is located in
fluent-support-pro/app/Modules/Workflows/Conditions.php

fluent_support_workflow_actions

---

This filter hook allows you to retrieve the Workflow actions data and modify it.

Parameters

• '$actions' (array) Workflow actions data
• '$workFlow' (array) Workflow data

Usage

add_filter('fluent_support/workflow_actions', function($actions, $workFlow) {
    // ...do something
    return $actions;
}, 10, 2);

Reference

apply_filters('fluent_support/workflow_actions', $actions, $workFlow)

This filter is located in
fluent-support-pro/app/Modules/Workflows/WorkflowController.php

fluent_support_workflow_trigger_classes

---

This filter hook allows you to register workflow trigger classes. Each class must extend `FluentSupportPro\App\Modules\Workflows\Triggers\BaseTrigger`; the order is the order shown in the workflow editor. This filter is available in Fluent Support Pro only.

Parameters

• '$classes' (array) Trigger class names

Usage

add_filter('fluent_support/workflow_trigger_classes', function ($classes) {
    // ...do something
    return $classes;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_trigger_classes', [...])

This filter is located in
fluent-support-pro/app/Modules/Workflows/Runner.php

fluent_support_workflow_action_classes

---

This filter hook allows you to register workflow action classes. Each class must extend `FluentSupportPro\App\Modules\Workflows\Actions\BaseAction`; the order is the order shown in the workflow editor. This filter is available in Fluent Support Pro only.

Parameters

• '$classes' (array) Action class names

Usage

add_filter('fluent_support/workflow_action_classes', function ($classes) {
    // ...do something
    return $classes;
}, 10, 1);

Reference

apply_filters('fluent_support/workflow_action_classes', [...])

This filter is located in
fluent-support-pro/app/Modules/Workflows/Runner.php

fluent_support_workflow_condition_matches

---

This filter hook lets you decide whether a single workflow condition row matches. Return `true` or `false` to decide it; return `null` to leave it to the built-in rules. This filter is available in Fluent Support Pro only.

Parameters

• '$matches' (bool|null) null by default
• '$row' (array) The condition row: data_key (provider.property), data_operator, data_value
• '$context' (array) The trigger context: ticket, customer when known, plus trigger-specific data

Usage

add_filter('fluent_support/workflow_condition_matches', function ($matches, $row, $context) {
    // ...do something
    return $matches;
}, 10, 3);

Reference

apply_filters('fluent_support/workflow_condition_matches', null, $row, $context)

This filter is located in
fluent-support-pro/app/Modules/Workflows/Conditions.php

fluent_support_ticket_full_match

---

This filter hook allows you to enable or disable exact-subject ticket matching when piping in a reply-by-email message, alongside the existing `fluent_support/ticket_partial_match` filter.

Parameters

• $fullMatch (boolean) Whether to attempt a full-subject match — default true

Usage

add_filter('fluent_support/ticket_full_match', function ($fullMatch) {
    return false;
}, 10, 1);

Reference

apply_filters('fluent_support/ticket_full_match', true)

This filter is located in
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/ByMailHandler.php

fluent_support_verify_webhook_signature_by_platform

---

This filter hook allows you to override the signature check on an incoming Telegram or Slack webhook before it's processed. `{platform}` is `telegram` or `slack`. The default value is the result of Fluent Support Pro's built-in check: Telegram's `X-Telegram-Bot-Api-Secret-Token` header, or Slack's signing secret (`X-Slack-Signature`). The built-in check passes when no secret is configured. Returning `false` rejects the request with a 403. This filter is available in Fluent Support Pro only.

Parameters

• $verified (boolean) Result of the built-in signature check
• $request (object) The current request, containing the raw webhook payload

Usage

add_filter('fluent_support/verify_webhook_signature_telegram', function ($verified, $request) {
    return $verified && my_verify_telegram_signature($request);
}, 10, 2);

Note: {platform} is the incoming webhook's platform slug (telegram or slack).

Reference

apply_filters('fluent_support/verify_webhook_signature_telegram', $telegram->verifySignature(), $request)
apply_filters('fluent_support/verify_webhook_signature_slack', $slack->verifySignature($request->getContent()), $request)

This filter is located in
fluent-support-pro/app/Modules/Chat/ChatController.php

fluent_support_ai_audit_batch_limit

---

This filter hook allows you to override how many candidate tickets are pulled per batch when generating AI ticket audits (mood/sentiment analysis) for a date range.

Parameters

• $limit (integer) Maximum tickets per audit batch — default 200

Usage

add_filter('fluent_support/ai_audit_batch_limit', function ($limit) {
    return 50;
}, 10, 1);

Reference

apply_filters('fluent_support/ai_audit_batch_limit', 200)

This filter is located in
fluent-support-pro/app/Modules/TicketAudit/AuditController.php

fluent_support_generate_ticket_audit

---

This filter hook allows you to override the AI prompt used to generate a ticket's mood/sentiment audit. The default prompt instructs the AI to return a JSON object with `mood`, `score`, and `summary` fields.

Parameters

• $prompt (string) The default audit prompt sent to the AI provider

Usage

add_filter('fluent_support/generate_ticket_audit', function ($prompt) {
    return $prompt . "\nAlso flag any mention of a refund request.";
}, 10, 1);

Reference

apply_filters('fluent_support/generate_ticket_audit', $prompt)

This filter is located in
fluent-support-pro/app/Modules/TicketAudit/AuditController.php

fluent_support_doc_post_categories

---

This filter hook allows you to modify the list of documentation post categories offered in the "Search Docs" AI settings, alongside `fluent_support/all_doc_post_types`.

Parameters

• $postCategories (array) Hierarchical category options, keyed for a flat select dropdown

Usage

add_filter('fluent_support/doc_post_categories', function ($postCategories) {
    // ...do something
    return $postCategories;
}, 10, 1);

Reference

apply_filters('fluent_support/doc_post_categories', $this->getHierarchicalCategoryOptions())

This filter is located in
fluent-support-pro/app/Http/Controllers/TicketFormController.php

fluent_support_doc_post_categories_limit

---

This filter hook allows you to override how many documentation categories are loaded when building the "Search Docs" category select in settings. This caps query/response cost on sites with very large category taxonomies.

Parameters

• $limit (integer) Maximum categories to load — default 500

Usage

add_filter('fluent_support/doc_post_categories_limit', function ($limit) {
    return 100;
}, 10, 1);

Reference

apply_filters('fluent_support/doc_post_categories_limit', 500)

This filter is located in
fluent-support-pro/app/Http/Controllers/TicketFormController.php

fluent_support_license_grace_period_days

---

This filter hook allows you to override the number of grace-period days allowed after a license check fails to report a value, before Pro features are restricted.

Parameters

• $graceDays (integer) Grace period in days — default 15

Usage

add_filter('fluent_support/license_grace_period_days', function ($graceDays) {
    return 30;
}, 10, 1);

Reference

apply_filters('fluent_support/license_grace_period_days', 15)

This filter is located in
fluent-support-pro/app/Http/Controllers/LicenseController.php

fluent_support_max_webhook_payload_size

---

This filter hook allows you to override the maximum accepted payload size (in bytes) for an incoming email-box webhook, to protect against memory exhaustion from oversized requests.

Parameters

• $maxPayloadSize (integer) Maximum payload size in bytes — default 5242880 (5 MB)

Usage

add_filter('fluent_support/max_webhook_payload_size', function ($maxPayloadSize) {
    return 10 * 1024 * 1024; // 10 MB
}, 10, 1);

Reference

apply_filters('fluent_support/max_webhook_payload_size', 5 * 1024 * 1024)

This filter is located in
fluent-support-pro/app/Http/Controllers/EmailBoxController.php

fluent_support_telegram_request_timeout

---

This filter hook allows you to change the timeout, in seconds, of requests to the Telegram Bot API. Requests are sent inside the request that fired the event, so keep it short. This filter is available in Fluent Support Pro only.

Parameters

• '$timeout' (integer) Timeout in seconds. Default 10

Usage

add_filter('fluent_support/telegram_request_timeout', function ($timeout) {
    return 5;
}, 10, 1);

Reference

apply_filters('fluent_support/telegram_request_timeout', 10)

This filter is located in
fluent-support-pro/app/Modules/Chat/Telegram.php

Email Piping Filters

fluent_support_pro_email_piping_classification

---

This filter hook allows you to change how an incoming piped email is classified before it reaches the ticket flow. This filter is available in Fluent Support Pro only.

• normal: handled as usual.
• automated: machine mail that answers nothing (Auto-Submitted: auto-generated, Precedence: bulk, a mailer-daemon@ sender, an auto-reply-like subject). It goes through the normal flow, but no automatic email is sent back to it.
• auto_reply: an out-of-office or vacation reply. Added as an internal note on the ticket it threads to (sender must be the customer or a CC), otherwise dropped.
• bounce: a delivery failure. Added as an internal note on the ticket whose email bounced, otherwise dropped.

Parameters

• '$kind' (string) normal, automated, auto_reply or bounce
• '$data' (array) Raw pipe payload (headers, subject, bounce, body_text, ...)

Usage

add_filter('fluent_support_pro/email_piping_classification', function ($kind, $data) {
    // Treat our monitoring alerts as normal tickets
    if ($kind === 'automated' && strpos((string) ($data['subject'] ?? ''), '[Monitor]') === 0) {
        return 'normal';
    }
    return $kind;
}, 10, 2);

Reference

apply_filters('fluent_support_pro/email_piping_classification', $kind, $data)

This filter is located in
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/AutoMailHandler.php

fluent_support_pro_auto_reply_guard_max

---

This filter hook allows you to change how many automatic emails (the "ticket created" confirmation, and a workflow reply to a customer's email) may be sent to one customer within a 3-hour window for tickets that came in by email. It stops two autoresponders from looping. Replies an agent writes are never held. This filter is available in Fluent Support Pro only.

Parameters

• '$max' (integer) Maximum automatic emails per window. Default 10
• '$customerId' (integer) Customer ID

Usage

add_filter('fluent_support_pro/auto_reply_guard_max', function ($max, $customerId) {
    return 20;
}, 10, 2);

Reference

apply_filters('fluent_support_pro/auto_reply_guard_max', self::MAX_PER_WINDOW, $customerId)

This filter is located in
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/AutoReplyGuard.php

fluent_support_pro_auto_reply_guard_max_same_subject

---

This filter hook allows you to change how many automatic emails with the same subject may be sent to one customer within the 3-hour window (see `fluent_support_pro/auto_reply_guard_max`). This filter is available in Fluent Support Pro only.

Parameters

• '$max' (integer) Maximum automatic emails per subject per window. Default 2
• '$customerId' (integer) Customer ID

Usage

add_filter('fluent_support_pro/auto_reply_guard_max_same_subject', function ($max, $customerId) {
    return 3;
}, 10, 2);

Reference

apply_filters('fluent_support_pro/auto_reply_guard_max_same_subject', self::MAX_SAME_SUBJECT, $customerId)

This filter is located in
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/AutoReplyGuard.php

fluent_support_pro_email_subject_match_days

---

This filter hook allows you to change how recent a ticket's last activity must be for a piped reply to be matched to it by subject, when the email's threading headers do not identify the ticket. Only emails that look like replies (a `Re:` style prefix or threading headers) are matched by subject. Values below 1 are raised to 1. This filter is available in Fluent Support Pro only.

Parameters

• '$days' (integer) Number of days. Default 30

Usage

add_filter('fluent_support_pro/email_subject_match_days', function ($days) {
    return 14;
}, 10, 1);

Reference

apply_filters('fluent_support_pro/email_subject_match_days', 30)

This filter is located in
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/ByMailHandler.php

fluent_support_pro_email_threading_headers

---

This filter hook decides whether Pro rewrites the `In-Reply-To` and `References` headers of a customer email for a ticket. When on, the email replies to the customer's own latest message and carries a signed ticket reference (`fst.{ticketId}.{sig}@{host}`) so the customer's reply threads back to the ticket through email piping. It runs on `fluent_support/mail_to_customer_header` (priority 20). This filter is available in Fluent Support Pro only.

Parameters

• '$enabled' (boolean) Whether to add threading headers. Default true
• '$ticket' (object) The ticket the email is for
• '$data' (array) The data passed to fluent_support/mail_to_customer_header

Usage

add_filter('fluent_support_pro/email_threading_headers', function ($enabled, $ticket, $data) {
    return $enabled;
}, 10, 3);

Reference

apply_filters('fluent_support_pro/email_threading_headers', true, $ticket, $data)

This filter is located in
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/EmailThreading.php

fluent_support_pro_email_piping_fetch_interval

---

This filter hook allows you to change how often Pro pulls missed piped emails from the piping service (an Action Scheduler job, `fluent_support_pro/fetch_piped_emails`). The default depends on the webhook health: 30 minutes when webhooks are arriving, 5 minutes when the last pull found a missed email or no webhook has arrived yet. The minimum is 60 seconds. Not used when `FLUENTSUPPORT_ENABLE_CUSTOM_PIPE` is defined. This filter is available in Fluent Support Pro only.

Parameters

• '$interval' (integer) Seconds until the next fetch
• '$health' (string) healthy, degraded or unknown

Usage

add_filter('fluent_support_pro/email_piping_fetch_interval', function ($interval, $health) {
    return $health === 'healthy' ? HOUR_IN_SECONDS : $interval;
}, 10, 2);

Reference

apply_filters('fluent_support_pro/email_piping_fetch_interval', $interval, self::getWebhookHealth())

This filter is located in
fluent-support-pro/app/Hooks/Handlers/EmailPipingRetryHandler.php

fluent_support_pro_pipe_feature_sync_budget

---

This filter hook allows you to change how many seconds one scheduled fetch run may spend telling the piping service which features each existing mailbox handles (bounce delivery). Mailboxes left over wait for the next run. This filter is available in Fluent Support Pro only.

Parameters

• '$seconds' (integer|float) Time budget in seconds. Default 15

Usage

add_filter('fluent_support_pro/pipe_feature_sync_budget', function ($seconds) {
    return 5;
}, 10, 1);

Reference

apply_filters('fluent_support_pro/pipe_feature_sync_budget', self::FEATURE_SYNC_BUDGET)

This filter is located in
fluent-support-pro/app/Hooks/Handlers/EmailPipingRetryHandler.php

fluent_support_pro_storage_allow_private_endpoint

---

This filter hook allows an S3-compatible storage endpoint on a private or local address, such as a MinIO server on your own network. By default Fluent Support Pro only accepts an endpoint that resolves to a public address.

Available since Fluent Support Pro 2.4.7.

Parameters

• '$allow' (boolean) Default false
• '$host' (string) The endpoint host

Usage

add_filter('fluent_support_pro/storage_allow_private_endpoint', function ($allow, $host) {
    return $host === 'minio.internal';
}, 10, 2);

Reference

apply_filters('fluent_support_pro/storage_allow_private_endpoint', false, $host)

This filter is located in
fluent-support-pro/app/Services/FileUploadIntegration/S3Compatible/S3CompatibleDriver.php

fluent_support_pro_storage_stream_threshold

---

This filter hook allows you to change the file size above which Fluent Support Pro streams an upload from disk with cURL. Smaller files go through `wp_remote_request()` and follow your WordPress HTTP settings. Streaming keeps large uploads out of memory.

Available since Fluent Support Pro 2.4.7.

Parameters

• '$bytes' (integer) Threshold in bytes. Default 16 * MB_IN_BYTES

Usage

add_filter('fluent_support_pro/storage_stream_threshold', function ($bytes) {
    return 8 * MB_IN_BYTES;
}, 10, 1);

Reference

apply_filters('fluent_support_pro/storage_stream_threshold', 16 * MB_IN_BYTES)

This filter is located in
fluent-support-pro/app/Services/FileUploadIntegration/Support/Http.php

Scheduled Reply Filters

fluent_support_scheduled_reply_max_days

---

This filter hook sets how many days ahead a reply can be scheduled (since 2.5.0). This filter is available in Fluent Support Pro only.

Parameters

• '$maxDays' (int) Maximum days ahead. Default 90

Usage

add_filter('fluent_support/scheduled_reply_max_days', function ($maxDays) {
    // ...do something
    return $maxDays;
}, 10, 1);

Reference

apply_filters('fluent_support/scheduled_reply_max_days', 90)

This filter is located in
fluent-support-pro/app/Modules/ScheduledReplies/ScheduledReplyService.php

fluent_support_remote_portal_ssl_verify

---

This filter hook sets whether the remote site's SSL certificate is verified for Remote Portal requests. The default is `true`, except on a site marked as local or development (`WP_ENVIRONMENT_TYPE`). This filter is available in Fluent Support Pro only.

Parameters

• '$verify' (bool) Whether to verify the certificate
• '$url' (string) The remote URL being requested

Usage

add_filter('fluent_support/remote_portal_ssl_verify', function ($verify, $url) {
    // ...do something
    return $verify;
}, 10, 2);

Reference

apply_filters('fluent_support/remote_portal_ssl_verify', $verify, $url)

This filter is located in
fluent-support-pro/app/Modules/RemotePortal/RemoteSiteClient.php