The core stays the same. The connector changes.
A property agency and a dental practice need different tools, but the AI conversation layer should not be rebuilt from scratch every time.
CRM / lead database
Read customer history, original enquiry, source, status and notes; write back qualification, timing, suppression and handoff context.
Property inventory
Search connected inventory naturally, retrieve trusted property facts and media, remember referenced listings and build viewing plans.
Booking / calendars
Look up available slots, retrieve existing reservations, change bookings when permitted and escalate exceptions with the context attached.
Client-site bridges
Where a provider restricts API calls by IP, a small signed bridge can run on the client’s existing server so their current authorised connection keeps working.
The Concierge asks for “3-bedroom apartments in La Cala under €500k”. The conversation engine does not care whether the result came from a central SaaS API, the client’s CRM, a WordPress database, XML feed or a signed client-site connector. It receives trusted structured data and carries on the conversation.
Want to see a connected tool in action?
The Property Concierge already demonstrates inventory search, property memory, media retrieval and natural references such as “the second one”.