Use case
Amarnex for Notaries and Transaction Service Providers
Coordinate property transaction formalities through a secure, auditable service pipeline.
How this tenant works
The notary or service provider keeps its users, professional credentials, legal working notes, templates, identity controls, and unrelated cases inside its own tenant. A controlled pipeline is created for each referring developer, broker, transaction, or authorized service category.
Customer and partner interactions
- 01
Referral intake, parties, authority, identity, consent, and conflict or eligibility checks where required.
- 02
Document checklist, missing-item requests, draft review, corrections, and readiness confirmation.
- 03
Appointment booking, reminders, secure communication, attendance, signing, witnessing, or attestation steps within legal authority.
- 04
Fee or payment status where applicable, completion evidence, copies, registration handoff, and case closure.
- 05
Questions and status updates shared with authorized parties without disclosing privileged or restricted information.
Shared pipelines between tenants
The referring tenant shares the minimum transaction, party, property, appointment, and document information authorized for the case. The provider returns checklist status, requests, appointment progress, approved documents, completion, and next steps. Professional credentials, private notes, identity evidence, and unrelated matters remain restricted.
Sharing principle
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 catalogReferral and Case Management
Organize cases by referring tenant, transaction, service, status, and deadline.
Document Checklists and Secure Exchange
Coordinate required files, versions, missing items, and approved copies.
Appointments, Tasks and Notifications
Schedule parties, reminders, responsible users, and next actions.
Approvals, Signatures and Audit Trail
Track authorized review, signature, attestation, and completion events where legally supported.
Shared Transaction Pipelines
Give developers and brokers a permissioned view of service progress.
Recommended features
Browse the feature catalog- Case-specific roles and field permissions.
- Identity and document-status checkpoints.
- Appointment coordination and reminders.
- Controlled document requests and exchange.
- Status, deadline, task, and escalation tracking.
- Completion evidence and immutable activity history where supported.
- Arabic-first workflows for KSA with adaptable UAE and Egypt processes.
Example connected journey
- 01
A broker or developer refers a transaction.
- 02
The provider receives approved case details.
- 03
The provider checks the required documents.
- 04
The provider requests missing items.
- 05
The provider coordinates the appointment.
- 06
The provider records authorized completion steps.
- 07
The provider returns status and evidence to the referring pipeline.
Business benefits
- Fewer incomplete files and appointment delays.
- Clear status for customers, brokers, and developers.
- Reduced manual follow-up across organizations.
- Better auditability and controlled disclosure.
- Protection of professional credentials and restricted case information.
Why this configuration matters
Property transactions involve many parties and sensitive documents. A shared pipeline provides reliable coordination while preserving professional independence, confidentiality, and legal responsibility.
Governance and rollout
Start with the pipeline stages, information ownership, sharing rules, service levels, and success measures agreed by the participating tenants. Configure the required modules, train each team for its role, and review performance without exposing unrelated tenant data. Availability of each module, connector, AI capability, and automated action remains subject to the purchased scope, local requirements, and implementation validation.
Other use cases
Design Your Tenant Workflow
Confirm stages, information ownership, sharing rules, and the modules this tenant needs.