Weblium and Wix inquiries and orders: how to build a streamlined CRM process

If data has to be transferred manually, managers spend time on administrative work before they even have their first conversation with a customer. As the number of inquiries grows, it becomes harder to keep track of who has already responded to a customer and what needs to be done next.

Integrating Weblium or Wix with a CRM connects your website with your team's workflow. Let's look at this process using Uspacy as an example—from receiving the data to further processing an inquiry or order.

Weblium and Wix are platforms for creating websites and online stores. They help businesses showcase their products and services, add inquiry forms, and accept online orders.

For example, an agency may create a website with a portfolio and a “Request an estimate” form. A potential customer reviews examples of the agency’s work, selects a service, and submits their contact information. A consulting company may use a landing page to allow visitors to book a consultation. A store can showcase products that customers can order directly from the website.

In each case, the business receives information that marks the beginning of a customer interaction. This could be a quick question, a request for a customized offer, or a completed order.

That is why a website should be viewed as part of the overall customer management process. After submitting a form, a person expects a response; after making a purchase, they expect confirmation and fulfillment. The team then needs a place where it can work with the data it receives.

The integration automatically transfers information from the website to the CRM. Managers no longer need to manually copy contact details and inquiry information each time.

However, receiving an inquiry does not mean it has been handled. Someone needs to be assigned responsibility, the next action needs to be scheduled, and any agreements need to be documented. If a customer is promised an estimate by Friday, the team should know who is preparing it and when the manager will send the result.

In the CRM, employees continue working with the inquiry: clarifying the customer’s needs, recording the outcomes of conversations, and moving the sales process toward completion. When a colleague joins the process, it is easier for them to understand the situation from the customer record.

This way, the website and CRM support a consistent customer experience. The website collects the initial information, while the team uses it to carry out specific actions. The workflow depends on what the customer did: placed an order or submitted an inquiry.

Website inquiries require different types of follow-up. That is why it is worth defining the next steps for orders and inquiries in advance.

Online store order. A customer selects a product and completes a purchase. The team needs to review the details, confirm the order, clarify payment and delivery terms, and monitor fulfillment.

The manager needs the customer’s information and order details. If any questions remain unresolved, the manager clarifies them before handing the work over to colleagues. For example, they confirm the shipping date and let the customer know when to expect delivery.

Form inquiry. Someone requests a consultation or a custom estimate but has not yet agreed to the terms of cooperation. The manager contacts them, identifies their needs, and determines the next step.

For the initial conversation, it is helpful to have the customer’s name, contact information, selected service, and a brief description of their request. If the proposal requires an estimate from a specialist, the manager passes along the clarified requirements. The customer should understand what they will receive and when.

In short, the main focus for an order is confirmation and fulfillment. For an inquiry, it is understanding the customer’s needs and preparing a solution.

Both integrations transfer store orders and inquiries from connected forms to Uspacy. For each type of inquiry, you can specify which CRM records will be created.

A Contact and a linked Deal are created after an order is placed. In the settings, select the pipeline, default source, and responsible person. The manager can review the order and move it through the stages until it is fulfilled.

A Lead or Contact is created after a form is submitted. The data is transferred to CRM fields according to the configured field mapping. For example, a “Request an estimate” form can transfer the customer’s name, contact information, selected service, and description of their needs.

For both integrations, you need to install the corresponding app from the Uspacy Marketplace.

In Weblium, you need to add the webhooks provided by Uspacy separately for the store and forms. The webhook should be connected to each required form. Then publish the changes and test all fields by submitting the form — after submission, the form will become available for configuration in Uspacy.

In Wix, you need to install the dedicated Uspacy app on your website and obtain the Instance ID to connect it to your Space. Then select the required forms, map the fields, and configure order processing.

Step-by-step instructions are available in the guides for connecting Weblium and connecting Wix to Uspacy.

The manager then continues working with the customer: schedules a call as an activity or involves colleagues through Uspacy tasks. For example, they can assign a specialist to prepare an estimate and link the task to the lead. For a product order, they can create a task to prepare the order for shipment and link it to the deal. This keeps customer communication and the team's internal work aligned.

Before getting started, test the entire workflow using a test inquiry. Submit a form and place a test order, then review the results in the CRM.

For Weblium, publish the changes and test the form by filling in all fields. After submission, it will become available for configuration in Uspacy. In Wix, save the settings for each form separately using the button in its own section.

Follow the customer journey from submitting their information to the manager's first action. This will help you verify both the integration settings and the team's readiness to handle inquiries.