VTE Next

Contact synchronization, Data mapping, Automatic update, CRM segmentation, API connection

Description: Integrate information and services from your VTENext CRM system within your Framework360 account, allowing centralized management of customer data.

What is it for? (Practical examples)

This tool is essential to keep customer data aligned between the Marketing Automation platform (Framework360) and your CRM system (VTENext).

  • Centralized contact management: Ensure that every new contact acquired through Framework360 (e.g., newsletter subscription or registration) is immediately created or updated in your CRM.
  • Advanced segmentation: Synchronize contacts into different VTENext categories (Leads, Accounts, Contacts) based on specific conditions defined in Framework360.
  • Always up-to-date data: Avoid manual entry and reduce errors, ensuring that personal information (address, phone, company name) is always consistent across both platforms.

Main features

Conditional contact synchronization

It is possible to define precise rules for exporting contacts. Based on these rules, a contact acquired in Framework360 can be sent to VTENext and categorized as:

  • Lead: Useful for initial contacts or potential customers.
  • Account: Useful for companies or existing customers.
  • Contact: Useful for individuals associated with an Account or as direct contacts.

Data field mapping

The system is preconfigured to automatically map the main personal data fields from Framework360 to their equivalents in VTENext, including:

  • First Name, Last Name, Email, Landline and Mobile Phone.
  • Company Name, Website.
  • Address, ZIP Code, City, State.
  • VAT Number and Tax Code (if available in billing data).

Support for additional custom fields

If you use custom fields to collect specific data in Framework360, you can manually map them to the corresponding fields in your VTENext system (e.g., map a custom "Sector" field to the CRM's "Industry" field).

Automatic record updating

When a contact is synchronized, the system checks if the record already exists in VTENext (typically via email address).

  • If the contact exists, it is updated with the new information.
  • If the contact does not exist, a new record is created.

How to configure

The configuration is divided into two phases: initial authorization and synchronization rule definition.

1. Connect to VTENext (Authorization)

To connect Framework360 to your CRM, you will need to provide API credentials.

Configuration FieldDescription
VTENext DomainThe full address of your VTENext system (e.g., https://mycrm.vtecrm.net/).
UserThe username associated with your API credentials.
Access KeyThe access key provided by VTENext for authentication.

During this phase, Framework360 will request authorization for Contact Management, necessary to read and write customer data in your CRM.

2. Set up Contact Synchronization

After establishing the connection, you need to define export rules in the "Contact Synchronization" section of the plugin settings.

For each VTENext category (Leads, Accounts, Contacts) you must:

1. Define Conditions: Use the query builder to specify which Framework360 customers should be sent to that specific category.

  • Example: Send only customers who have made a purchase as "Account".

2. Map Additional Fields (Optional): If you have custom fields in Framework360, use the dropdown menu to select the corresponding VTENext field where to save that data.

Automatic integrations

Contact synchronization is a fully automated process triggered at key moments of user interaction:

Immediate synchronization upon registration

Whenever a user completes a registration process (for example, creating a customer account on your website), their data is immediately analyzed and, if it meets the set conditions, sent to VTENext.

Synchronization upon newsletter subscription

When a user subscribes to one of your newsletters, their data is automatically verified and synchronized with your CRM, ensuring that new leads are immediately available to your sales team.