You add AI to a property management company by putting a conversational agent in front of the rental enquiry. It asks what your guest card asks, one question at a time, types the answers into a structured record, and posts that record to your property management system the moment it is complete.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A stranger, on a phone, from a listing site, almost always outside office hours.
What it costs today
A voicemail nobody returns until morning, an ILS form with three fields, or an answering service that cannot answer a single question about the home.
What it has to produce
A complete guest card: which home, when they need it, how many people, pets, how the rent is covered, and a number that will be answered.
73%
of one operator’s 839 rental enquiries arrived outside regular business hours
Respage
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Identity on the guest card |
| phone | phone | Yes | How the coordinator calls back |
email | — | Listing details and confirmations | |
| home_of_interest | text | Yes | Which listing, in their words |
| desired_move_in | text | Yes | Matches them to what is actually turning |
| household_size | number | Yes | Occupancy, asked as a total and never as a family question |
| pets | text | — | Pet policy, with assistance animals recorded as not pets |
| income_source | text | — | How rent is covered, recorded and never assessed |
| wants_tour | boolean | — | Routes straight to the viewing queue |
And what it will not do
Collected data
412 collected31 this week6 need attention
Export CSVTasha Boyd
Captured 2h ago · Cedarline Rental Enquiry · joina.chat
Captured data 7 of 8 fields
From the conversation
“The two bed on Alder Street, is it still free? Beginning of next month ideally, there’s two of us and a dog and I work at the hospital.”
Every value keeps the sentence it came from, and a value the visitor never said is never stored. A Gnosari cannot quote itself into your data.
From here a record can go straight on to Slack, a sheet, a Zap or your own API. The inbox is where you read them, not where they get stuck.
Signed headers
Body
{
"type": "data.collected",
"event_id": "1b6f9c02-4d1a-4f7e-9b3c-2a5e8d0f1c44",
"created_at": "2026-08-11T09:14:22Z",
"payload_version": "v1",
"data_kind": "Rental enquiry",
"record_id": 1234,
"attributes": {
"full_name": "Tasha Boyd",
"phone": "+1 503 555 0172",
"home_of_interest": "Alder Street, 2 bed",
"desired_move_in": "Start of next month",
"household_size": "2",
"pets": "One dog, medium"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when someone corrects something.
Signed, so you can trust it
Standard Webhooks HMAC-SHA256, with webhook-id, webhook-timestamp and webhook-signature on every request. Verify before it writes to a guest card.
Quotes are opt-in
The provenance block, the enquirer’s verbatim words, is absent unless you turn it on for that destination.
Zapier or Make
Paste a Catch Hook URL into your Gnosari destination, then point the Zap at your property management system.
Free tier, no app to install, and it fires the moment the guest card is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The coordinator sees the enquiry before the office opens.
Your own endpoint
Give us an https address, verify the signature, write the guest card yourself.
A few lines of code, and the delivery log tells you when something did not land.
And you can see every attempt
| When | Event | Outcome | Detail |
|---|---|---|---|
| 21:07:44 | data.collected | Delivered | 200 OK |
| 21:07:41 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 18:22 | data.updated | Delivered | 200 OK |
| Yesterday 09:15 | data.collected | Delivered | 200 OK |
Every attempt is kept, newest first, with the reason when there is one. Failures retry on their own, and the signing secret lives in your dashboard so you can rotate it without calling anybody.
These are examples, not a partner list. AppFolio, Buildium, Yardi, RentManager and DoorLoop are all reachable the same way: through a Zap, or straight to an endpoint you control. If it takes an HTTP request, it takes the guest card.
A button in the corner that opens into a conversation. Your logo, your colours, sitting on the pages you already have.
No chat window and no widget. Your headline leads, the thread sits under it, and it reads like you asked rather than like software collecting.
Every screen on this page is a published Gnosari, embedded from the app. Type into any of them.
display_mode="bubble" A floating button in the corner. Opens over your page and closes again. The default, and the one nobody has to be taught.
Four corners to choose from
display_mode="sidebar" A fixed panel down one side, always open. For pages where the conversation is the point rather than an aside.
Left or right, any width
display_mode="sidebar-push" The same panel, but your content moves over to make room instead of being covered. Nothing on the page is ever hidden.
Left or right, any width
display_mode="drawer" Slides in over the page when it is called, then slides away. The middle ground between a bubble and a sidebar.
Left or right
01 · A link you send
Put it in an email, a text, a booking confirmation or a signature. Each link carries its own opening line and headline, and counts its own visits, so you can tell which channel actually worked.
02 · A code they scan
Every link comes with a QR. On a table card, a receipt, a delivery note, a door. Someone points a phone at it and the conversation starts, with no app and no typing.
03 · A flyer you hand over
A builder for the printed thing itself. Pick a template, restyle it, edit the words on the page and export a print-ready poster or card with the QR already placed.
Twelve curated looks, each a colour and a background pattern chosen to go together. Pick one and you are done.
22 colour themes and 44 background patterns, each drawn in code at four intensities. That is 3,872 combinations before you touch a single token.
22 colour themes
44 background patterns
Every pattern, four intensities
Exact hex values, fourteen fonts, bubble shape per side, corner radius, density, header and input. Explicit tokens always win over the preset. Two chats can share every line of markup and still wear two different brands: only the tokens differ.
A boutique hotel
A developer tool
fontFamily accepts fourteen faces
Set with one call, or one click in the designer. Changing it later takes the same one call, and every published surface updates at once.
| What changes | Voicemail and a callback | ILS or website form | Gnosari |
|---|---|---|---|
| At 9pm on a Sunday | Rings out | Sits in an inbox | Answered, typed, delivered |
| What you get back | A name and a number, if that | Three fields | The whole guest card |
| Missing answers | You call and ask | Submitted as-is | It asks a follow-up |
| Gets into your PMS | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it is complete |
| Fair housing | Depends who answered | Whatever the form asks | The same questions every time, protected classes never asked |
| Where the answer came from | Someone’s memory | The field | The verbatim sentence, kept |
Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.
Gnosari runs the guest card a leasing office would otherwise fill in by phone during office hours: move-in date, budget range, bedrooms, pets, occupants as a total number, and how to reach the prospect. It asks one question at a time on your listings or through a link, then posts a typed guest card to your property management system. Your leasing agent opens a complete card the next morning.