# Which MoxiWorks referrals become signed listings? Canonical: https://hivesilo.com/integrations/moxiworks Reviewed: November 2026 Connection: proposed; scope agreed with the customer. A client in another market wants a listing consultation. One agent knows the client and another knows the neighborhood. HiveSilo helps the brokerage trace that introduction to an attended appointment and a signed instruction while both offices retain their own relationship records. [Contact HiveSilo](https://hivesilo.com/contact?hs_source=moxiworks--hero--contact#contact) [Explore the fit](https://hivesilo.com/integrations/moxiworks#solution) Start with a conversation. No client records needed. One introduction. A known outcome. [Your client list stays yours.](https://hivesilo.com/integrations/moxiworks#privacy) [The value](https://hivesilo.com/integrations/moxiworks#solution) [AI control](https://hivesilo.com/integrations/moxiworks#governance) [Your data](https://hivesilo.com/integrations/moxiworks#privacy) [What you could gain](https://hivesilo.com/integrations/moxiworks#results) [Let’s talk](https://hivesilo.com/integrations/moxiworks#fit) [FAQs & evidence](https://hivesilo.com/integrations/moxiworks#evidence) ## A promising referral can disappear between offices. MoxiWorks supports the agent’s marketing and CRM. The originating office may still lack the result of an introduction it made. **Did the receiving office win the listing?** A referring agent may see a presentation go out while the receiving office holds the appointment and the listing agreement. Without an agreed handoff and a verified outcome, both offices can count the same opportunity, or neither can explain what it produced. MoxiWorks offers brokerage marketing, presentations and CRM. MoxiEngage supports relationship campaigns and sales stages. RISE adds native AI-guided workflows. The decision here is whether a particular referral source earns another investment once the receiving office confirms the result. A MoxiWorks review starts with the edition installed and the rights each participating office and agent can grant. [[M1]](https://hivesilo.com/integrations/moxiworks#source-M1) [[M2]](https://hivesilo.com/integrations/moxiworks#source-M2) [[M3]](https://hivesilo.com/integrations/moxiworks#source-M3) [[M4]](https://hivesilo.com/integrations/moxiworks#source-M4) [[M6]](https://hivesilo.com/integrations/moxiworks#source-M6) ## Follow the referral to a business outcome. Give the referring agent a disposition, give the receiving agent ownership and give the broker a fair comparison of referral sources. [Talk through your use case](https://hivesilo.com/integrations/moxiworks#fit) **Who owns the introduction?** Ask the referring agent to confirm the client’s permission and the receiving office to accept the handoff. An existing exclusive relationship takes precedence. **Which result counts?** Use the attended consultation and signed listing agreed by the receiving office. Keep open opportunities separate from confirmed withdrawals. **Should the brokerage invest again?** Compare signed contribution after referral fees for mature referral groups. A market with delayed closings deserves a longer observation period. **See the intelligence behind the next move** ### Recover a stalled introduction. Revenue Seeker can surface an accepted introduction with no recorded appointment. The referring agent checks whether a conversation has already happened before nudging the other office. [[M1]](https://hivesilo.com/integrations/moxiworks#source-M1) [[M2]](https://hivesilo.com/integrations/moxiworks#source-M2) Useful output: An exception for the relationship owner to review. ### Compare referral sources. Use figures approved by both offices to connect origin, appointment, listing and contribution after fees. Keep unresolved referrals visible and avoid giving one source credit for another office’s prior relationship. Useful output: A source comparison for the broker and marketing director. ### Protect the agent’s sphere. Let each agent confirm what may be shared. The broker can review aggregate outcomes while private address books and identifying notes stay within the office that controls them. [[M3]](https://hivesilo.com/integrations/moxiworks#source-M3) [[M6]](https://hivesilo.com/integrations/moxiworks#source-M6) Useful output: An aggregate brokerage report with local relationship details. **One coastal referral, two offices and one listing decision.** An agent asks a colleague in a coastal market to arrange a listing presentation. The receiving office already knows the household. Both offices report a potential new listing. ### Start with MoxiWorks MoxiWorks can support the agents’ CRM work and presentations. The receiving office owns the calendar and signed listing outcome in this example. ### Bring the relevant context together - A permitted referral reference and the accepting office - The attended presentation and signed instruction confirmed by the receiving office - Customer-approved referral fee and net brokerage contribution ### Make the decision If the original agent introduced a genuinely new opportunity, credit the referral. If the receiving office already had an active engagement, keep that attribution. Leave unresolved matches out of the budget calculation. ### A useful output One disposition for the referral and a source-level contribution entry without duplicate credit. ### Keep responsibility clear The receiving broker confirms the listing. The originating broker approves a change to marketing spend. #### Hold and ask If permission, referral ownership or exclusive representation is disputed, return the case to both brokers before assigning credit or contacting the client. #### Record the outcome Measure referral acceptance, attended consultations, signed listings, net contribution and unmatched share over the same reporting period. [[M1]](https://hivesilo.com/integrations/moxiworks#source-M1) [[M2]](https://hivesilo.com/integrations/moxiworks#source-M2) ## Require control before AI acts. An introduction belongs to the agents and client who agreed to it. Both offices can review the business outcome while controlling who can act on it. If one office disputes the source, pause credit assignment and any new follow-up. The brokers resolve ownership before the next spend review. - 1 ### Request An AI proposes an action - 2 ### Check Policy and authority - 3 ### Approve Named owner, when required - 4 ### Act Within permitted scope - 5 ### Record Keep the action, outcome and accountable owner traceable. Unclear authority? Hold the action. Resolve with the named, authorized owner before proceeding. Controls apply to actions routed through the configured HiveSilo boundary. **Read the governance and escalation requirements** Make accountable authorization a condition of putting AI to work. HiveSilo describes an operating layer that combines buyer intelligence, customer-data privacy and governance. Your deployment should establish the responsible owner and permitted scope before an agent can change records, contact buyers or trigger campaigns. HiveSilo documents policy checks before execution, default denial when authorization is unclear, human checkpoints, scoped stop controls and decision receipts. These controls apply to actions routed through its policy boundary. Keep decisions, required approvals and held actions traceable as the workflow progresses, then record the action, outcome and accountable owner. [[HS6]](https://hivesilo.com/integrations/moxiworks#source-HS6) [[HS7]](https://hivesilo.com/integrations/moxiworks#source-HS7) **Who** Identify the acting agent or person and name the business owner accountable for this workflow. **What** Define the action and permitted data categories before execution. **Where** Specify the approved system, destination and customer custody boundary. **How** Require an approved execution path, access scope and applicable policy checks. **When** Set the permitted conditions and approval validity; recheck authority before a held action resumes. **Why** Record the business purpose and the basis for allowing, denying or holding the action. ### An edge case should stop the affected action. For the deployment, require unresolved authority, an unapproved destination or an out-of-policy action to remain on hold. A timeout or unanswered approval request must not become permission to proceed. ### Who gets the question? Agree a named owner and authorized delegate for each workflow. A proposed responsibility model is: sales for buyer outreach and lead handling; marketing for campaign spend and audiences; security or privacy for data-access exceptions; the platform owner for connector or runtime changes. Test the escalation route. If no authorized reviewer is available, keep the action held. Named-owner routing is configured and demonstrated for each deployment. Governance covers actions routed through its configured boundary; external systems remain responsible for actions outside that scope. ### Make responsibility part of the AI rollout. Use the AI implementation layer to put policy checks, approval checkpoints and decision records around the actions in scope. Your enterprise agreement defines the legal responsibilities and any agreed liability allocation or transfer. [[HS7]](https://hivesilo.com/integrations/moxiworks#source-HS7) [[HS10]](https://hivesilo.com/integrations/moxiworks#source-HS10) [Explore the AI implementation layer](https://hivesilo.com/ai-implementation-layer) · [How enterprise agreements govern the engagement](https://hivesilo.com/terms) ## Your client list stays yours. The brokerage can reconcile the referral inside the authorized office. Contact details, private notes and agreements stay there. [Explore the security architecture](https://hivesilo.com/security-architecture) Your client records stay with your business under HiveSilo’s published architecture. **How your data stays under your control** Agent contact records and referral joins stay inside the brokerage-controlled environment. Exchange only approved, non-identifying disposition signals. Require agreement on office and agent authority before any matching, and withhold small groups that could reveal a relationship. [[M1]](https://hivesilo.com/integrations/moxiworks#source-M1) [[M2]](https://hivesilo.com/integrations/moxiworks#source-M2) [[M3]](https://hivesilo.com/integrations/moxiworks#source-M3) [[M4]](https://hivesilo.com/integrations/moxiworks#source-M4) [[M6]](https://hivesilo.com/integrations/moxiworks#source-M6) [[HS4]](https://hivesilo.com/integrations/moxiworks#source-HS4) ### Your controlled environment Office-controlled referral and listing records Identities and re-identifiable records stay here. Your enclave. Your keys. Only permitted non-PII signals and scores Approved referral and disposition counts ### HiveSilo intelligence HiveSilo context for signed contribution No customer identity transfer to HiveSilo. Published architecture. Confirm the data boundary for your deployment. ### Customer-controlled keys Documented BYOK options cover AWS, Azure and GCP. Review key ownership, revocation and the deployment's access policy with your security team. [[HS3]](https://hivesilo.com/integrations/moxiworks#source-HS3) ### Protected processing The architecture describes confidential computing and trusted execution environments. Request deployment-specific attestation and data-flow evidence for your CISO's review. [[HS3]](https://hivesilo.com/integrations/moxiworks#source-HS3) ### Scoped destinations and actions Agree which systems receive outputs and what actions are authorized. Keep identity handling within the documented customer boundary. [[HS2]](https://hivesilo.com/integrations/moxiworks#source-HS2) [[HS4]](https://hivesilo.com/integrations/moxiworks#source-HS4) ### Control through the full relationship Review permitted use, export, retention, deletion and offboarding terms. Customer-controlled keys are one control; they do not establish every contractual exit right. [[HS3]](https://hivesilo.com/integrations/moxiworks#source-HS3) [[HS4]](https://hivesilo.com/integrations/moxiworks#source-HS4) Only approved, non-identifying source and outcome signals can cross into HiveSilo’s intelligence service. Small groups may still identify a client. Combine or withhold those figures before sharing them. Evaluate the native CRM, presentations and RISE workflow before proposing another agent action. [[M1]](https://hivesilo.com/integrations/moxiworks#source-M1) [[M2]](https://hivesilo.com/integrations/moxiworks#source-M2) [[M3]](https://hivesilo.com/integrations/moxiworks#source-M3) [[M4]](https://hivesilo.com/integrations/moxiworks#source-M4) [[M6]](https://hivesilo.com/integrations/moxiworks#source-M6) Customer identity custody is separate from HiveSilo account, billing and support records. Re-identifiable pseudonymous data is not anonymous. ## What you could gain. Measure whether confirmed introductions lead to signed business, how often a second office receives duplicate credit and what the brokerage earns after referral fees. These are evaluation measures for the proposed use case. [Explore HiveSilo case studies](https://hivesilo.com/case-studies) [Contact HiveSilo](https://hivesilo.com/contact?hs_source=moxiworks--results--contact#contact) ### Sharper scoring. Clearer intent. 3,790 of 5,000 · UHNW buyer score Illustrative score Give an agent a reason to review an introduction while leaving the client’s intent for the conversation. ### Find more clients like your best. 4–6× · Reported conversion lift Closed-revenue outcomes Compare spend with the value retained from mature referral groups. ### Put more of your budget to work. Up to 31% · Reported ad-spend savings Bot and invalid-traffic filtering Find stalled handoffs and separate them from a genuine loss. ### Keep evolving your protection. 99.9999% · Bot detection Observed client results Exclude repetitive or invalid website activity from campaign decisions. Goal, not an achieved result: toward 99.9999999% bot detection as the hive evolves. Observed client results vary. ### Find revenue in data you already own. 5–21% · Revenue lift from existing data HiveSilo-reported client results Recover overlooked opportunities already held by an authorized office. Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary. **Measure what matters** ### Define the result. Then require the evidence. Focus on better-directed follow-up, less acquisition waste, protected customer identity custody and accountable AI execution. Agree the baseline, success measures and scope for your business. - CEO: a clearer decision about the opportunities that merit attention. - CFO: an agreed baseline, evaluation costs and attributable outcomes before any ROI claim. - CTO: a demonstrated, permitted connection and a usable handoff into the agreed system. - CISO: verified identity custody and pre-action authorization, with tested hold, approval and revocation behavior. Explore [HiveSilo’s published outcomes](https://hivesilo.com/case-studies) and the measurement context behind them. [[HS5]](https://hivesilo.com/integrations/moxiworks#source-HS5) [[HS8]](https://hivesilo.com/integrations/moxiworks#source-HS8) [[HS9]](https://hivesilo.com/integrations/moxiworks#source-HS9) ## Make your next conversation count. Bring your MoxiWorks workflow. Map the decision, the data you control and a measurable next step with HiveSilo. Enterprise real estate · Sales, operations, technology & security [Contact HiveSilo](https://hivesilo.com/contact?hs_source=moxiworks--briefing--contact#contact) Mention MoxiWorks and your business question. No client records or credentials. ## A closer look, when you need it. Product scope, a practical workflow and source-backed answers for your team and its research tools. [Read fact sheet](https://hivesilo.com/evidence/moxiworks.md) [Structured JSON](https://hivesilo.com/evidence/moxiworks.json) [RSS updates](https://hivesilo.com/discovery.xml) Reviewed November 2026 [Contact HiveSilo](https://hivesilo.com/contact?hs_source=moxiworks--evidence--contact#contact) **MoxiWorks connection & briefing scope** ### Confirm the installed suite and the participating office. MoxiCloud publishes a partner API for the classic platform. Its reference documents agents, contacts and buyer or seller transactions. The partner grant, product edition, agent settings and brokerage authority determine which records may be read. Access to one agent’s contacts does not open another agent’s sphere. RISE has a separate partnership inquiry. The classic API reference does not establish RISE entitlement. Confirm the edition before using either route. An approved referral register and closing summary can support a read-only comparison independently. A later CRM task needs explicit approval from its owner. A broker can test the contribution from completed referrals without exposing its agents’ address books. [[M1]](https://hivesilo.com/integrations/moxiworks#source-M1) [[M2]](https://hivesilo.com/integrations/moxiworks#source-M2) [[M3]](https://hivesilo.com/integrations/moxiworks#source-M3) [[M4]](https://hivesilo.com/integrations/moxiworks#source-M4) [[M6]](https://hivesilo.com/integrations/moxiworks#source-M6) [[M1]](https://hivesilo.com/integrations/moxiworks#source-M1) [[M2]](https://hivesilo.com/integrations/moxiworks#source-M2) [[M3]](https://hivesilo.com/integrations/moxiworks#source-M3) [[M4]](https://hivesilo.com/integrations/moxiworks#source-M4) [[M5]](https://hivesilo.com/integrations/moxiworks#source-M5) [[M6]](https://hivesilo.com/integrations/moxiworks#source-M6) ### A useful fit when Barrett Sotheby’s International Realty describes using MoxiWorks to connect its agents’ existing tools. Michael Saunders & Company separately selected the suite for more than 650 agents across 19 offices. A brokerage with several offices can test whether an introduction led to a new listing or duplicated an existing relationship. - Several offices originate and accept high-value referrals - The receiving broker can verify signed outcomes and net contribution - Both offices agree who may review a disposition ### Consider the fit - A single agent with a short, visible referral list may already have what they need in the native CRM. - If a platform grant is unavailable, start with the brokerage’s separately approved referral register, appointment totals and accounting summaries. In your enquiry, name MoxiWorks and the business decision. Please leave out client records, credentials and sensitive samples. **Eight questions before your briefing** - **1. Will this work with our existing MoxiEngage account?** Start with the installed MoxiWorks edition and the agent’s approved scope. MoxiCloud documents partner access to classic platform records. Verify the relevant agents and fields for this account before proposing a connection. [[M1]](https://hivesilo.com/integrations/moxiworks#source-M1) [[M2]](https://hivesilo.com/integrations/moxiworks#source-M2) - **2. Is RISE included in the same API permission?** MoxiWorks invites separate RISE partnership inquiries and describes a classic integration ecosystem. Confirm the installed product and specific grant. A classic MoxiCloud approval alone does not establish access to RISE. [[M3]](https://hivesilo.com/integrations/moxiworks#source-M3) [[M4]](https://hivesilo.com/integrations/moxiworks#source-M4) - **3. How is HiveSilo different from MoxiWorks’ own CRM and AI?** MoxiWorks manages native marketing, CRM activity and productivity. HiveSilo can compare referral origination with a result confirmed independently by another office, then help a broker evaluate where future acquisition spending belongs. [[M2]](https://hivesilo.com/integrations/moxiworks#source-M2) [[M3]](https://hivesilo.com/integrations/moxiworks#source-M3) - **4. Do brokerage managers see every agent’s contacts?** The public MoxiEngage help describes agent-specific contact visibility. Each office should confirm its operating agreement and obtain the authority required for the selected records. Brokerage-level reporting can begin with aggregate dispositions. [[M6]](https://hivesilo.com/integrations/moxiworks#source-M6) - **5. What if both offices claim the listing?** The receiving broker checks the dates, existing relationship and referral terms with the originating broker. Exclude a disputed attribution from the budget comparison until the offices agree. The client can continue working with the agreed agent. - **6. What evidence would justify changing referral spend?** Compare similar cohorts after enough time for the listings to mature. Count attended consultations, signed listings, referral fees and retained contribution. Report incomplete matches alongside the denominator so a small number of closings does not dominate the decision. - **7. Can a brochure request trigger an automated approach?** A brochure request can inform the responsible agent, who checks the client’s preference and current relationship. A CRM grant is only a technical permission. The broker and agent decide whether to contact the client. [[M1]](https://hivesilo.com/integrations/moxiworks#source-M1) [[M6]](https://hivesilo.com/integrations/moxiworks#source-M6) - **8. What should we bring to a first discussion?** Bring one referral source, the offices that receive it, an agreed definition of a signed listing and aggregate results from a comparable period. Note which office can confirm each result. Client files are unnecessary for this first conversation. **Sources, scope & verification** - [MoxiCloud partner API reference [M1]](https://moxiworks-platform.github.io/api.html) Classic partner API resources, agent and contact scope and restrictions. Reviewed November 2026 - [MoxiWorks real estate CRM [M2]](https://moxiworks.com/solutions/real-estate-crm/) Agent relationship management, brokerage pipeline and ownership. Reviewed November 2026 - [RISE by MoxiWorks [M3]](https://moxiworks.com/rise/) Native AI real-estate marketing platform and brokerage workflows. Reviewed November 2026 - [MoxiWorks partner integrations [M4]](https://moxiworks.com/partner-integrations/) Distinct RISE partnership inquiry and classic-suite integrations. Reviewed November 2026 - [Michael Saunders & Company selects MoxiWorks [M5]](https://moxiworks.com/press/moxiworks-and-michael-saunders-company-announce-strategic-partnership-to-power-brokerages-next-phase-of-growth/) Named luxury brokerage relationship, 650+ agents across 19 offices, and the distinction between a selected platform and active seats. Reviewed November 2026 - [MoxiEngage contact-card sharing [M6]](https://support.moxiworks.com/hc/article_attachments/360000436463) Agent-specific visibility and limited contact card sharing. Reviewed November 2026 - [Barrett Sotheby’s International Realty CRM case study [M7]](https://get.moxiworks.com/hubfs/MoxiWorks/Guides/Q3_2024_MoxiWorks_CRM_Guide.pdf) Barrett Sotheby’s operations director describes the installed MoxiWorks hub and integrations in the guide’s CRM case study. This does not establish API use by the brokerage. Reviewed November 2026 - [HiveSilo: industry coverage [HS0]](https://hivesilo.com) First-party description of buyer intelligence across 12 luxury niches. Reviewed October 2026 - [HiveSilo: platform [HS1]](https://hivesilo.com/platform) Published intent, sales-prioritization and traffic-quality capabilities. Reviewed October 2026 - [HiveSilo: integration scope [HS2]](https://hivesilo.com/integrations) Named destinations, scoped activation and customer-controlled dispatch. Reviewed October 2026 - [HiveSilo: security architecture [HS3]](https://hivesilo.com/security-architecture) Documented confidential processing, BYOK and customer control. Reviewed October 2026 - [HiveSilo: data handling [HS4]](https://hivesilo.com/data-handling) Customer identity custody, pseudonymous-data boundaries and separate account records. Reviewed October 2026 - [HiveSilo: published outcomes [HS5]](https://hivesilo.com/case-studies) Existing first-party outcomes material, with client-reported and illustrative descriptions. Reviewed October 2026 - [HiveSilo: AI agentic governance [HS6]](https://hivesilo.com/ai-agentic-governance) Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts. Reviewed October 2026 - [HiveSilo: AI implementation layer [HS7]](https://hivesilo.com/ai-implementation-layer) Published combined implementation model for intelligence, confidential processing and AI governance. Reviewed October 2026 - [HiveSilo: bot-detection results and buyer-score specimen [HS8]](https://hivesilo.com/) The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen. Reviewed October 2026 - [HiveSilo: owned-data revenue result briefing [HS9]](https://hivesilo.com/contact?hs_source=moxiworks--evidence--contact#contact) HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows in October 2026. Reviewed October 2026 - [HiveSilo: enterprise agreements and responsibility [HS10]](https://hivesilo.com/terms) Signed enterprise agreements govern the engagement and take precedence over website summaries. Reviewed October 2026 Vendor sources describe their own product. The workflows on this page describe a HiveSilo application, scoped to customer permissions, contracts and the selected product edition. HiveSilo’s reported outcomes retain their original measurement context; the illustrative score and future bot-detection goal are identified in the outcomes section. Independent HiveSilo use-case page. MoxiWorks is identified to explain the workflow; no endorsement, certification or partnership is implied. Your next move starts with a conversation. [Contact HiveSilo](https://hivesilo.com/contact?hs_source=moxiworks--closing--contact#contact)