Gabriel Cséfalvay

Contact forms will remember user input. When the user types some input into a form, it’ll be saved automatically. When the user opens the same page again, the previous input will be pre-filled in the form. Returning clients and registrees won’t have to type again. The data is stored locally in the user’s browser and it never leaves their device.
What data is remembered and recalled:
<ul>
<li>Text inputs – all kinds, incl. telephone numbers, e-mail addresses</li>
<li>Checkbox states</li>
<li>Radio button states</li>
<li>Dropdown selects’ states</li>
</ul>
Configuration options:
<ul>
<li>Automatic data privacy infobox.</li>
<li>Include/exclude individual fields by their tag name,</li>
<li>Include/exclude pages by URL,</li>
<li>Temporary disable,</li>
<li>Clear settings from database.</li>
</ul>
So far tested with:
<ul>
<li>Contact Form 7</li>
<li>WPForms*</li>
</ul>
*In WPForms, only the standard style dropdown is supported.
More coming soon. Other plugins are likely to work, too.
This plugin was just released, and I’d like to enhance it. Let me know about any ideas or bugs. If you have a problem or a request, open a new topic here: https://wordpress.org/support/plugin/formmemory/
Love.

FormMemory

Let your contact forms remember and pre-fill previous user input, so clients don't have to type again. So far tested with Contact Form 7 and WPFo …

AlertWire

AlertWire is a system for centralized administration of alert/messaging for multiple sites.
Once your site has been configured in the AlertWire system, you can add this plug-in and set the data-token to enabled the checking of alerts. When the 
page is rendered, a <code><script></code> tag will be inserted into the document being rendered.
How AlertWire Works
<ol>
<li>The page is generated with the correct API server and <code>data-token</code> configured, typically added to the bottom of the page <code>body</code> tag.</li>
<li>An async script tag is executed (late as possible) which loads a small (<4K) javascript plug-in. This plug-in has no dependancies and will 
not interfere with any existing frameworks like jQuery</li>
<li>A cross-domain JSON request is made to the AlertWire API service to determine if there are any active alerts for the <code>data-token</code> specified.</li>
<li>If there are one or more alerts to view, a CSS style-sheet will also be loaded from the API server.</li>
<li>The alerts are then generated dynamically into the document and styled automatically. There are several formats that are rendered 
differently (e.g. page-top, lightbox, etc.).</li>
<li>Tracking pixels are generated to record when a check-in for alerts cccurs and when a view or close or click-through of an alert occurs.</li>
</ol>
Notes
<ul>
<li>The javascript plug-in and CSS style-sheet are publically cached from a CDN and are very small, the impact on load times should be tiny.</li>
<li>The CSS file is only loaded if there are alerts to be rendered.</li>
<li>The javascript plug-in only introduces one symbol into the global scope, the AlertWire module. All other functionality is behind that scope.</li>
<li>The plug-in will set a cookie when a user closes an alert to ensure it isn’t displayed again. Depending on the alert type, this cookie may be a 
session cookie or a durable cookie with a 1 year expiration.</li>
<li>A very small font file will be downloaded for the alert icons the first time an alert is displayed to an end user.</li>
</ul>

AlertWire plug-in to easily insert script tag for AlertWire client sites.

FormMemory vs AlertWire