Enquiries and approval
Where enquiries arrive, how the agent prepares replies, and why nothing leaves without your yes.
Where enquiries arrive
Every enquiry lands in /anfragen: the list on the left, the thread on the right. Each enquiry shows where it came from:
- from searchers with an Athaus account,
- through the form on the listing page, without an account (Website),
- from ChatGPT, Claude or another AI assistant through the MCP server Athaus Immobiliensuche,
- through a viewing's booking link.
An enquiry's status is one of: New, In conversation, Viewing, Accepted, Declined.
Enquiries without an account
On a listing page on www.athaus.ai anyone can contact the provider directly: name, email address, phone if they like, message. Before that they explicitly agree:
I agree that Athaus passes my name, email address, phone number (if given) and message to the provider of this listing so that they can reply to me.
The consent is stored with its version, language and wording. Your reply goes to the person by email; if they answer, their mail lands in your own mailbox.
Someone with an account who sends an enquiry releases their name, contact details and folder to that provider, and can withdraw that later in the enquiry.
Approval at the boundary
What stays in-house, the Athaus agent does on its own: sorting, filling in, setting the status, writing drafts. What leaves Athaus waits for your yes.
- The draft sits ready in the reply field, marked as a draft by Athaus. Sending means yes.
- On the start page, the tab To approve collects all drafts. Depending on the kind it offers Approve and send, Apply (for something that stays in-house) or Approve and publish (for a social media post).
- Approve only appears once the whole text is visible.
- A morning email around 7 am lists the new suggestions.
What the agent prepares that goes out: replies to enquiries, follow-ups (only where Athaus sees the reply), news about the property such as a price drop, rejections, the message after a viewing, posts and replies on social networks.
You set how far the agent may go on its own, per kind: automation levels. The same boundary applies over MCP (when a click is needed).