--- title: "Conditional Buyer and Seller Forms for Agent Websites" description: "Specify buyer, seller, and property-question form branches. Check conditional requirements, changed answers, hidden values, and the received inquiry." canonical: "https://scalewithsearch.com/articles/conditional-buyer-seller-contact-form-fields" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Conditional logic forms: buyer and seller fields on your agent website Use conditional logic to show the questions that match a visitor's buyer, seller, or property inquiry. Write the branch rules before building the form. Test a changed selection and inspect the received inquiry before accepting the work. Conditional logic changes a form according to earlier answers. Tally documents rules that show or hide questions and make answers required conditionally. [Tally conditional logic documentation, checked 2026.10.14](https://tally.so/help/conditional-form-logic). For an agent website, start with the service question you need to answer. Use the proposed brief below to define visible fields, required answers, and final submitted values. Confirm every requested behavior against your chosen tool's current documentation and a demonstration. ## Write the buyer and seller branch rules Keep a shared contact section for the visitor's name, email address, and question. Add a clearly labeled inquiry-purpose choice. Approve these proposed choices against the services your business provides: | Visitor's selection | Additional questions to propose | Fields to keep out of this branch | | --- | --- | --- | | Buying | Areas to discuss and broad search timing | Seller-property details | | Selling | Property location and the selling question | Buyer-search preferences | | Buying and selling | Both sets, with buying and selling timing labeled separately | None of the approved buyer or seller questions | | A question about a specific property | Property link or reference and the property question | General buyer-search and seller-property sections | | Another question | Shared question and reply details only | All transaction-specific sections | Treat the choices and fields as a design proposal. Avoid collecting documents or financial detail for a first conversation. Leave timing and extra context optional unless you can name a reason to require them. Write the actual conditions beside the sections. Show buyer questions when the purpose is **Buying OR Buying and selling**. Show seller questions when it is **Selling OR Buying and selling**. Give the property-question section its own condition. Keep the shared question visible in every branch. Require an unselected purpose to produce an understandable correction rather than silently selecting a service. Approve the correction wording with the builder. ## Separate visibility from required answers Give every field two decisions: when it appears and when an answer is required. Put those decisions in the same worksheet. A proposed requirement might make a property reference mandatory only for the specific-property branch. Tally documents a **Require answer** action that can change whether an answer is required. Its guide instructs builders to hide blocks initially before showing them through a conditional rule. [Tally conditional actions, checked 2026.10.14](https://tally.so/help/conditional-form-logic). Gravity Forms documents field visibility rules with **all** or **any** conditions. Its rules must refer to another field; self-referencing visibility rules are unsupported. [Gravity Forms field logic, checked 2026.10.14](https://docs.gravityforms.com/enable-conditional-logic/). These are documented examples, not a vendor recommendation. Have the maintainer identify your actual form tool, version where applicable, and supported settings. Request the dated documentation for its required-field behavior too. Require a demonstration that an inactive branch cannot block submission with an unreachable required field. Also test that an active required field produces a visible, correctable error. Keep either result unresolved until observed. The inspected Tally logic guide does not establish what happens to every hidden required field. Do not infer that behavior from its show-and-hide controls. Ask the maintainer to resolve it before accepting the form. ## Decide what survives a changed selection Specify what should happen when someone starts as a seller and then selects buying. Use a controlled seller-property value in the demonstration. Compare the final selected purpose with both the saved submission and the destination record. Gravity Forms says fields hidden by conditional logic are excluded from submission and saved entries. It also says nested conditional logic is unsupported. Keep those limits with the Gravity Forms implementation. [Gravity Forms limitations, checked 2026.10.14](https://docs.gravityforms.com/enable-conditional-logic/). The inspected Tally guide does not establish whether an answer entered before hiding is retained in the final submission. Require documentation and a test for that question. Avoid applying Gravity Forms' rule to Tally or another provider. As a proposed acceptance rule, require the final inquiry to exclude values from branches the visitor no longer selected. If your tool cannot meet that rule, resolve the implementation before release. Consider separate buyer and seller forms instead. Decide whether returning to a previously selected branch restores its entries or asks for them again. Record the chosen behavior. Require shared reply details and the question to remain available during these changes. Keep branch conditions tied to the original purpose choice where possible. Ask the builder to explain dependencies before adding conditions based on other conditionally displayed fields. ## Match the final branch to the receiving record Give the builder a proposed destination map for the purpose, question, reply address, and active branch details. Have the recipient identify where each value should appear. Mark an unsupported destination field unresolved. For the combined branch, require the recipient to distinguish the home being sold from the areas being considered for purchase. Use separate field labels and test values. Avoid a single unlabeled location value for both. For a property question, request the submitted property reference beside the question. Inspect that exact pair at the destination. Do not accept a generic buyer label as sufficient evidence for this branch. Keep these checks focused on the form's final state. Use the [website-to-CRM field map](/articles/real-estate-crm-and-website) for broader record mapping and repeat-contact questions. Do not assume a branch automatically changes notification recipients or contact-system assignment. ## Check visitor data before adding a form tool A form tool may process visitor data. Tally states that it processes and stores respondent data for form creators. [Tally form-data documentation, checked 2026.10.14](https://tally.so/help/gdpr). Ask the maintainer to identify the selected tool, its data-processing documentation, and every intended destination. Have the responsible reviewer approve collection and public privacy wording. Keep unrelated marketing choices outside the inquiry-purpose selector. Use the [privacy applicability draft](/articles/ccpa-applicability-agent-website) and [inquiry retention draft](/articles/website-lead-retention-schedule-agent) to prepare that separate review. Those pages do not determine your business's obligations or approve a vendor. - [File upload security for real estate inquiry forms](/articles/secure-file-uploads-agent-inquiry-forms) ## Test branch changes before accepting the form Agree on labeled test messages and use reply details you control. Run the checks on the published page in the agreed test environment. Include phone use and keyboard operation. | Proposed test | Evidence to require | | --- | --- | | Choose each purpose from a fresh form | Only its approved fields appear; shared fields remain reachable | | Select buying and selling | Both sections appear with distinct labels and correctly received values | | Leave an active required field empty | A reachable correction identifies the field; submission waits for correction | | Leave an inactive required field empty | The hidden branch does not block the selected path | | Enter seller details, then change to buying | The saved and received inquiry follow the approved inactive-value rule | | Switch back to the original branch | Entries behave as agreed; shared contact details remain available | | Change a property question to another question | No abandoned property reference survives in the final inquiry | | Complete the final selected branch | The intended recipient finds the matching purpose, question, and active details | Save the selected purpose, visible fields, submitted values, and matching receipt together. Record the page, date, device, form configuration, and person checking it. Keep failures open until the repaired branch passes a repeat check. These are acceptance requirements to request. They are not evidence that your current form works or a forecast of inquiry results. ## Bring the branch worksheet into your website brief Your branch worksheet records visible fields, inactive values, and the intended recipient for each selection. Bring that behavior to [whole website fix: conditional fields](/for/real-estate). The whole website fix verifies receipt after repairing inquiry delivery. [Published work scope, checked 2026.10.14](https://scalewithsearch.com/work). - [Test the seller inquiry path on your real estate website](/articles/seller-inquiry-path-agent-website) - [Check your real estate website in 30 minutes](/articles/real-estate-website-audit) - [Own your real estate website: domain, hosting, editing, and leads](/articles/own-your-site) ## Related: Real estate - [Test the seller inquiry path on your real estate website](/articles/seller-inquiry-path-agent-website) - [Check your real estate website in 30 minutes](/articles/real-estate-website-audit) - [Own your real estate website: domain, hosting, editing, and leads](/articles/own-your-site) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```