Back to CapabilitiesOverview

Languages, training and delivery

Arabic/English interfaces, RTL delivery, handover material, training and support.

Arabic / EnglishAudit logsFlexible hostingTraining and handover

Next step: a short fit check to confirm path, scope and first deliverables.

Platform preview

Government operations platform

Illustrative view

Signal 1

247 requests

Signal 2

31 overdue

Signal 3

96% auditable

Citizen service request

CS12:42Review
68%

Directorate approval

DG11:15Escalated
44%

Security site report

SEC09:55Active
81%

Performance trend

Audit log retained
Role model active
Report export ready
Page summary

Languages, training and delivery

Arabic/English interfaces, RTL delivery, handover material, training and support.

Product path

Capabilities

Best first scope

One service, approval chain or dashboard

First deliverable

Scope brief, roles, outputs, acceptance criteria and handover path

Best next step

Short fit check or formal requirements review

Start the conversation

Start with a short institutional briefing

No public project names are required in the first contact. Choose the closest path, then turn the discussion into a pilot brief, technical pack or tender invitation.

30-minute briefingReviewable scope briefTechnical or procurement packTraining and handover path

Next outputs: role confirmation, 30-minute briefing, workflow selection, scope brief, then technical or procurement pack.

Fast first request

A short intake that routes the request to the right path. Details can be completed later through a formal meeting or tender documents.

Confidential discussions are available under NDA. No reference or organization name is published without written approval.

Only 4 fields are visible first. Open optional routing details when needed.

We use these details to route the request internally. Do not send sensitive documents or public project names in the first message.

Optional routing detailsOptional

These details help route the request, but they are not required for the first reply.

Languages and interface readiness

Two clear delivery languages: Arabic and English

Core-Intel supports Arabic and English interfaces, Arabic RTL experience and handover material that can be used by daily users, technical teams and leadership.

Arabic

For daily interfaces, manuals, training, notifications and government-side review.

English

For technical proposals, delivery documentation, IT teams and executive or supplier review.

RTL-ready delivery

Arabic interfaces are planned with right-to-left layout for forms, menus, dashboards and content.

Bilingual handover and training

Training and handover material can be prepared in Arabic with English support where technical review needs it.

About Us

Technology built around real Iraqi operations

Core-Intel is a technology company based in Najaf, Iraq. We design and deliver systems that help institutions manage requests, documents, staff, payments, approvals, reporting and communication from one secure digital foundation.

Process-first delivery model

Process-first delivery model

1

Arabic and English interfaces

Arabic and English interfaces

2

Support and monitoring model

Support and monitoring model

SLA

Training & Handover

Teams can operate the platform after launch

Core-Intel prepares the people who will use, manage, monitor and maintain the platform, so the organization is not dependent on informal knowledge after delivery.

Admin training

User roles, permissions, configuration, service queues, content updates and basic troubleshooting.

Employee training

Daily workflows for receiving, reviewing, assigning, approving, reporting and communicating around cases.

Management training

Dashboard use, report interpretation, SLA follow-up, workload visibility and decision support.

Technical team handover

Hosting model, environments, backups, monitoring, access rules, deployment notes and support responsibilities.

Support Model

Structured support after launch

Core-Intel supports production systems with clear support hours, monitoring expectations, maintenance planning, incident handling and reporting.

Business hours support

Standard support for questions, user issues, configuration help and operational follow-up during agreed working hours.

Critical monitoring options

Critical production systems can include agreed monitoring for availability, health checks and urgent service risks.

Maintenance windows

Planned update windows for fixes, improvements, security updates and infrastructure changes.

Incident response

Defined response process for urgent issues, service interruptions, access problems and production defects.

Monthly reporting

Monthly operational summaries covering incidents, uptime, support activity, improvements and recommended next steps.

How We Work

Define scope, validate delivery, then expand

For government and enterprise environments, the appropriate path is a controlled pilot with measurable outputs, review points and a formal expansion decision.

Process discovery

We map the current paper, office and communication flow to identify delays, risks and manual work.

Pilot design

We select one service or department, define roles, forms, approvals, reports and success criteria.

Build and integrate

We deliver the portal, dashboard, workflow, storage, notifications and integrations required for the pilot.

Train and operate

We train the team, monitor usage, fix bottlenecks and prepare the system for wider rollout.

Next decision route

Three clear actions instead of a generic contact request

Choose the action that matches the organization's current stage.

Contact

Request a briefing

Arabic/English interfaces, RTL delivery, handover material, training and support.