From property enquiry to viewing: a Swiss agency playbook

A visitor asking “Can I see reference ZH-204 on Saturday?” has not booked a viewing. You still need a valid listing, the right broker, access to the property and an available time. Write down who checks each item before you automate anything. An enquiry assistant can collect the request immediately while your team makes those checks.

intoCHAT can book through one Cal.com or Calendly calendar and one event type per agent. It does not automatically select a different event type for each listing or check who holds the keys. A practical first setup is a viewing-request form plus an optional “15-minute property consultation” calendar. Call that meeting a consultation throughout the chat. Offer an actual viewing only if the configured event type, location and availability are valid for that property.

The workflow below is a design you can adapt, not a claimed customer result. It assumes you control the agency website and can keep its published listing information current.

A long application form is a poor opening conversation. For a first viewing request, collect only what the team needs to identify the property and reply. Ask broader search criteria only when the visitor has no listing in mind. Do not ask for identity documents, bank statements or a full rental application in the chat.

Create a chat form on the Actions tab. The example below uses six fields, well within the twenty-field limit. Labels and dropdown choices are your own text; translate them for the audience that sees the form. The confirmation should say “Request received; our team will contact you to arrange a viewing,” so nobody mistakes a submission for a reservation.

Begin with a manageable group of active listings, your contact page, office hours, viewing process and approved answers about fees. Preview the imported text: a polished listing page may hide essential details in images or a PDF. Make sure the property reference, rent or price, currency, stated additional costs, address or area and publication status are readable.

Treat a crawled listing as a snapshot. Auto-resync can check website pages daily or weekly and retrain changed text; it is not a live availability feed. Refresh and verify a changed listing before relying on the new answer. If a property disappears from your site, check the source list and remove obsolete knowledge instead of assuming that a failed fetch has removed it. Uploaded brochures need a new upload when they change.

intoCHAT has no native Homegate, ImmoScout24, Garaio REM or ImmoTop connection. A developer can evaluate a custom API action when your property system exposes an appropriate API. Until that is built and tested, the agent must describe uncertain availability as something the broker will confirm.

Paste these rules into Instructions, replace the bracketed placeholders and adjust the wording to your process. They guide the agent; forms, handoff and calendars still have to be configured separately. Choose either the request-only rule or the optional booking rule rather than leaving conflicting instructions in place.

On Actions, connect Cal.com or Calendly and select the single event type that this agent should book. The current Calendly Scheduling API requires a paid Calendly plan. intoCHAT cannot use Calendly event types with required additional questions or a location that needs invitee input. Collect property details in your chat form, or use a suitable external booking page when your appointment needs fields the in-chat picker cannot supply.

Set “When to offer booking” to the purpose you actually support, for example “When the visitor asks for an initial property consultation; explain that it is a call to discuss the request and does not reserve an on-site viewing.” The picker gets times from the provider and displays the visitor’s time zone. Its name-and-email step does not automatically send your chat-form answers into the calendar event.

Cal.com can require host confirmation. In that case, distinguish a requested appointment from a confirmed one. Rescheduling and cancellation happen in Cal.com or Calendly; intoCHAT’s booking list retains the original record. Give your team a clear rule for checking the calendar before contacting the visitor.

intoCHAT replies in the visitor’s language by default. Its widget language is a separate setting. Your form title, custom labels, choices, confirmation and calendar event title stay as you wrote them. A French AI reply above a German-only viewing form is an unfinished experience.

Review the complete journey in German, French, Italian and English where those languages matter to your agency: welcome text, listing answer, form, appointment title, confirmation and the colleague’s follow-up. Use explicit language-specific forms or page-specific agents when you need predictable field labels. Do not rely on the AI to translate the saved form itself.

For German-language Swiss pages, preserve local room descriptions such as “3.5 Zimmer” and CHF formatting from the source. Do not turn rooms into bedrooms or translate a named neighbourhood into a different place. Swiss German questions deserve their own tests; choose standard German replies if that is your agency’s written style.

Choose one responsible inbox and a backup colleague before launch. Chat-form emails use your lead-alert recipients and require “Email when a new lead arrives” to be on. Turn on the separate Form submission and Booked meeting Slack options if you want those alerts. Test the actual destination instead of assuming every event creates a lead email.

For CRM automation, consume the event for what happened. Form submissions and calendar bookings are separate records; neither emits lead.created. Use their conversation reference in your receiving workflow to connect them when you need the request details beside the appointment. A developer or automation tool must implement that join and any broker-routing rules; it is not an automatic real-estate CRM sync.

This illustrative conversation uses an invented listing, not a customer case study. Assume its approved source says reference ZH-204 has a parking space at an additional CHF 150 per month, but current availability must be checked by the team.

Visitor: “Is parking included for ZH-204, and can I visit on Saturday?” Assistant: “The listing shows parking at an additional CHF 150 per month. Saturday would be a request rather than a confirmed appointment. You can send the property reference and your preferred time below, and our team will arrange the viewing with you.”

After the form is submitted, the saved form confirmation acknowledges the request. If a consultation calendar is also enabled, the assistant can offer that clearly named call. It does not turn the call into an on-site viewing or claim that the property has been reserved.

Use an invented test listing and no real applicant data. Run each question manually through the complete visitor journey, then use the same expectations in Tests with simulated customers on Starter and above. Simulated tests do not submit forms, send handoffs or create bookings, so verify those deliveries separately. A booking made in the ordinary Playground is real; use a designated test event and cancel it in the calendar afterwards.

Before launch, save a baseline from a comparable period if you have one: website property enquiries, usable viewing requests, confirmed appointments and staff time spent clarifying requests. Keep the property mix and traffic source visible. Without a baseline, the first week establishes one; it does not prove an uplift.

Track unique conversations with viewing intent, submitted viewing-request forms, requests that contain the required reference and contact, separately booked consultations, and viewings your team actually confirms. A consultation is not a viewing, and a chat that saves an email is not automatically a qualified property enquiry. The dashboard’s lead count alone cannot answer those questions.

Define “usable request rate” as usable viewing requests divided by all submitted viewing-request forms. Define “confirmed viewing rate” as team-confirmed viewings divided by usable viewing requests. Record numerator and denominator beside each percentage; small samples are directional. Inspect incorrect availability answers and booking misunderstandings individually.