Demo workspace · Account records are not connected; nothing is submitted.

Agent review

Demo Integrations review: fictional connections and attempts. No account, provider or delivery is changed.

Integrations

Manage accepted-enquiry delivery to your CRM, choose alerts and check recent delivery attempts.

Enquiry alerts

Alerts tell you an enquiry is waiting and when to answer. Buyer contact details stay in Enquiries until you accept. Your in-app notifications remain available whichever alert preference you choose.

Saved alert preference: Email
Platform email: Not configured

Email configuration does not prove a message arrived. WhatsApp alert sending is not available yet, even with a connected account.

Edit alert preference

JavaScript is required for protected connection editing. Loaded connections and delivery history remain readable.

Alert preference

Saving changes the preference for offers and the morning summary. A chosen channel may still be unavailable.

Send a test alert

This sends a real alert using the saved preference. Check your saved preference before confirming; unsaved edits do not change the destination.

Account channels

WhatsAppConnected
SMSRequested
CallingNot connected
E-signatureConnection failed

Channels and sequences

In-app notifications

CRM delivery

Accepted enquiries are sent to your HTTPS endpoint with the buyer details your acceptance opened. Each request is signed. An enabled endpoint is a setting; check delivery attempts for its actual responses.

Saved delivery setting: Paused
Last connection change: 19 Oct 2026, 13:00

https://example.invalid/fictional-crm

Edit CRM address

JavaScript is required for protected connection editing. Loaded connections and delivery history remain readable.

CRM endpoint, starting with https://

Saving the address enables deliveries, including when the connection is paused. An existing connection keeps its signing secret. Refresh after acknowledgement to check the saved setting.

Signing secret

Your CRM uses this private value to verify request signatures. Update your CRM whenever you replace it.

Send a CRM test

This sends a real request to the saved address, including when deliveries are paused. A test contains no enquiry or buyer contact. It does not test accepted-enquiry routing.

Resume deliveries

Future accepted enquiries can be delivered again. This does not replay earlier enquiries.

Replace signing secret

Your CRM will need the new secret before it can verify subsequent requests.

Remove CRM connection

Remove the saved endpoint and signing secret. Previously recorded delivery attempts remain in the history.

Recent delivery attempts

The latest 20 loaded attempts, in Dubai time. A successful HTTP response confirms endpoint acceptance, not a completed CRM workflow or a buyer outcome.

Accepted enquiry503 - Failed
19 Oct 2026, 15:00
Enquiry reference 44444444-4444-4444-8444-000000000002
CRM test204 - Accepted
18 Oct 2026, 14:00
No enquiry attached.
CRM testNot reached
17 Oct 2026, 13:00
No enquiry attached.

Delivery format and signature

One HTTPS POST with JSON and two headers: X-PropRealm-Event and X-PropRealm-Signature. The signature is sha256= followed by the HMAC-SHA256 of the exact body in hex, using your signing secret. Respond with a 200-299 status within eight seconds. Tests carry no enquiry or contact.

{
  "event": "enquiry.accepted",
  "sent_at": "…",
  "enquiry": {
    "lead_id": "…", "received_at": "…", "campaign": "…", "area": "…", "language": "…",
    "budget": "under_1m | 1m_2m | 2m_5m | 5m_plus | undisclosed",
    "timeline": "now | three_months | six_months | later | undisclosed",
    "financing": "cash | mortgage_preapproved | mortgage_needed | undisclosed",
    "intent": "strong | moderate | light | unknown"
  },
  "contact": { "name": "…", "phone": "+971…", "email": "…", "message": "…" }
}