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 read

Contact Form on 1C-Bitrix: Why a Submission Shouldn't End with Just "Sent"

Bquadro released a ready-made form module. I examine what else a store must configure: message delivery, question logging, and a clear response to the customer.

An online store employee responding to a customer at a desk
In this article

The message "Your message has been sent" reassures the customer. However, it does not prove that the inquiry reached a person capable of answering. Often, several disconnected settings lie between the button on the site and the first useful response.

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

Ask Only What Is Necessary

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

It is useful to automatically transmit context: which product card the inquiry came from and which offer was selected. This saves the employee from rewriting long model names. The employee must see this context directly in the inquiry, not search for it across scattered notifications.

On mobile, 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 carefully described an issue, mistypes a single character, and loses the entire message.

Sending, delivery, and response are distinct events

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

Define where the inquiry is stored if the notification fails to deliver. For critical questions, you must be able to locate the original text and submission timestamp. This also helps resolve duplicate submissions: a buyer might have clicked the button twice because they did not see a confirmation.

The success message should be substantive. Specify a clear next step and a realistic response time that your team can actually meet. Promising a callback within a 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 recommend including regular checks: sending from both desktop and mobile, delivering to a work mailbox, and verifying that an authorized employee can open any attached files.

To evaluate the value of a contact form, you need more than just submission counts; you must assess the quality of inquiries: how many received a response, how many stemmed from missing information in product cards, and how many led to actual orders. If the same question repeats daily, it may be more cost-effective to fix the product page itself. A well-designed form facilitates communication but should not compensate for all catalog gaps.

Discussion0

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

No comments yet. Start the discussion.