What the data for this category looks like
Residential development marketing form data mainly comes from online landing page submissions, in-person registration at sales offices or exhibition points, and referrals from distribution channels. Update rhythm follows two patterns: single submissions are stored in real time, while bulk summaries are updated daily. Most fields are structured, including intention_unit_type, building_area (unit: square meters), intention_floor, contact_phone_number, intended visit time slot, and other fields. An optional customer remark text box is included. Some scenarios also add a checkbox field for whether to accept marketing push notifications.
Constraints imposed by these characteristics on the forms and interactions link
High proportions of structured fields with specific units require forms to pre-set unit suffixes to avoid user input format errors. Multiple data sources require forms to automatically associate channel identification fields to match follow-up rules for different sources. The real-time single-data storage feature requires the submission process to provide immediate success feedback. The daily bulk summary update rhythm requires configuring scheduled trigger options for bulk exports in the form backend. Enumerated fields such as intended floor and intended visit time slot need preset standard options to reduce manual entry errors. Contact information fields need built-in format check rules to adapt to local number formats.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
global_variable_initial_value | Set to "pending follow-up", bind update trigger condition to form submission event | Matches the initial state requirement for residential development customer follow-up, resolves issues where variable initialization does not take effect |
form_field_unit_suffix | Add "㎡" suffix to the building area field, no additional suffix for the intention unit type field | Adapts to the field unit specifications of residential development forms, reduces user input errors |
conditional_branch_trigger_rule | Trigger branches based on the intention_level field value output by GPT | Adapts to subsequent operational processes layered by customer intention, matches configuration requirements for conditional selection |
knowledge_base_bind_switch | Bind the exclusive knowledge base for the corresponding project, support switching by scenario | Supports calling corresponding knowledge base content based on different residential projects, matches the requirements of selecting models and knowledge bases via API interfaces |
form_submit_success_timeout | 3000 milliseconds | Matches user waiting habits when submitting forms, avoids delayed timeout feedback |
form_input_format_check | Enable format check for contact phone number and date fields | Adapts to standardized entry requirements for residential development customer information, reduces invalid data |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume and business rules. Specific issues require specific analysis, and it is recommended to test on your own samples before finalizing.
Three Common Misconfigurations
- Symptom: After setting the initial value of a global variable, the variable does not update as expected when the form is submitted. Cause: The variable update trigger condition is not bound to the form submission event, only the initial value is configured and the real-time update rule is not enabled.
- Symptom: A
408 Request Timeouterror is displayed on the interface after submitting the form. Cause: Theform_submit_success_timeoutconfiguration value is too short, exceeding the time threshold for backend data synchronization. - Symptom: Conditional branches do not trigger based on GPT output results. Cause: The
intention_levelfield is not specified in the GPT prompt, or the field name in the branch rule does not match the output field name.
How to Confirm the Configuration Is Complete
- Enter the form editing interface, verify that the field suffix configuration matches the requirement that the building area uses
"㎡"and the visit time uses standard date and time format. - Submit a test form entry, check whether the global variable is initialized and updated according to the rules after submission.
- After configuring the conditional branch, input simulated GPT output content to verify that branch redirection meets expectations.
- Enable the knowledge base binding configuration, switch the test knowledge base for different projects, and confirm that the model call link operates normally.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.