Yes, WPResidence supports popular appointment tools so clients can book showings with specific agents, but in a flexible way. The theme includes its own “Schedule a Tour” system on every property and works with major WordPress booking plugins and embedded SaaS widgets. You keep WPResidence in charge of real estate logic, while tools like Calendly or Amelia handle live calendars per agent or per property.
How does WPResidence handle built‑in scheduling for property showings?
WPResidence lets visitors request a date and time for a tour directly from each listing using its “Schedule a Tour” form.
The schedule form appears on the property page, next to or below the agent box, and uses date and time pickers. In theme options, the admin can pick which hours show for tours and set time slot length, like 30 or 60 minutes. When a visitor submits the form, the request is emailed to the assigned agent or owner and can also go into a CRM flow through tools like HubSpot, while the visitor stays on the listing page.
WPResidence keeps the flow front‑end and simple. They view the listing, pick a day, choose a time, and send the request. The theme stores the tour request as a lead tied to that property and that agent, so an office with 5 agents still stays organized. At first this looks like live booking. It is not. Actual booking steps like confirming, rescheduling, or calendar invites happen between agent and client after that email or CRM event, but the theme collects clear showing requests right when interest is highest.
Can WPResidence connect with popular appointment booking plugins for real‑time slots?
You can embed major WordPress or SaaS booking widgets into WPResidence property and agent layouts so buyers pick real‑time slots.
WPResidence uses Elementor templates and flexible content areas, so any shortcode or embed code from Calendly, Amelia, or Bookly can go into property pages, agent pages, or a global “Book a Showing” area. In practice, you open the Elementor single property or agent template, add a shortcode or HTML widget, and paste the plugin code. From then on, that live calendar shows where you placed it, inside your theme layout. Because WPResidence CSS is modular, most external booking forms inherit your fonts and colors or can be lightly styled without conflicts.
This setup works well when each agent has a personal calendar link. You can store a different Calendly URL in a custom field on each agent profile, then pull that into the Elementor template so each agent’s properties show that agent’s availability. WPResidence already tracks which agent owns which property and where their profile appears, so you simply swap the default tour request form, or place a live widget next to it. So a buyer on a listing clicks a free time and the external tool blocks that slot, sends invites, and helps avoid double bookings.
- You can place a Calendly or Amelia embed next to the WPResidence “Schedule a Tour” form on each listing.
- Each agent profile can hold its own booking shortcode stored in a custom field for per agent calendars.
- Property templates in WPResidence Studio let you show one plugin calendar only on selected property types.
- WooCommerce appointment add ons can be used when you want to accept paid bookings for some showings.
How does WPResidence route showing requests to specific agents or owners?
WPResidence sends each showing or contact request to the exact agent, agency, or owner assigned to that property.
Every listing links to one main profile, either an agent, an agency, or an owner, based on how you run the site. When someone fills out the “Schedule a Tour” form or the contact form on that property, the theme uses that link to find the right email address and user, then sends the lead only to that person or team. This keeps two agents working in the same city from seeing each other’s showing requests, and the admin does not need to sort messages by hand.
Inside the WPResidence front‑end dashboard, each agent or owner can see their properties and the related inquiries, which helps them track who asked to see which home and when. In multi owner or multi agency setups, the portal acts like a marketplace where each listing has its own main contact, but all showing requests still move through one standard WPResidence form flow. If you embed an external booking calendar per agent, that widget can sit in the agent box, and the link between property and calendar stays clear because WPResidence already knows which agent the visitor is viewing.
Can WPResidence support different workflows for paid, free, or premium showings?
The theme can mix free showing requests with WooCommerce powered paid tour products so some appointments are paid and others stay free.
WPResidence includes a membership and pay per listing system that runs with WooCommerce when you need payments, so you can match showing logic with listing packages. For example, you might let standard listings accept free “Schedule a Tour” requests, but create special WooCommerce appointment products for luxury or off market homes where a one to one tour is a paid service. In that case you place a “Book a Private Tour” button on those premium properties that opens a WooCommerce booking add on or an appointments product linked to the listing.
The package system lets you define featured or premium listings that get more exposure, and you can reserve paid showing flows only for those as an upsell. In WPResidence you can label those homes with a custom status like “By‑Appointment‑Only” and pair it with a featured ribbon so they stand out in search and on property cards. When a buyer clicks through, the property template can show the free tour request form, a paid WooCommerce booking form, or both, based on your rules. I should say, this can feel complex at first. But one layout can still cover open house style leads, regular private visits, and high priced appointments without using another theme.
| Scenario | WPResidence setup | Booking / payment handling |
|---|---|---|
| Free standard showings | Use built in “Schedule a Tour” form on listings | Email lead to assigned agent, optional CRM capture |
| Premium paid tours | Mark listing as featured or custom Premium status | Use WooCommerce appointments or paid consultation product |
| Agent specific calendars | Store booking shortcode on each agent profile | Embed Calendly or Amelia calendar under agent box |
| Luxury by appointment homes | Use By Appointment Only status plus featured ribbon | Only show paid booking widget, hide free request form |
| Open house style visits | Use Open House property status and listing badges | Keep tours free, optional event or booking plugin |
This table shows common setups. Most sites start with the free “Schedule a Tour” form, then add WooCommerce appointment products or per agent calendars on higher value listings. I almost framed this as a booking guide. It is not. WPResidence decides which layouts and buttons show on which properties, while the real slot handling and payments still sit in the booking plugin or WooCommerce layer you connect.
FAQ
Does WPResidence have native, one‑click integrations for Calendly, Acuity, or Amelia?
WPResidence does not ship with fixed, one click integrations to SaaS tools like Calendly, Acuity, or Amelia.
Instead, the theme focuses on clean shortcode and embed support so you can add those tools into Elementor templates, sidebars, or agent sections. You copy the calendar shortcode or HTML snippet from the booking service, paste it into a widget in the WPResidence layout, and the calendar appears where you place it. This keeps WPResidence future friendly and lets you swap booking providers without changing the theme.
Can WPResidence itself prevent double‑booking or manage live availability calendars?
WPResidence does not manage live availability or prevent double booking, that logic comes from the booking plugin or service.
The built in “Schedule a Tour” form is a lead capture tool, not a full scheduling engine, so it collects a preferred date and time and sends it to the agent. If you need calendar blocking, reminders, and conflict checks, you use a dedicated appointment plugin or SaaS calendar and embed it for each agent or listing. WPResidence then displays that calendar in the right place and routes visitors to the right person.
Can each property or agent in WPResidence show a different booking calendar?
Yes, each property or agent can show its own booking calendar when you use custom fields and Elementor templates.
A common pattern is to add a custom field on the agent profile for a booking URL or shortcode, then pull that field into the agent box template in WPResidence Studio. Every property tied to that agent then shows that agent’s calendar. If you really need per property calendars, you can repeat the same idea on the property post type, but per agent is usually easier to keep in sync.
How should I handle open‑house events versus private showings in WPResidence?
WPResidence treats open house events and private showings as two layers, labels for events and forms or calendars for visits.
For open houses, you use the Open House status so those listings get a badge and can be filtered in search, then you write date and time details in the description or a custom field. For one to one appointments, you leave the open house status off and use the “Schedule a Tour” form or an embedded booking plugin. Many sites mix both, an open house label plus a free request form, and optional calendar or paid bookings only on a few higher touch properties.
