Web Inquiries & Tour Requests

A prospect fills in the tour form on your website at eleven at night; by morning, a leasing agent has an inquiry that already knows the unit, the ad that brought the prospect in, and a showing on the calendar. That's the web-inquiry loop: your public listing pages turn a form submission into a REDA Inquiry — REDA's record for someone who has reached out — carrying the visitor's details, where the property page was, and the full campaign attribution. This article is for the leasing agents who work those inquiries and the marketing analysts who report on them. After reading it, you'll be able to read a web inquiry's provenance fields with confidence, and trust the attribution data behind your campaign reports.

Where web inquiries come from

Web inquiries arrive from the public listing pages that REDA publishes for your properties — the search and unit-detail pages embedded in your marketing website. Each unit page carries a contact form and a "schedule a tour" form. When a visitor submits either one, REDA writes an inquiry on the spot. (For how those pages are set up and what they show, see Publishing Properties to Your Website.)

What the form writes onto the inquiry

The form fills in far more than a name and an email. Here's the full picture of what lands on the inquiry, and when:

The record type matters: it's set from the visitor's action — a rent enquiry becomes a Leasing inquiry, a buy enquiry becomes a Property Sale inquiry — and it drives the path the inquiry follows afterward.

The automatic showing event

When the visitor uses the tour form rather than the plain contact form, REDA doesn't just record the requested date on the inquiry — it also creates a showing event linked to the inquiry, so the requested tour lands on the calendar rather than sitting as a note someone has to action. The tour request itself is captured on the inquiry as three details:

So a prospect who asks for an afternoon virtual walkthrough on the fifteenth arrives with all three details on the record — the agent knows the when, the roughly-when, and the how before they even pick up the phone.

Attribution data for marketing

The reason web inquiries are worth reading closely is the attribution they carry. When a visitor arrives through a tagged campaign link or an ad click, the form records exactly where they came from, so your reports can credit the right campaign. Two kinds of data do this work:

Only visitors who arrive with these tags carry them — someone typing your address directly has none, which is expected, not a fault.

Working a web inquiry

Once it's created, a web inquiry is an ordinary inquiry — the Web source and its record type simply tell you where it came from. From here it follows the normal path:

• The Web source value sets these apart in list views and reports, so you can filter to website leads.
• If the same prospect submitted twice, REDA flags it: use the Potential Duplicates card and Merge Duplicates on the inquiry (see Finding & Merging Duplicate Inquiries).
• When the prospect is ready, convert the inquiry to a lease or opportunity with the standard convert action; for rentals, an online lease application may run first.

Two web paths, same fields

Your REDA listing pages aren't the only way a web inquiry can appear. External forms — a Webflow-native form, another landing page — can send the very same attribution payload through the Data Service, which offers exactly this set of web parameters as a no-code intake. Same fields on the inquiry, a different pipe feeding them: the listing page writes the inquiry directly, while an outside form posts through the Data Service.

Worked example: Aisha finds Meridian Court #101

Aisha spots Meridian Court #101 through a Google ad and clicks through — landing on the unit page with utm_source=google, utm_campaign=summer-lease, and a Google click ID in the address. On the page she requests a Saturday-morning tour. The result in REDA:

Marketing's "leads by campaign" report counts Aisha under summer-lease, and the agent has her tour on the calendar before the office opens.

The Inquiry created from a web submission — Record Type Leasing, Inquiry Source Web, and the matched property (Meridian Court #101) and property type carried onto the record.

The same inquiry's Web Info section — the full UTM set (source, medium, campaign, term, content) plus the captured click IDs and landing page.

Where to go next

1. Publishing Properties to Your Website (RDELS) — the pages that host these forms.
2. REDA Data Service: Connect Your Forms — the other pipe that writes web inquiries.
3. Online Lease Applications (RLA) — the usual next step for a rental prospect.
4. Finding & Merging Duplicate Inquiries — handling the same prospect twice.

Frequently asked questions