Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article3 min readViews1

Contact Form for 1C-Bitrix: Why a Submission Should Not End with the Message "Sent"

Bquadro has released a ready-made form module. I examine what else a store needs to configure: message delivery, question storage, and a clear response for the buyer.

Comments 0

An employee of an online store responding to a buyer at a workstation
In this article

The message "Your message has been sent" reassures the buyer. However, it does not yet prove that the inquiry reached a person who can respond. Often, several unrelated settings lie hidden between the button on the website and the first useful answer.

On September 15, 2026, Bquadro published an analysis of its free contact form module for 1C-Bitrix. It allows configuring fields, mandatory completion, and protection against automated submissions. A ready-made form accelerates launch, but the workflow must be reviewed in its entirety.

Ask Only What Is Necessary

To clarify product sizes, the organization name and full delivery address are usually unnecessary. Every mandatory field must have a clear purpose. If the buyer prefers a response via email, requiring a phone number needs separate justification.

It is useful to automatically transmit context: from which product card the inquiry originated and which product variant was selected. The buyer will not have to re-enter a long model name. At the same time, the employee must see the context directly in the inquiry, not search for it across scattered notifications.

On a phone, verify that the form fits above the keyboard and that text is preserved after an error. The most frustrating scenario is when a user has detailed their request, mistyped a single character, and lost the entire message.

Submission, delivery, and response are distinct events

A site may successfully accept a form, yet the email could end up in spam or go to a former employee's mailbox. Therefore, testing must include actual message receipt and assignment of a responsible person. A green confirmation notification alone is insufficient.

Determine where the inquiry is stored if the notification fails to deliver. For critical issues, there must be a way to retrieve the original text and the send time. This also helps resolve duplicate messages: a buyer might have clicked the button twice because they did not see a confirmation.

Make the success message substantive. Specify a clear next step and a realistic response time that the team can actually meet. Promising a callback in one minute is harmful if no one is working at night.

Test the form after site changes

A new template, security update, or email migration can affect a form that has been working for a long time. I would include regular checks involving sending from both a computer and a phone, delivering a message to a work mailbox, and having an authorized employee open the attached file.

To evaluate the benefit, you need not only submissions but also the quality of inquiries: how many received a response, how many were related to missing information in cards, and how many led to orders. If a question repeats every day, it may be more profitable to fix the product page. A good form helps communication but should not compensate for all catalog gaps.

Discussion 0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.