Examples & Recipes

This guide brings together common Nelx JFB Email Templates setups without repeating the full instructions from each feature guide.

Use the recipe that is closest to what you are building, then follow the linked guide when you need the complete configuration.

The field names below are examples. Replace them with the actual field names used by your JetFormBuilder form.

1. Simple Form Confirmation #

Goal #

Send a clear confirmation to the person who submitted a form.

Assume the form contains:

• first_name
• email
• message

Recipient #

Use Standard and insert:

{email}

Subject #

We received your message, {first_name}

Email Content #

Hello {first_name},

Thank you for getting in touch.

We have received your message and will respond as soon as possible.

Your message

{message}

This is a good first template because it uses only normal form-field placeholders.

See Creating Your First Email Template and Dynamic Content, Placeholders & Macros.

---

2. Confirmation for a Post Created by the Form #

Goal #

Send the submitter a link to a post created by JetFormBuilder.

Email Content #

Hello {first_name},

Your submission has been created successfully.

Reference: #{post_id:inserted}
Title: {post_title:inserted}

[button:{post_url:inserted}]View Submission[/button]

Use this when the same form submission creates a WordPress post.

The inserted-post placeholders become available from that workflow.

See Dynamic Content, Placeholders & Macros for {post_id:inserted}, {post_title:inserted}, and {post_url:inserted}.

---

3. Route Enquiries to Different Departments #

Goal #

Send Sales enquiries to one group and Support enquiries to another.

Assume the form has:

department

with values such as:

sales
support

Default Recipients #

Set a normal fallback recipient first.

For example:

admin@example.com

Sales Condition #

Set:

• Field: department
• Operator: Equals
• Value: sales

Then configure the Sales recipients.

Support Condition #

Add a second condition:

• Field: department
• Operator: Equals
• Value: support

Then configure the Support recipients.

Conditions are checked from top to bottom and the first matching group is used.

If neither condition matches, the default recipient remains available as the fallback.

See Conditional Recipients & Routing Rules.

---

4. Rotate New Leads Between Staff #

Goal #

Assign each new lead to one staff member at a time.

Recipient Setup #

Choose a recipient pool such as a WordPress role or selected user IDs.

Turn on:

Enable Rotation

Each new submission is sent to the next available recipient in the rotation cycle.

Save the Assignee #

If the form creates a Lead post and you need the assigned user later, enable:

Store Rotation User in Post Meta

Use:

{post_id:inserted}

as the post ID, then enter the assignee meta field used by your Lead post type.

For example:

assigned_staff_id

The selected user’s ID is then available for listings, queries, later workflow steps, or reporting.

See Round-Robin Rotation & Assignment Tracking.

---

5. Support Ticket Conversation With Smart Recipient #

Goal #

Route replies between the person who created a ticket and the staff member assigned to it.

Turn on:

Smart Recipient

Provide the assignee ID from your ticket workflow.

Subject #

Re: Support Ticket #{post_id:inserted}

Email Content #

Hello recipient:name,

currentuser:displayname has added a reply to the ticket.

{reply_message}

[button:{post_url:inserted}]View Ticket[/button]

Smart Recipient determines who should receive the message from the current conversation context.

Do not combine Smart Recipient with Conditional Recipients on the same template.

See Smart Recipient & Conversation Routing.

---

6. Event Registration With Dates and Term Labels #

Goal #

Send a readable event confirmation when the form stores dates, times, and a term ID.

Assume the form contains:

• event_type
• event_date
• event_time

Email Content #

Hello {first_name},

Thank you for registering.

Event: {event_type:term}
Date: {event_date:date}
Time: {event_time:time}

The :term format displays the term label instead of its ID.

The date and time formats use the site’s WordPress date/time settings.

See Dynamic Content, Placeholders & Macros.

---

7. Show Clean Labels Instead of Raw Option Values #

Goal #

Avoid values such as:

private_limited

appearing in a customer-facing email.

JetEngine Glossary #

If company_type gets its options from glossary 84:

{company_type:glossary|84}

Manually Entered Options #

If experience_level uses options entered directly into the form:

{experience_level:options}

Example #

Company: {company_name}
Company Type: {company_type:glossary|84}
Experience Level: {experience_level:options}

See Dynamic Content, Placeholders & Macros.

---

8. Order Confirmation With a Repeater #

Goal #

Display several submitted order rows without building an HTML table by hand.

Assume the Repeater Field is:

order_items

and it contains:

• product_name
• product_type
• quantity
• shipping_method

product_type uses glossary 45 and shipping_method uses manually entered options.

Use:

{order_items|product_type:glossary|45,shipping_method:options}

Email Content #

Hello {customer_name},

Thank you for your order.

{order_items|product_type:glossary|45,shipping_method:options}

Total: {order_total}

[button:{order_tracking_url}]Track Your Order[/button]

The repeater is rendered as a table on larger screens and cards on smaller screens.

See Repeater Fields in Email Templates.

---

9. Attach Supporting Documents #

Goal #

Send files uploaded with a form together with the email.

Suppose the form has:

supporting_document

Add that field under the template’s File Attachments setting.

If the Media Field is inside a Repeater, select the Repeater Field rather than only the nested Media Field.

If Modern Media Upload is enabled, the frontend upload experience changes, but the email template still decides which upload fields should become email attachments.

See File Attachments & Secure Documents and Modern Media Upload.

---

10. Send an Email and an In-App Notification #

Goal #

Notify an assigned staff member by both email and the Nelx Notification System.

Assume the form creates a task post.

Email #

Subject: New task – {post_title:inserted}

Hello recipient:first-name,

A new task has been assigned to you.

[button:{post_url:inserted}]View Task[/button]

Notification #

Enable:

Create notifications for recipients

Then use:

Event Type

task

Notification Message Content

A new task "{post_title:inserted}" has been assigned to you.

Notification URL Content

{post_url:inserted}

The email and notification follow the same recipient workflow.

See Nelx Notification System Integration.

---

11. Use a CCT Item to Find the Recipient #

Goal #

Send an email to a user stored in a JetEngine CCT item.

Choose:

CCT Item

as the Recipient Type.

Provide the CCT Item ID and CCT Slug, then load the CCT fields.

If the CCT author should receive the email, keep the normal author recipient behavior.

If another CCT field stores the intended user, enable custom recipients and insert that field.

For example:

[assigned_staff_id]

Email Content #

Hello [client_name],

Quote [quote_number] has been updated.

Expiry: [expiry_date:date]

See CCT Recipients & CCT Placeholders for the complete setup.

---

12. Assign a JetAppointments Provider and Create the Relation #

Goal #

Assign a service request to one provider and connect the new Services post to that provider’s Service Provider post.

Recipient Workflow #

Use a provider recipient pool and enable Rotation if only one provider should be selected for each submission.

Connect Relation #

Enable:

Connect Relation

Then configure:

• Service Providers Post Type Slug;
• Service Provider ID Field;
• Unique Identifier Key;
• Services Post ID.

If the form creates the Services post, use:

{post_id:inserted}

for Services Post ID.

The selected recipient is used to find the matching Service Provider post before the relation is stored.

See Connect Relation for JetAppointments and Round-Robin Rotation & Assignment Tracking.

---

13. Use a Styled Notice and Button #

Goal #

Highlight an important section without writing custom email HTML.

Create a Section Style named:

Important Notice

Then use its generated macro around the relevant content.

For example:

%important-notice%

Please review the request before the deadline.

[button:{post_url:inserted}]Review Request[/button]

%/important-notice%

The section styling belongs to that template.

The button appearance comes from Email Branding.

See Template Styling: Message Boxes, Sections & Buttons.

---

Choosing the Right Feature #

You want to…	Start with…
Send a simple email	Creating Your First Email Template
Choose recipients	Recipients & Delivery Options
Route by form answers	Conditional Recipients & Routing Rules
Distribute submissions one user at a time	Round-Robin Rotation & Assignment Tracking
Route ticket replies	Smart Recipient & Conversation Routing
Read a recipient from a CCT	CCT Recipients & CCT Placeholders
Insert form/post/user data into the email	Dynamic Content, Placeholders & Macros
Display Repeaters	Repeater Fields in Email Templates
Attach uploads	File Attachments & Secure Documents
Change the frontend Media Field experience	Modern Media Upload
Change standard form-field appearance	Modern Form Fields
Add an in-app notification	Nelx Notification System Integration
Link a JetAppointments service to its provider	Connect Relation for JetAppointments

Keep the Recipe Simple First #

When a workflow uses several advanced features, build it in stages.

For example, if you need:

• Conditional Recipients;
• Rotation;
• post-meta assignment;
• notifications;
• Connect Relation;

start by confirming that the correct recipient receives the email.

Then add Rotation.

Then confirm the stored assignee.

Then enable the notification.

Finally, add Connect Relation.

Testing one part at a time makes it much easier to see which setting needs attention if the final workflow does not behave as expected.