Business Problem:

Currently, custom fields in respond.io are stored at the contact level. For businesses managing multiple sales opportunities with the same customer, values such as quotation amount, project timeline, or product interest can overwrite each other across conversations.

This makes it difficult to track separate opportunities accurately.

Desired Outcome:

Allow custom fields to be stored at the conversation or opportunity level instead of only the contact level.

This would let each conversation maintain its own sales data, follow-up details, and opportunity information without affecting other conversations with the same customer.