SAMA / 01 / PRODUCT STUDIO

Implemented custom product

Sama Scan Control Center

Every request has a path.
Every follow-up has an owner.

An Arabic workspace connecting examination requests with contacts, appointments, and follow-ups. It brings website enquiries into a structured reception and operations workflow.

Reception, center managers, relationships and marketing teams
SAMA / 01 / WORKSPACEDemonstration interfaceSama Scan Control Center — Demonstration interface
Actual product interface rendered with labelled demonstration data.

01 / WHY THIS PRODUCT

One connected request record. A clear next step for the team.

A website request may be scheduled and followed up through several channels. A connected record helps staff see its owner and next action, and distinguish a pending request from a confirmed appointment.

  1. 01Examination request arrives
  2. 02Reception reviews it
  3. 03Appointment is arranged
  4. 04Attendance and follow-up are recorded

02 / INSIDE THE PRODUCT

See how the work connects.

Choose a view to inspect the interface and its role in the workflow. All images use demonstration data.

Today's workspace

Start with the work that needs attention.

The opening view brings open requests, appointments, and urgent tasks together. Reception can move into a request or task from this starting point.

  • Daily request and task summary
  • Direct navigation across operations
  • A separate physician-relationships area
Sama Scan Control Center — Today's workspace — Demonstration interfaceInspect the full interface
Actual product interface rendered with labelled demonstration data.
Request journey

A request keeps its context after first contact.

The request list shows examination, source, stage, owner, and next action. A website submission remains a request for reception review; appointment confirmation is a separate workflow step.

  • Stage, source, and owner filters
  • Request and follow-up share context
  • Coordinated booking with staff confirmation
Sama Scan Control Center — Request journey — Demonstration interfaceInspect the full interface
Actual product interface rendered with labelled demonstration data.

03 / PRODUCT CAPABILITIES

Details that serve the workflow.

Center operations

01

A unified contact record

Requests connect to normalized contact records, with archiving and reactivation when needed.

02

Owned, staged requests

Examination type, source, stage, and owner stay together so a task retains its context.

03

Appointment coordination

Schedule by examination resource, check conflicts, and record confirmation, attendance, or cancellation.

04

Timed, prioritized follow-ups

Assign tasks with due dates, priorities, and completion status, with a view of work needing attention today.

05

Workspaces by role

Administration, reception, and marketing roles, with an audit trail and version checks during editing.

06

Center relationships

Referring-physician, visit, and report modules sit alongside operational and marketing summaries.

ASK THE EXPERIENCE / 06

Ask a better question.
See the practical answer.

Six practical answers about Sama Scan Control Center, its workflow, connections and delivery scope.

Return to the interface tourExplore the CRM service studio
01How does Sama Scan CRM preserve an examination request’s context?
THE ANSWER / IN PRACTICE

The request links contact, examination, source, stage and owner. Reception can see the last action and next follow-up without rebuilding context from separate conversations. Staff must keep records current.

02Does a website request confirm an appointment?
THE ANSWER / IN PRACTICE

A website request starts the review. Reception arranges the resource and time, records confirmation, then attendance or cancellation. Separating these stages makes request, appointment and attendance figures understandable.

03How are follow-ups shared between reception and management?
THE ANSWER / IN PRACTICE

Tasks have an owner, due date, priority and completion state. Role-based workspaces and an audit trail support coordination; access is configured against team responsibilities during setup.

04How are referring-physician relationships represented?
THE ANSWER / IN PRACTICE

Administrative modules cover referring physicians, visits, follow-ups and reports. They preserve relationship context and next actions alongside daily center requests, based on the records entered by the team.

05Is this a radiology or diagnostic-record system?
THE ANSWER / IN PRACTICE

This scope covers administration, requests, appointments and follow-ups. The walkthrough excludes radiology images, diagnostic reporting and billing, and does not expose real patient records.

06What can I assess before commissioning a similar system?
THE ANSWER / IN PRACTICE

Inspect the interface, request journey and module roles. Demonstration records do not prove booking volumes or operating outcomes. A similar build starts with sources, appointment resources, permissions and acceptance criteria.

Your workflow has its own details.Discuss your specific question
Implemented custom product

The product's delivery stage and scope.

An implemented custom product for the center's administrative operations. The tour uses demonstration data. Google summaries include dated snapshots; the content module supports preparation and review. This scope is administrative and excludes radiology images, diagnostic reporting, and billing.

Read the project case study

LET'S DESIGN YOUR WORKFLOW

Does your center need a clearer booking workflow?

Start with request sources, team roles, and appointment resources, then define the necessary modules and website connection.

Google Business Profile

Office location in Al Masif, Riyadh

Digital enquiries are accepted 24/7. Office visits are available after the appointment is confirmed; remote collaboration is available across Saudi Arabia.

Open the business profile and directions
6619 أبي زيد البلخي، 3726 حي المصيف, Riyadh 12465Digital intake 24/7 · visits by appointment057 939 5299
Call now Message on WhatsApp