Email Piping for FCRM? Use Case, Thoughts & Request for Feedback

Hey everyone,

I’ve been thinking about this for a long time, and I’d love your feedback (especially from those running service-based businesses).

FCRM has grown a lot, and the recent addition of sending transactional emails directly from the contact profile was a great step.

But here’s the gap:

Those emails still end up as normal SMTP records and we all know those logs must be purged regularly to keep the DB clean.

For consultants, agencies, designers… 90% of client communication lives in email. And what’s missing is a proper, persistent conversation record, similar to what Fluent Support achieves with email piping.

I’m referring to something like:

• Real threaded email history
• Open/close style entries
• Clear timeline of exchanges with a contact
• No need to manually copy/paste emails into Notes (which is error-prone and easy to forget)

Many CRMs (especially B2B-oriented ones) offer this: a unified conversation history that becomes the backbone for follow-up, pipelines, and client management.

In FCRM we currently use the Notes area with toggles like “proposal sent”, “accepted”, “not accepted”, etc. But:

• Notes are not designed for message history
• You can’t filter or distinguish between record types
• It feels like the feature was meant to grow into something bigger—but it hasn’t yet
• Copying an email into a note is… well, not ideal 😅

Email piping in Fluent Support gets close to what would solve this, but using a helpdesk ticketing plugin to emulate CRM communications feels like a workaround, not the real solution.

I’d love to see:

1. Email piping (or similar ingestion) directly into FCRM
2. A true message timeline tied to each contact
3. Better handling of proposals/estimates as first-class CRM objects
4. Integration with the future Pipeline so we get real relationship tracking

We already archive everything independently in our firm, so this isn’t about storage—it’s about workflow.

If FCRM gave more love to transactional email records and the Notes section, it could evolve into a proper client conversation manager instead of a lightweight event log.

Curious to hear how others are handling this.

Anyone using Support + piping as a workaround? Do you feel the same gap?

Looking forward to your thoughts.

cc: Shahjahan Jewel