Skip to main content

FluentCRM

#Feature Request

Feature request: support “Transactional” status in Fluent Forms → FluentCRM integrations

Hi FluentCRM / Fluent Forms team,

We found a consent-management gap while building a service lead funnel and wanted to suggest an improvement.

Environment:

  • FluentCRM 3.2.0
  • Fluent Forms 6.2.14
  • Fluent Forms Pro 6.2.14

Use case:

We have a service/contact form where submitting the form is operational and does NOT require consent for promotional marketing.

The form has a separate, optional marketing-consent checkbox.

Desired behavior:

  • New contact without marketing consent → Transactional
  • New contact with explicit marketing consent → Subscribed
  • Existing suppressed contacts should not be automatically reactivated
  • Pending should remain available for double opt-in workflows

FluentCRM already has a Transactional status, which is a good fit for service/operational contacts that should receive necessary communications but should not receive promotional campaigns.

Current limitation:

In the Fluent Forms → FluentCRM “New Form Submission” automation trigger, the available subscription-status choices do not provide a clean way to create a new contact as Transactional based on the form’s marketing-consent field.

The native Fluent Forms → FluentCRM feed also does not provide conditional status mapping that cleanly handles this use case.

As a result, a service business has to either:

  1. mark a non-consented service lead as Subscribed,
  2. use Pending even when double opt-in is not the intended workflow, or
  3. add custom code to create the contact with the correct Transactional status.

Suggested improvement:

Could FluentCRM/Fluent Forms support:

  • Transactional as an available contact status in the Fluent Forms trigger/feed;

  • conditional status mapping based on a form field, for example:

    • consent_marketing = yes → Subscribed
    • consent_marketing != yes → Transactional;

  • an option such as “Do not change existing contact status” so submitting a service form cannot accidentally change an existing subscription/suppression state.

This would make it much easier to keep service communications separate from promotional consent while using the native Fluent ecosystem.

We reproduced the limitation on the versions listed above and currently need a small custom integration layer to model the consent correctly.

Would this be something you could consider adding to the native Fluent Forms ↔ FluentCRM integration?