Gravity Forms
+ Entry Conversations

Turn a Gravity Forms form into a lightweight request inbox. The Gravity Forms Entry Conversations add-on puts a reply box on the entry detail screen so you can answer the person who submitted the form — and when they reply to your email, their answer threads back onto the same entry as the next message in the conversation. It is not a one-way admin note and it never creates a new entry: the whole back-and-forth lives on the one entry, in order.

Every outbound reply sets a per-entry Reply-To address (a secret plus-tag such as conversations+1842+…@yourdomain.com) together with Message-ID and References headers, so the customer's mail client threads the exchange and their reply lands back on the right entry. The add-on reads that reply from either your own mailbox over IMAP, checked on a schedule by WordPress cron, or an inbound-email webhook you point at it from Mailgun, Postmark, SendGrid or any JSON / raw-email sender. Both paths use your own mailbox or route — there is no third-party helpdesk to sign up for and no CRM to sync to. This is the same self-serve inbound model as the Gravity Forms Email to Entry add-on.

Each entry carries a status that flips on its own — waiting on the customer after you reply, waiting on us after they reply — so you can see at a glance which requests still need you. A conversation history timeline shows who said what and when, inbound replies have their quoted text and signatures trimmed to the new message, and reusable reply templates with Gravity Forms merge tags let you answer common questions in a click. Mailbox passwords and webhook signing keys are stored encrypted at rest. For Gravity Forms 2.9 and newer.

When you send a reply from an entry, the add-on emails the submitter and sets the Reply-To to a per-entry plus-tag address built from your conversation address, together with a Message-ID and References headers. It records the message in the entry's conversation history and flips the entry's status to waiting on the customer. When the submitter replies, their email reaches your site either because WordPress cron reads it from your IMAP mailbox, or because your email service posts it to the secret inbound webhook address. The add-on reads the entry id and the 160-bit token from the plus-tag in the recipient address (falling back to the References / In-Reply-To headers if the plus-tag was stripped), verifies the token, trims the quoted earlier conversation and the signature, appends the message to the same entry's history and flips the status to waiting on us — it never creates a new entry. Auto-replies and out-of-office messages are ignored, and duplicates are skipped. Mailbox passwords and webhook signing keys are encrypted at rest, and the add-on makes no outside HTTP request beyond the mailbox or webhook you configure.