Standard & Individual request processes - Which options do you have?
An important goal of the Rubens Configurator is to increase the conversion rate. Conversion goals are manifold; one of them is the generation of requests by interested users and potential new customers. In this article, we will show you both the standard request process and ways to customize it.
Requests in the Rubens Standard User Interface
The Rubens Configurator User Interface offers the possibility to initiate a request via the fixed button "Request Product":
When the "Request product" button is clicked, information such as ConfigurationID, parts list, price (if price calculation is activated), label and image are transferred from the configurator.
In addition, this information can be processed further by the store as required - displaying an image of the configuration in an overlay, saving the configuration ID, forwarding the price to an existing web store based on the partlist, etc. For lead generation, for example, a form that requests specific customer information is suitable. When the form is submitted, the previously mentioned information such as configuration ID, part list, etc. can be sent to a defined mail address.
In order for a request to be triggered in the standard and the corresponding information to be transmitted, the callback "onRequestProduct" must be defined in the integration code.
💡Explore our documentation on "Listen to onRequestProduct" for a code example.
Save draft & get share URL
By clicking on "Save draft", the user receives a link with which he can open the previously created configuration again at any time. By default, the link takes the user to the Roomle destination and not back to your own destination. If you want the user to return to your webshop when opening the configuration, you have to change the share URL accordingly. Furthermore you have to make sure that you have a page where existing configurations can be called again.
💡Explore our documentation on "Change share url".
Individualization of Requests in the Rubens User Interface
You can deviate from the Roomle standard and define your individual request process. For this you can hide certain standard Roomle buttons first.
💡Explore how to do that in our documentation "Show/Hide certain Buttons".
So if you want to use your own buttons and thus call the request from outside, you use the method "triggerRequestProduct". This will trigger the same process as in the standard scenario, even if you work with your own call-to-actions and design your own overlays.
💡To go the individual route, you should engage a web developer with Java Script knowledge.
Here is an example of different call-to-actions with customized buttons and overlays: