SupportCandy Email Marketing Tools Integration - WordPress Plugin

How to Configure SupportCandy Email Marketing Tools Integration for Ticket-Based Subscriptions

SupportCandy Email Marketing Tools Integration is not meant for sending email campaigns from WordPress. Its job is to pass contacts cleanly from SupportCandy to an external email marketing service. In this guide, we will walk through how to prepare your support portal, where to enable the subscription option, how to choose Mailchimp, GetResponse, or Brevo, what to verify in your audience and tags, and how to confirm that a contact actually landed where it should.

This guide is written for a site owner, support administrator, or marketer who already uses SupportCandy as a ticketing system and wants to connect support with follow-up communication. We will not cover purchasing, license keys, or activation workarounds. What matters here is working configuration, user consent, result verification, and troubleshooting cases where the subscription does not appear in the email service.

Keep one core principle in mind from the start: a support contact should never be turned into a subscriber without clear consent and a verifiable setup. This integration saves time, but it does not replace your data processing policy, a clean list structure, or a proper test scenario before going live.

What this integration actually does and where it is most useful

Core SupportCandy handles support operations: ticket forms, the customer portal, conversation lists, agent roles, notifications, and ticket history. An email marketing service solves a different problem: it stores audiences, segments, tags, subscription statuses, and campaigns. SupportCandy Email Marketing Tools Integration connects those two layers at the moment when a user registers in the support portal or creates a new ticket.

The practical value is straightforward: if someone explicitly opts in to receive useful content, you do not need to move that contact into Mailchimp, GetResponse, or Brevo by hand. The administrator selects a service, an audience or list, chooses where the subscription option appears, and adds tags. After that, the contact can go straight into the right marketing database with context attached, for example as a support customer, product user, training participant, or visitor who reached out with a pre-sales question.

This integration is especially useful on sites where support is closely tied to education and retention:

• A product website where users benefit from receiving guides, updates, and educational emails after contacting support.
• A digital products portal where support questions help reveal a user's interest in a specific topic.
• A service business that wants to keep support customers separate from regular blog subscribers.
• An education-focused project where tickets are often related to courses, access, materials, and reminders.
• An online store or membership site where support requests can be gently connected to follow-up email content, but only if the user agreed to it.

It is important not to overestimate what this add-on does. It does not build advanced automations inside WordPress, it does not replace an email editor, and it should not be your only consent management tool. Its real strength is instantly moving a consenting user from the support flow into the selected audience. Everything after that is configured inside Mailchimp, GetResponse, or Brevo.

Who this plugin is a good fit for

SupportCandy Email Marketing Tools Integration is a strong fit for teams that already run support through SupportCandy and do not want to place a separate newsletter form next to the ticket form. If the user is already registering or submitting a request, it makes sense to offer an opt-in in the same place, but without pressure and without hidden consent.

The plugin is also useful for teams where support and marketing work closely together. Agents do not need to export email addresses manually, the marketer gets a cleaner audience, and the administrator can use tags for follow-up segmentation. For example, one tag can identify registered users, another can mark people who created their first ticket, and a third can separate customers who came in through a specific support page.

Who should consider a different approach

If you need a full email marketing hub inside WordPress, with a visual email builder, automated sequences, forms, analytics, and built-in CRM logic, you should look at a dedicated marketing plugin instead. The SupportCandy add-on handles the narrow task of passing a contact along, not the entire email marketing workflow.

It may also be unnecessary if you do not use registration, do not show a public ticket form, or are not ready to handle subscription consent properly from a legal standpoint. In that case, the support page, privacy policy, and subscription flow need to be cleaned up first. Only after that does it make sense to connect the integration.

What to verify before installing it on a live site

Do not start with the Activate button. This integration depends on several things being in place: a working SupportCandy setup, properly configured portal pages, a selected email marketing service, an audience or list, an API key, and clear consent text. If you skip this stage, troubleshooting later becomes murky: you will not know whether the setting failed to save, the API request failed, the user never saw the checkbox, or the contact simply went into a confirmation-pending state.

Check your core SupportCandy setup

First, make sure the support portal itself works. On a typical site, there is usually a page with the [supportcandy] shortcode, and a separate new ticket form may use [wpsc_create_ticket]. If SupportCandy does not know which page is your support page or custom new ticket page, the integration may be enabled but the user will never see the subscription option where it matters.

A practical check is simple: open the support page as a regular user, create a test ticket, make sure the support email is sent, and confirm that the ticket appears in the admin panel. If you use a separate new ticket page, verify its URL in the SupportCandy page settings. If you use a custom registration page, confirm that the registration flow is actually tied to SupportCandy and not just a standard WordPress form.

Review registration, guest tickets, and consent

The official SupportCandy documentation shows several registration options: the built-in form, standard WordPress registration, and a custom URL. This matters for the integration because the add-on can show the subscription option on the registration page, on the create new ticket page, or in both places. If registration is disabled but the opt-in is only shown on the registration page, the user will never see it.

Guest tickets need separate attention. SupportCandy allows guest ticket creation, but that mode is not necessarily enabled by default. For marketing opt-ins, that means a contact may come from a form without a full user account. Check which fields are available to guests, how consent is presented, whether OTP access is sent for ticket access, and whether you are accidentally treating a guest email as if it belonged to a registered user.

Pre-launch check: create one test ticket as a registered user and one guest ticket if guest mode is enabled. Compare where the subscription checkbox appears, which email addresses are sent to the email service, and which tags are applied.

Prepare the audience, list, and tags in your email service

In Mailchimp, the main entity is called an audience, although the API and documentation also use the term lists in nearby contexts. In GetResponse, a contact list is typically the main container, and tags are used for segmentation and later filtering. In Brevo, a contact can be added to lists, while extra data depends on which attributes already exist in the account. For a SupportCandy administrator, this means one thing: you cannot select an audience that does not exist yet, and you cannot treat tags as a substitute for consent.

Set up a clear structure before connecting anything. For example, you might use one audience for all support users and separate tags for registrations, new tickets, product type, or traffic source. Do not create a new list for every tiny scenario if your email platform works better with tags. But do not dump everyone into one stream with no source markers either, or your marketer will not be able to tell the difference between someone who subscribed on the blog and a customer who checked the box during a support request.

Installation and the first check in WordPress

SupportCandy Email Marketing Tools Integration is an add-on for SupportCandy, so you need to start with the core plugin and its working pages. If SupportCandy is not installed yet, install it first through the WordPress plugin directory or by uploading the ZIP file, activate it, and create the support page. Only then does it make sense to add the email marketing integration.

In a normal workflow, there are three steps: install the add-on, confirm that the Email Marketing Tool section appears in the admin panel, and then connect the specific service. Do not enter API keys on a local copy if other developers can access it or if it may end up in a public repository. API keys are secrets. They should not be shared in plain-text task descriptions, unnecessary tickets, or external content generators.

A safe installation order

1. Back up the site, or at least make sure you have a current backup of both files and the database.
2. Update core SupportCandy to a version that is compatible with your add-ons, but test that on a staging copy first if the site is business-critical.
3. Make sure the server meets the minimum WordPress and PHP requirements listed on the product page.
4. Install the add-on ZIP file through Plugins and activate it.
5. Open Support → Settings → Email Marketing Tool and confirm that the section is available to the administrator.
6. Do not enable every subscription display option right away. Start with one service and one test scenario.

After activation, do not rush into sending real data. Create a test audience or a separate test tag in your email service first. That lets you see which contacts are created, what subscriber status they get, how tags are applied, and whether the service introduces any delay.

What counts as a successful initial check

A successful installation is not the same thing as a successful integration. Installation means WordPress activated the add-on without a critical error. The integration is only working when you can complete the full path: show the checkbox to the user, submit the form, see the contact in the selected audience, and verify the tag or list.

If the settings section does not appear after activation, first check the permissions of the current user and whether core SupportCandy is active. If the section appears but the service list is empty or the settings do not save, disable aggressive admin-side caching, check the browser console, and make sure no other plugins are blocking WordPress admin requests.

Choosing between Mailchimp, GetResponse, and Brevo without unnecessary confusion

The official product page and documentation list three supported options: Mailchimp, GetResponse, and Brevo. The choice here is not about which platform is better overall. It is about where your contact database already lives, how your lists are structured, how you use tags, and what kind of subscription confirmation model you want.

Mailchimp: audience, status, and tags

Mailchimp is built around the audience and the contacts inside it. In the API, the subscription status is important when adding a contact: the contact may be added immediately as subscribed or placed into a confirmation-pending state as pending if the workflow uses confirmation. In SupportCandy settings for Mailchimp, you will see API Key, Audience, Default Subscriber Status, and Subscriber Tags.

In practice, Mailchimp is the right choice if your team already runs campaigns there and understands the difference between an audience, a tag, and a contact status. For support-related workflows, tags are especially helpful: for example, support-registration, new-ticket, or product-question. But do not use tags as your only proof of consent. Consent should be visible in the form and reflected in the site's policy.

GetResponse: contact lists and tags for segmentation

The SupportCandy documentation for GetResponse lists API Key, Audience, and Subscriber Tags. In GetResponse, lists act as containers for contacts, while tags and scoring help segment the audience. That is useful if you manage several product lines and want to send different educational sequences to users who came in through support.

Before connecting GetResponse, create a separate list or choose an existing one where the contact source is clear. If the database is large, it is better to start with a test tag instead of immediately connecting a production email sequence. That way, you can see how new contacts from SupportCandy appear in the list and only enable follow-up automations after you verify the setup.

Brevo: lists, attributes, and the API key

The SupportCandy documentation for Brevo lists API Key and Audience. In Brevo's own API documentation, contacts can be created and updated through the contacts endpoint, while list membership is defined through list IDs. Brevo also uses contact attributes, but those attributes must already exist in the account or extra values may simply be ignored.

For SupportCandy, this means you should not expect the add-on to map every ticket field into Brevo unless that capability is explicitly confirmed in the product documentation. The reliable workflow is to send the email into the selected list and then handle segmentation inside Brevo using the tools that are actually available in your account.

If you are still unsure which service to choose, do not try to resolve that inside SupportCandy. Choose your email platform first as a marketing system, then connect the add-on as a support contact source.

Detailed setup after installation

The most important settings section is located at Support → Settings → Email Marketing Tool. The SupportCandy documentation describes a general section plus Mailchimp, GetResponse, and Brevo. Start with General, because that is where you define which service is used and where the user will see the subscription option.

Connection: choose one working service

In the connection area, choose the service that will receive contacts. Do not try to design several independent destinations at once unless your add-on documentation explicitly confirms simultaneous delivery to multiple platforms. For the first launch, use one service, one audience, and one clear tag. That makes verification easier and reduces the risk of sending contacts to the wrong database by mistake.

After selecting the service, move to the corresponding tab or menu. In Mailchimp, enter the API Key, choose the Audience, set the Default Subscriber Status, and add Subscriber Tags. In GetResponse, enter the API Key, choose the Audience, and add tags. In Brevo, enter the API Key and choose the Audience. If the audience list does not appear after entering the key, check the key itself and the account permissions in the email platform before you start looking for a WordPress-side problem.

How to handle API keys

An API key gives an external application access to operations inside your email service. Treat it like a secret: do not send it in public tickets, do not paste it into notes for contractors, do not leave it in screenshots, and do not pass it to an article generator. If the key is ever exposed, revoke it in the email service and create a new one.

For testing, it is better to use a separate API key if the service allows that, or at least a separate test audience. On a live site, do not swap the key while support requests are actively coming in, or some users may submit the form at the exact moment when the integration can no longer connect to the service.

Subscription Options: where to show the opt-in

In the general integration settings, you can choose where the user sees the subscription option: on the registration page, on the create new ticket page, or in both places. The choice should match the real user journey, not an attempt to collect more email addresses.

If the site is built around a closed portal where the user registers first, it makes sense to start with registration. If users often create requests without an account or the ticket form is used like a contact form, test the create new ticket page option first. If you enable both locations, make sure the consent text does not conflict and that the user does not see two different promises in one flow.

A typical setup for different sites

• Product site with a customer portal: Show the opt-in during registration and add a tag that identifies portal users.
• Support site without required registration: Show the opt-in in the new ticket form, especially if guest tickets are enabled.
• Site with a separate marketing subscription in the blog: Do not reuse the same wording. The SupportCandy opt-in should explain what the user will receive specifically after contacting support.
• Site with sensitive support requests: Align the wording with your data policy first and do not enable automatic subscription without an explicit user choice.

Audience and tags: how to avoid wrecking segmentation

The audience or list is where the contact goes. The tag is what helps you understand the source and scenario later. One bad practice is sending all support users into a shared database with no tags. The opposite extreme is creating so many tags that no one actually uses them. A good structure is usually simpler: one list for support opt-ins and 2 to 4 tags that genuinely matter.

Here is a sensible example structure:

• support-portal - the user registered through the support portal.
• support-ticket - the contact was created after a ticket submission.
• product-help - the contact is related to product education materials.
• trial-question - the user is asking questions before testing or implementation.

Do not put personal data, problem descriptions, order numbers, or other sensitive ticket information into tags. A tag should be a category, not a copy of the ticket content. That is safer and far more useful for marketing.

Consent text and nearby SupportCandy settings

The integration works alongside the Terms and Conditions and GDPR settings in SupportCandy. Those settings do not replace the subscription checkbox, but they help explain what data is stored and under what conditions the user submits the form. If the site serves users in regions with strict consent requirements, do not rely on a technical checkbox as legal protection. Make sure the form text, policy page, and data transfer flow all say the same thing.

Quick setup summary: first connect one service, then choose one subscription display location, then one test list and one tag. Only after a successful test should you expand the setup to both forms or to a live audience.

Practical scenario: subscribing a user after ticket creation

Let us walk through the scenario that makes the most sense for SupportCandy Email Marketing Tools Integration: a user creates a product-related ticket and voluntarily opts in to receive educational emails. The goal is to send that contact into the selected email platform with a tag so the marketer can follow up with useful guides and updates instead of generic promotional noise.

Scenario goal

You want the following result: on the new ticket page, the user sees a clear subscription option, submits the request, and their email appears in the selected Mailchimp, GetResponse, or Brevo audience. If the service supports tags through the add-on settings, the contact should also receive a tag tied to the support-ticket source.

Preparation

• SupportCandy already has a working new ticket page or a full support portal.
• A test audience or list has been created in the selected email service.
• A test tag has been created, for example support-ticket.
• Your site policy explains that the user may subscribe to helpful emails related to the product or support.
• You have a test email address that does not already exist in the selected audience.

Setup steps

1. Open Support → Settings → Email Marketing Tool → General.
2. In Connection, choose the service that will receive contacts.
3. In Subscription Options, choose to show the option on the create new ticket page. If the setting is labeled slightly differently in your interface, follow the intent: the opt-in should appear in the new ticket form itself.
4. Open the selected service tab and enter the API Key.
5. Select the test Audience or list.
6. For Mailchimp, set the Default Subscriber Status according to your confirmation model. If you use subscription confirmation, make sure the user understands that they need to open the confirmation email.
7. Add Subscriber Tags if they are available for the selected service.
8. Save the settings and clear the support page cache if a cache plugin is serving the public form.

Testing on the public site

Open the new ticket page in a private browser window. Fill out the form as a normal user, check the subscription box, and submit the request. Then verify three places: the ticket itself in SupportCandy, the support notification, and the contact in the email platform. If the ticket is created but the contact is missing, the problem is not the ticket form itself. It is the connection to the email service or the contact status.

A note about existing contacts

If the test email already exists in the audience, the result may differ. In Mailchimp, for example, the contact status and behavior depend on the current state of that contact. In Brevo, the contact may be updated or added to a list depending on the API logic in play. That is why the first test should use a clean address. The second test can use an existing contact to see whether the tag updates correctly and whether any duplicate-related behavior appears.

How to verify the result after launch

Once the integration is enabled, do not stop at saying "contacts should appear." Build a short verification checklist that an administrator can repeat without a developer. This is especially important if several roles are involved: the site owner, marketer, support agent, and outside technical specialist.

Check inside SupportCandy

In SupportCandy, verify that the ticket was created under the correct user or guest email and that the form did not lose any required fields. If the subscription checkbox does not appear on the new ticket page, go back to Subscription Options and the page settings. If you are using a custom new ticket page, make sure SupportCandy scripts are loading there. The SupportCandy documentation separately calls out script loading for shortcode-based pages, and that often affects the form.

Check inside the email platform

In the email platform, look for the contact by status as well as by list. In Mailchimp, the contact may be subscribed, pending, unsubscribed, or in another state if it already existed in the audience. In GetResponse, check the list and the tag. In Brevo, check the contact email, the list, and any available attributes if your account uses them.

Do not jump to conclusions too quickly. Some services show new contacts in the interface with a delay, and subscription confirmation may depend on an email the user still needs to open. But if the contact still does not appear after a reasonable amount of time, move into troubleshooting: API key, audience, status, browser errors, cache, plugin conflicts.

Check the marketing workflow

A contact appearing in the list does not mean the communication is ready. Verify that the automation, segment, or manual campaign is not sending the user the wrong email. Someone who came in through support may already be frustrated. The first message after the opt-in should help them: a knowledge base, a how-to guide, answers to common questions, or product updates, not an aggressive sales sequence.

A solid success criterion: a new user with a test email created a ticket, voluntarily opted in, appeared in the right audience, received the expected status and tag, and did not trigger a marketing sequence unless you intended it.

Tags and segmentation for support: how to keep the database from turning into chaos

Subscriber Tags are one of the most useful parts of this integration, because the mere fact that someone contacted support does not say much about their intent. One person asks a technical question, another needs help with access, a third wants pricing information, and a fourth just sends a message through the form. If they all land in one list with no source markers, the email strategy quickly becomes blunt and ineffective.

Start with a minimal tagging model. One tag represents the channel, another represents the subscription location, and a third reflects a broad product interest. For example, support, ticket-form, and plugin-help. There is no need to send the ticket subject or full message into a tag. It is awkward, unsafe, and almost useless for campaign targeting.

How to connect tags to future emails

A tag should answer a marketer's question: what email can we send this person without it feeling random? If the tag is support-ticket, a logical follow-up could be a guide to working with support, a roundup of useful resources, instructions for creating a ticket with attachments, or an explanation of support response times. If the tag is product-question, you can send a product education resource. If the tag is too vague, such as new, it does not help much.

Validate tags in two stages. First, confirm that they are applied to a test contact. Then create a test segment in the email platform and make sure that contact appears in it. Only after that should you enable automated emails.

What to do if you need a more advanced workflow

Sometimes a team wants more: different tags by ticket category, by product, by customer status, by WooCommerce order, or by LMS course. Do not present those as promised capabilities of SupportCandy Email Marketing Tools Integration unless your version's documentation explicitly confirms them. For more advanced logic, look at other SupportCandy extensions, external webhooks, CRM integrations, or dedicated marketing plugins. The add-on covered in this guide is confirmed to send a subscriber to the selected service with basic audience and tag settings, not to act as a full rule builder.

Consent, security, and performance

Technically, the subscription is just a small checkbox in a form, but for the site it is still a transfer point for personal data to an external service. That means the configuration should be treated not only as a marketing convenience, but also as part of your data handling process. SupportCandy includes separate Terms and Conditions and GDPR settings that help explain data storage and submission consent. They do not override your regional requirements, but they provide the right foundation for a transparent interface.

Consent should be separate and easy to understand

Do not hide the subscription inside the general ticket submission text. When a user creates a support request, their main goal is to get help. Marketing consent should be separate, readable, and never pre-enabled without a clear reason. The text next to the checkbox should be written plainly: what exactly the user will receive, how often, and how to unsubscribe.

If your site is multilingual, review the translation of the consent text carefully. Do not allow a situation where the ticket form is translated but the subscription block stays in another language or promises something different from what is actually sent. In the Russian version, the wording should be specific: educational materials, product updates, support instructions - not a vague phrase like "marketing communications."

API keys and access

Mailchimp, GetResponse, and Brevo API keys should not be stored in article notes, screenshots, open tickets, or task descriptions for outside contractors. If you are handing the site over for support, it is better to grant limited access inside the service itself or create a separate key that can be revoked later. After an administrator change, verify that old keys are not still active unnecessarily.

If the integration stops working after a key change, do not immediately start switching every setting around. First verify the service connection, then the audience, then a test form submission. That way, you avoid creating a second problem on top of the first one.

Site speed and caching

This integration should not noticeably slow down the public site in most cases, because its main work happens when the registration form or ticket form is submitted. But caching and optimization tools can interfere with form display or AJAX requests, especially if the support page is built in a nonstandard way. If the checkbox does not appear or the form behaves unpredictably, temporarily exclude the support page and the new ticket page from aggressive JavaScript optimization, then test again.

Do not disable the entire site cache permanently. It is enough to exclude SupportCandy shortcode pages selectively or make sure the Load Scripts setting covers the necessary pages. After testing, re-enable optimization and repeat the test in a private window.

Why the subscription is not working and how to find the cause

Errors in this kind of integration are rarely mysterious if you move through the chain step by step. First check the SupportCandy form, then the subscription display location, then the API key, then the audience or list, then the contact status and tags. Do not start by reinstalling the plugin before you have checked the simple causes.

The subscription checkbox does not appear in the form

Symptom: the user opens registration or the new ticket form but does not see the subscription option. The ticket itself may still be created normally.

Possible causes: a different screen is selected in Subscription Options, the user is on the wrong page, SupportCandy scripts are not loading on the custom page, cache is serving an older version of the form, or the integration is not active.

What to check: open Support → Settings → Email Marketing Tool → General and confirm that the display location matches the real user path. Then review Support → Settings → General Settings → Page Settings, especially the custom page URL and script loading.

How to fix it: choose the correct display location, clear the page cache, and test the form in a private window. If you are using a page builder or a separate template, temporarily test a plain page with the SupportCandy shortcode.

The contact does not appear in Mailchimp, GetResponse, or Brevo

Symptom: the ticket is created, the user checked the subscription box, but the contact cannot be found in the email service.

Possible causes: incorrect API key, wrong list selected, the contact is waiting for confirmation, the email already existed under a different status, the service is delaying the display, or the request was rejected بسبب account restrictions.

What to check: use a new test email, verify the selected audience, and check the contact status. In Mailchimp, check specifically whether the contact is in pending or unsubscribed status. In Brevo, verify the list and email, not just the general contacts screen.

How to fix it: create a new API key, choose a test audience, save the settings, and repeat the submission. If the service shows an authorization error, revoke the old key and connect the new one.

The tag was not applied to the subscriber

Symptom: the contact appears, but the expected tag is missing or the tag-based segment is empty.

Possible causes: the tag is misspelled, the wrong service is selected, the current service or pricing tier does not handle tags the way the team expects, or the contact already existed and its data was not updated.

What to check: compare the tag spelling in SupportCandy and in the email service. Create a new contact with a new email. Check not only the contact card, but also the segment that is supposed to use that tag.

How to fix it: simplify the tag to a short ASCII value without spaces or special characters. For example, use support-ticket instead of a long phrase. Repeat the test with a clean address.

The user subscribed twice or ended up in the wrong audience

Symptom: the same email appears in an unexpected segment, the user receives the wrong sequence, or the marketer sees duplicates or conflicting statuses.

Possible causes: the subscription is enabled on both registration and the ticket form, the site already has a separate newsletter form, or Mailchimp audiences and GetResponse/Brevo lists were chosen without a shared structure.

What to check: follow the user's path from registration to ticket submission. Separately check footer forms, popups, and checkout opt-ins if they exist. Compare the tags applied by each form.

How to fix it: keep one primary SupportCandy subscription flow or separate your tags by source. If the user needs to see the checkbox in two places, the consent text and list purpose should be equally clear in both.

The form breaks after optimization or an update

Symptom: the checkbox appears and disappears inconsistently, the submit button behaves unpredictably, or the behavior changes after a theme or cache plugin update.

Possible causes: script optimization affected SupportCandy pages, the new ticket page is not included in the script loading list, or cache is serving stale form markup.

What to check: disable JavaScript optimization only for the support page and test again. Then check the Load Scripts setting in SupportCandy. If the problem disappears, bring optimization back gradually.

When to roll back the setting: if enabling the subscription option makes the ticket form unstable for real users, temporarily disable the subscription display and keep SupportCandy itself working. The subscription feature can be restored after testing on a staging site.

Useful improvements without inventing hooks or making risky edits

For this add-on, do not make up PHP hooks or hidden CSS classes unless they are confirmed by the documentation or by the code in your version. It is safer to improve the workflow through SupportCandy settings, list structure, and form wording. That may not look like a hack, but it is far less likely to break ticketing after an update.

Create a separate admin test checklist

Create an internal note for the team that records the selected service, audience, tag, subscription display location, test email, expected status, and the person responsible for email campaigns. A checklist like that is more useful than random custom code, because most errors happen not in PHP but in misalignment between support and marketing.

SupportCandy Email Marketing Tools Integration check:
1. The new ticket page opens for the intended role.
2. The subscription checkbox is visible next to clear text.
3. The test ticket is created without errors.
4. The contact appears in the selected audience.
5. The support-ticket tag is applied.
6. The automation in the email service does not start by accident.

This snippet is not something you need to insert into WordPress as code. It is a working checklist for an administrator or QA specialist. You can keep it in project documentation so the integration can be retested quickly after updates.

Separate support wording from marketing wording

Do not use wording next to the checkbox that promises a "support response" while also subscribing the user to updates. The support response should arrive whether the user opts in or not. Marketing consent must be a separate action. Good wording is short and clear: the user understands that the ticket will be sent either way, while the subscription provides additional resources.

If the site has multiple languages, align the translations of key terms. In the Russian version, do not leave outside-the-form words like newsletter or updates if you can say "helpful emails" or "product updates" instead. Exact service names and interface button labels can remain in English, especially inside the admin panel.

When SupportCandy Email Marketing Tools Integration is the right choice

This add-on is worth using if you already have a working SupportCandy setup, a clear support portal, and a selected email marketing service. It is especially useful when the subscription option should appear at a natural contact point: during support portal registration or when creating a ticket. In that scenario, the integration helps you keep consenting users from slipping through the cracks and immediately label them as part of the support audience.

Before going live, verify three things: the user sees clear consent text, the contact lands in the right audience, and the tags do not turn the database into a mess. If all of that works with a test address, you can download the latest version of SupportCandy Email Marketing Tools Integration and then repeat the setup on your own site using this guide.

If what you really need is not contact transfer from a support form but a full email system, CRM, visual email builder, and advanced automations inside WordPress, it is better to choose a dedicated marketing tool first. SupportCandy Email Marketing Tools Integration is strongest as a bridge between the ticket and the audience, not as a replacement for an entire marketing platform.