Answers and guides for choosing and using X-OPP

Leads can be captured from agreed digital sources and assigned through configured routing rules.

The system compares recorded client requirements with available project or property data. Agents must confirm current availability, pricing and suitability before presenting options.

Yes. Activity, stage movement, overdue actions and conversion measures can be shown by agent or team.

Availability depends on the source and refresh process agreed with the developer or inventory owner. Users should confirm current details before advising a client.

Yes. Separate record structures and verification workflows can be configured for both inventory types.

Search and comparison views can use fields such as location, price, payment plan, handover and property type.

Yes. The rollout can begin with the highest-priority processes and expand after workflows, permissions and reporting are confirmed.

The platform can be configured for company, branch and group structures, subject to the agreed implementation scope.

Approval stages, limits, roles and escalation rules can be configured around the approved business process.

Connected events such as a new lead, lease expiry or reporting exception can create tasks when the integration and rule are configured.

Yes. Repeating operational, compliance and reporting work can use approved templates and schedules.

Workload views can show assignments, due dates, status and capacity indicators using the available data.

Shift, attendance and schedule structures can be configured around the organisation's operating model.

Payroll scope depends on the approved setup. The platform can organise payroll inputs and, where configured, support payroll processing and reporting.

Employee and manager request workflows can be provided with approval status and balances where included.

Yes. Property, unit, lease and billing structures can be configured for different asset types.

Payment schedules can record cheque, transfer or other agreed payment details and show due and collection status.

A request channel and internal assignment workflow can be configured as part of the implementation.

Company, branch and consolidated reporting structures can be configured within the agreed implementation scope.

The platform can connect property, lease, commission and project activity with accounting workflows based on the approved design.

Yes. Connected modules can share approved master data and operational transactions with finance.

It can be configured for different healthcare settings. The final scope should be confirmed through a workflow and compliance review.

Yes. Location-based access, activity views and group reporting can be configured for multi-branch operations.

Appointment scheduling, queue coordination, reminders and staff views can be included in the agreed setup.

No. It structures the data and calculation process. The healthcare provider remains responsible for source accuracy, methodology approval and final submission.

Yes. Cost centres and allocation sequences can be configured around an approved step-down methodology.

Common drivers include headcount, floor area, devices, encounters and service activity. The correct driver depends on the cost and methodology.

No. It supports general multi-brand marketing, with additional value when connected to real estate project and inventory data.

Publishing connections depend on the selected channels, permissions and final integration scope.

Yes. Content briefs, creative files, reviewers, status and approval history can be structured in the workflow.

The connection scope depends on available APIs, exports, data quality and access permissions. Delemon confirms this during discovery.

Yes. Views can be configured by role, department, company, branch or other approved access rules.

Recurring reports and management summaries can be scheduled for the relevant recipients.