Use case
Amarnex for Real Estate Brokers
Run one independent brokerage tenant while collaborating with every developer you represent.
The broker keeps its own brand, users, social-media credentials, lead sources, customer history, and internal analytics. It creates a separate, controlled pipeline for every developer and project, sharing only the information that developer is authorized to see.
Customer interactions
- 01
Lead generation from the broker’s campaigns, social accounts, portals, referrals, events, and inbound channels.
- 02
Calls, SMS, email, chat, qualification, property discovery, viewing schedules, and follow-up.
- 03
Matching prospects to approved inventory, offers, reservations, documents, finance options, and contracts.
- 04
Developer coordination, customer questions, commission milestones, after-sale handoff, repeat buyers, and referrals.
Shared pipelines between tenants
Each shared pipeline exposes only approved records, fields, stages, documents, tasks, and performance indicators to named counterpart tenants. Every tenant keeps its own users, credentials, social-media accounts, communication channels, internal notes, and unrelated customer data. Permissions, ownership, edit rights, expiry, and audit history are configured for every relationship.
Recommended modules
Browse the module catalogBroker CRM and Lead Management
Own the brokerage database across all developers.
Multi-Developer Pipelines
Separate stages, permissions, inventory, targets, and reporting.
Campaign and Channel Management
Capture leads while keeping credentials private.
Inventory and Matching
Guide buyers using authorized project information.
Communications
Preserve call, SMS, email, and chat continuity where enabled.
Documents, Offers and Reservations
Coordinate transaction steps.
Performance and Commissions
Share agreed results and track commercial milestones.
Recommended features
Browse the feature catalog- Private broker-wide customer profile and consent history.
- Developer-specific permissions and shared dashboards.
- Lead routing by project, location, budget, source, and agent.
- Viewing, offer, reservation, document, and follow-up checklists.
- Conversion reporting by developer, project, agent, and source.
Example journey
- 01
The broker captures a lead through its own Instagram campaign.
- 02
The broker qualifies the buyer.
- 03
The broker opens the relevant developer pipeline.
- 04
The broker shares approved opportunity fields.
- 05
The broker coordinates viewing and reservation.
- 06
The full cross-developer relationship stays inside the broker’s private tenant.
Benefits and why
The model protects the broker’s brand, credentials, users, customer relationships, and cross-developer intelligence while giving each developer transparent performance for its own opportunities. It reduces spreadsheet reporting, improves response discipline, and makes commissions and service handoffs easier to follow.
Governance and rollout
Confirm stages, information ownership, sharing rules, service levels, success measures, purchased modules, and local requirements before implementation. Feature availability remains subject to the contracted scope and technical validation.
Other use cases
Design Your Tenant Workflow
Confirm stages, information ownership, sharing rules, and the modules this tenant needs.