Integrations

• Property listing source. If property details come from another system, map the stable property code, address and USD asking price. App Administrator owns the resulting listing and owner-consent information.
• Viewing coordination. Agree the authorized reservation action and any external calendar connection used by the brokerage. Preserve the property, agent and opportunity references, along with the viewing window and hold expiry.
• Customer evidence source. Arrange how proposal documents, acceptance evidence and useful communication outcomes reach the opportunity. Choose attachment visibility deliberately and keep the intended customer relationship explicit.
• Transaction-completion services. Connect the external procedures used after a commercial outcome where needed. Agree what downstream confirmation is required for a compensating action, and retain it with the relevant operation evidence.

Assign an owner to each handoff and use the pilot opportunity to rehearse it. An external reference must identify the actual result being claimed. A property address, customer name or current stage alone cannot establish that a particular operation succeeded.

Preserve the action’s operation identity and expected revision when handling repeated requests. If the response is uncertain, investigate the original receipt before issuing another effect. Reconciliation compares existing local evidence; it does not replay the commercial action to make the earlier claim true.

Viewing setup must preserve the configured access boundaries. Sales Manager can inspect stored reservations, while Relationship Owner uses the authorized visit path. Agree any required action access before widening the operating scope.

Customer acceptance and transaction completion remain separate events. The reviewed CRM outcome keeps its evidence, while any downstream correction waits for the confirmation required by that connected process. Rehearse those boundaries during implementation.