Product Support

Contact Button Field

Provides a secure "contact" button for your lists and single record displays.

Product Setup

Start by installing and activating the add-on, making sure you also have installed the Participants Database Email Expansion Kit plugin.

Adding a Contact Button

The first step is to add a new field for your button on the Manage Database Fields page. You can call it “contact” or anything you want. This will add a contact button to your list and/or single record display in the same way that any other field is shown. You can show it with other fields, or show it alone by using the “fields” attribute of the shortcode.

The contact button is always associated with a single Participants Database record.

For instance, if you are showing a list of records that includes the contact button, each button in the list can send an email based on the information in that record: typically, it will be the email address. So, if your list is a list of club members, clicking on the contact button on a member’s listing could send an email to that member. That is only one example, the configuration of the button is very flexible, many other actions are possible.

The text on the button is configured in the add-on’s settings, but it is also possible to individually configure the button in the “values” section of the field definition on the Manage Database Fields page. This is explained in detail below.

What the Button Does

Once you have added your contact button field and configured it to appear in your list and/or single record display, it will show up as a clickable button. When that button is clicked, a contact form appears in an overlay on the page. This form includes an input for their name, email address and the message they want to send. Optionally, the user can enter a subject line.

When the user clicks the “send” button, the email is triggered with the entered information and also the data from the associated record.

reCAPTCHA

If you have Participants Database reCAPTCHA installed, the form will include an “invisible” recaptcha device that will verify that the user is a human.

To configure the reCAPTCHA for this add-on, you must use “invisible” API credentials, the regular reCAPTCHA v2 credentials won’t work.

Go to your reCAPCTCHA developer page. You will see a list of all your API keys. Under “Site Type” you will see if the key you are using is v2 or Invisible. If the keys you are using are v2, you should create a new set of keys (you can’t change existing keys) for your site, and make sure they are the “invisible” type. Use these new keys in the settings for Participants Database reCAPTCHA. The usual reCAPTCHA on your signup forms will continue to work with the new keys.

If you don’t use reCAPTCHA, the contact forms will still work, but they won’t be protected against automated submissions from non-human users. In many cases, this is OK, the contact forms are not easily detected by bots, or perhaps in your case the page with the contact buttons is not public.

Setting Up the Email

When a users submits the contact form, an “email event” is triggered with the submitted data. For that event to actually send an email, you must use an email template that determines what will be in the email, who it goes to, and all that stuff.

Email Template Configuration 1Go to the PDb Email Templates screen and create a new template. Set the Send Action to “Contact Button Email” so that the template will be triggered when the contact form is submitted. Fill out the rest of the template to set up what the content of the email will be and who it will go to.

Using Value Tags

In your template, you can use “value tags” that will be substituted with the values in the form submission. It’s important to understand that the data you will have access to in this template is all the record data from the record that was displayed or clicked on to send the contact email. There will, of course, also be all the information the user entered into the contact form.

To set up a typical contact email where the record the user has selected is the person to whom the contact email is sent, put the participant record email in the Recipient Email space. You can also fill in the Recipient Name with fields from the record as well. (See the screenshot below for what that looks like.)

Information from the contact form uses field names that are prefixed with “pdbcff-” (short for Participants Database Contact Form Field) so that they will not conflict with information from the record. The fields from the contact form that you will be able to use are:

  • pdbcff-sender_name
  • pdbcff-sender_email
  • pdbcff-subject (this is the “Global Subject Line” setting)
  • pdbcff-body
This image shows how a typical contact email template might be configured.

The “Body” of the email template would probably contain only the [pdbcff-body] tag, but you could add other text and use the pdbcff-body tag to place the message from the user in the body of the email.

Of course, this is only a starting point. Your template can easily be customized to your particular needs. You can also use the CC and BCC sections to send duplicate emails to other people. It is also possible to place multiple email templates on the same event if you need different emails to go to several recipients.

Defining the Email Subject

Email subjects are an important way to organize incoming emails for the recipient, and with this add-on you have a lot of flexibility in defining the subject of the email. In the add-on settings is a setting for the email subject line. This setting accepts value tags, so you can construct a subject that includes all the information needed to help manage the incoming emails. This means you can include any information from the record the user clicked on.

If you are allowing the user to enter their own subject, that information is available in the tag [pdbcff-subject]. If that tag is included in your subject line setting, the user’s subject will be shown. It is recommended that you also add text to the subject so that the email can be easily identified as coming from the contact form… for instance:

That way, no matter what subject the user enters, the recipient will know this was a submission from the Participants Database contact form.

In the email template, the [pdbcff-subject] tag will show the Global Subject Line.

example of a configuration where each contact button field uses a different email template. This one is configured to send on a field named “contact”

Using Conditional Sends

The Send on Condition setting can be used to determine if an email template should be used based on the user’s input or data from the record the contact button was attached to.

The typical use for this is if you have more than one contact form. In a setup like that, each contact form field will have a different name. In the conditional setup, one of the fields available is “pdbcff-field” which holds the name of the contact button field that the user clicked on. When you have more than one contact button field, this is how you would attach a different email template to each of your contact button fields.

Field-Specific Configuration Options

Many of this plugin’s configuration settings can be set on a per-field basis by defining the values in the “values” parameter of the contact button field definition on the Manage Database Fields page.

The values are set using the usual syntax for the “values” configuration field. For instance, to set a special title and contact button text, you could use a setting like this:

form_title::Support Request,contact_button::Get Support

Here is the list of options that can be set in the field definition:

  • sender_name_label – labels the “sender_name” input
  • sender_email_label – labels the “sender_email” input
  • message_label – labels the message input
  • subject_label – labels the subject input
  • subject_line – sets the subject of the email
  • placeholder – sets a placeholder text for the message input
  • form_title – sets a title for the form
  • contact_button – text for the contact button
  • submit_button – text for the send button
  • sent_message – text shown after a successful send

These configurations can also contain value tags that will be filled with data from the record…for example:

sent_message::your message has been sent to [first_name] [last_name]

 

F.A.Q.

Can I reposition or hide the Google reCAPTCHA badge?

In the settings, there is a location preference for the badge, but in practice only the “inline” setting is very useful.

You can change the position, size, etc. of the badge when it is in “inline” mode with your own CSS. Be aware that hiding the badge is probably a violation of Google’s terms of use. It may also be a privacy law violation in the EU. Here is a link with some more details on this question.

Can I use the reCAPTCHA without the reCAPTCHA add-on?

Yes, if you use two filters to supply the site key and private key. The filters are:

‘pdbcff-recaptcha_site_key’ for the site key
‘pdbcff-recaptcha_private_key’ for the private key.

If you don’t know how to set up filters, you’re probably better off just using the add-on.

Can I add more fields to the contact form?

Yes, this is possible, you’ll need to have some basic coding ability and a good understanding of HTML form elements.

I’ve written a short tutorial on how to add a phone field to the contact form:

Adding Fields to the Participants Database Contact Form

Support Discussions for Contact Button

Got a Support Question?

You have to agree to the comment policy.