What this guide covers

Track test orders and manually entered results through review and delivery. Keep a distinct patient identity on every order. The example does not connect analyzers or interpret results; qualified laboratory staff must check values, units and reference information before release.

Business names and figures below are illustrative. Start with sample data and agree the sections, permissions and calculations before building. The final screens and menu labels depend on your approved plan.

Before you start: account and subscription

  1. Create or use your account. Open gammal.tech/join and complete identity verification through official registration. Follow the document requirements shown and wait for approval; account activation and app building have separate timelines.
  2. Activate the WhatsApp subscription. After approval, open my.gammal.tech, check the current subscription price, fund the wallet if needed and activate the subscription. Confirm it is active; adding wallet funds alone does not activate it.
  3. Prepare your scope and budget. List the sections, staff roles and devices you need. Request separate prices for building, hosting, staff login codes and additional usage. The WhatsApp subscription is separate from the app cost.
  4. Open the building conversation. Contact +201033998844. Send one message at a time and wait for its reply before continuing.

See the official account guide for current identity requirements. Submit identity documents only through official registration.

Step 1

Enter build mode

Send this command on its own, including the square brackets, colon and space:

[mode: build]

The button prepares the message only. Press Send inside WhatsApp and wait for build-mode confirmation before sending your request. [mode: web] is an alternative for the same mode; use one command. Send [exit] on its own to return to the normal assistant.

Step 2

Request the app and review the quote

Replace the example business name, location and scope with your own. The suggested address is illustrative and subject to availability. Use fictional customer details while trying the request.

Adapt this example, then send it:

I want a program for my lab, Alpha Medical Lab in Assiut: a test list with price, sample type and turnaround, patients with referring doctor and a balance for each, orders with a cashier screen and status, results with a flag and printing, and expenses. Name it alpha-lab Explain the sections, roles, calculations, manual steps and offline limitations. Quote building, hosting and usage separately, and wait for my approval before execution.

Before approving, check the proposed sections, who can read and edit each one, the calculation and alert rules, and the quoted cost and estimated timing. Ask for any unclear point to be revised first.

When the scope and cost suit you, use the confirmation requested by the assistant. Execution starts after approval, and the link arrives when the build is ready. Use the estimate in the quote to plan your review and testing; scope and revisions affect timing.

Step 3

Open the app and add staff

  1. Open the delivered link in a current browser and check the app name before entering data.
  2. Sign in with an authorised phone number and the code received on WhatsApp. Initial sign-in needs a connection and sufficient login-code balance.
  3. Use Install or Add to Home Screen if your device offers it. Browser labels and support vary; you can also use the app in the browser.
  4. Load the relevant sections and let them sync before testing offline work. After reconnecting, review pending records and conflicts. Do not clear browser storage while changes are waiting to upload.

Add staff and test permissions

Add the agreed phone numbers and roles in the staff section. The owner and authorised admins can manage members within their permissions. Suggested roles for this example:

ReceptionTechnicianDoctorManager

Test each role with a separate account and sample records. Section permissions do not hide a single field inside a shared record. Agree separate sections when information needs different access.

On a shared device, PIN switching can be used after the device’s supported sign-in setup. Each staff member uses their own account; do not share login codes.

Step 4

Set up sections and starting data

Use these sections and fields as the starting specification. Agree the calculation and alert rules rather than assuming they are included automatically:

  • 🧑‍⚕️ PatientsName, Phone, Birth date, Gender, Referring doctor, Notes💳 balance per person (owes / credit)
  • 🧪 TestsName, Price, Sample, Turnaround hours, Normal range
  • 🧾 OrdersPatient, Total, Paid, Status, Date, Notes🧾 cashier screen (scan, pay, print) · 📈 daily and monthly reports
  • 📋 ResultsOrder, Test, Result, Flag, Date, Notes
  • 💸 ExpensesDescription, Amount, Date, Type, Notes📈 daily and monthly reports

After approving the plan, open a section and add a sample record. The following entries illustrate the workflow; the figures are not live prices or real customer data:

  • Tests: Complete blood count CBC: price 150, sample Blood, turnaround 4 hours, normal range (for reference). Fasting glucose: 60, blood, 2 hours.
  • Patients: Hussein Ali: phone, birth date, gender, referring doctor Dr. Samir. Created once.
  • Orders: From the cashier screen: pick the patient, type the test names (CBC, fasting glucose), the total is calculated, enter the amount paid, Pay & print. The status starts as "Received".
  • Results: Order number, test CBC, result (the values), flag Normal, High or Low, date. Tap 🖨️ to print the result with the lab name.
Step 5

Use the app in daily work

Reception: the patient arrives, you open the cashier screen, pick their name or create a file, type the requested tests, take the money and print the receipt. The order is recorded with status "Received".

The technician: opens Orders, switches the status to "In progress" when starting, then records each test under Results with the value and flag (normal, high, low), and sets the order to "Ready". The doctor reviews the results before delivery.

Delivery: reception checks the orders with status "Ready", prints the result with 🖨️, and switches the status to "Delivered". At the end of the day reports give the order count, revenue and expenses.

The cashier screen

From the home screen tap the cashier button: type the service or item name and it drops into the bill at its price, adjust the count if needed, enter the amount paid (or tap "Exact"), and press Pay & print. The receipt prints and the screen is ready for the next bill. Keyboard shortcut: F2 for the next bill.

Every person has a page listing everything linked to them (their invoices, visits, payments) and their balance: owes when something is unpaid, credit when they paid extra.

For printing, preview the output and test the intended printer and paper size. Offline work needs a previously signed-in, synced device. After reconnecting, check that changes uploaded successfully; other staff cannot see them until they sync.

Step 6

Review reports and exports

Open Reports and select the period you want to review. Identify what each total represents: invoices, cash received, expenses or deal value. Do not add an invoice and its receipt as two separate revenues, or treat every summary as accounting profit.

Try Export CSV, open it in Excel or Google Sheets and compare record counts and totals with the source entries. Check whether staff reports refer to the person responsible for the work or the person who entered it; those can be different people.

Use the business-specific checks below to validate the figures before relying on them.

Step 7

Request and check changes

Send one clear change request in the building conversation. Identify the app when working on several projects, and review the price and effect on existing data before approving.

Adapt this example, then send it:

add a normal range field to results so it prints with the result

Adapt this example, then send it:

add a section called outsourced samples with the external lab, test, date and status (sent, returned)

Adapt this example, then send it:

let the technician role see orders without editing them and record results

After the change, check old and new records and the affected calculations. If you need to reverse it, ask what undo will restore before using it. Reversing an app change is not a guarantee of deleted-data recovery. Keep an appropriate export before material changes and check the current refund terms.

Step 8

Add a public page if needed

The app manages internal work. If you need a public customer page, request it as a separate project and explain how enquiries will be reviewed and entered into the app. A WhatsApp button does not automatically import an order or confirm a booking.

Adapt this example, then send it:

I want a website for Alpha Medical Lab in Assiut: a home page with working hours, address and home sample collection, a test list page with prices, and a book a home visit on WhatsApp button 01000000000. Name it alphalab Use only my actual business information; do not invent reviews, guarantees, prices or delivery times. Quote the cost and wait for approval. An enquiry or booking request stays pending until I confirm it.

Answer real customer questions: the service, location, price or pricing method, inclusions and confirmation process. Use only images and reviews you have permission to publish. Clear facts help readers, search engines and AI systems understand the business, but do not guarantee rankings or recommendations.

If you need visitor sign-in, online payment or email notifications, specify each feature, its cost and its test procedure in the quote. Do not assume they are automatic additions. The actual recipient of earnings should review payment setup on their verified account.

Step 9

Check costs and renewal

Budget separately for WhatsApp access, the one-time build, hosting and usage such as staff login codes. Use the amount shown in your account and the quote you approve. Do not rely on an old EGP-to-USD conversion.

Examples of follow-up messages
Message Purpose
prices Ask for the current build, hosting and usage costs before approving.
app status Check the hosting period and usage balance.
renew the app for 1 month Request the duration, review the amount and confirm the renewal.
add 100 EGP to the app balance An example usage-balance request; choose your amount and review the confirmation.
[exit] Leave build mode. This does not mean cancelling hosting or a subscription.

Check the expiry date and renew manually before it. Wallet funds alone do not renew MeNooN hosting. Before letting the app expire, export what you need and check the current retention and recovery terms; indefinite preservation is not assumed.

Test the app before relying on it

Run these checks with fictional data before moving real work into the app. If a result differs, describe the case to the assistant, request a correction and test again.

  1. Create two fictional patients and orders with the same test. Confirm that results and printouts stay attached to the correct patient and order.
  2. Have qualified lab staff enter a fictional result with unit and applicable reference information, review it and release it. Verify that an unreviewed record is not presented as approved.
  3. For company billing, keep each patient separate and link a distinct payer account. Verify that the bill groups charges without merging patients or their results.

Also test a restricted staff role, printing or export, and one offline record followed by sync. Start with a small workflow and review the results with your team during the first week.

Questions about this app

What does the printed result look like?

Agree the print layout before use: patient and order identifiers, test, result, unit, applicable reference information, date and reviewer. Qualified laboratory staff must review the result and the output. This example initially prints one test per sheet; grouped reports need a separate request.

Do analyzers send results to the program by themselves?

No, direct connection to analyzers is not available. The technician types the result from the device screen into the result field.

How does the patient know the result is ready?

Reception checks the orders with status "Ready" and calls them. After delivery the status becomes "Delivered" so nobody asks twice.

We have insurance company contracts?

Keep the actual patient on every test order. Request a separate payer or company account for billing, linked to those orders. Do not register an insurer as the patient or merge different people’s results into one patient file.

Do I need to know how to code?

You do not need to write code to follow these steps. Describe the request in WhatsApp, review the quote and test the delivered app. You may need to refine the request to fit your workflow.

Where is the data stored?

Records are stored on Gammal Tech servers and may also have a device copy for offline work. Device protection, staff permissions and exports still matter; server storage does not remove the local copy.

Can I import an Excel file?

The initial plan here uses entry inside the app and CSV export. Do not assume Excel import or record-image uploads are included. If migration is essential, agree a supported route before building.

Will it work on my device?

Start with a current browser and test the actual device. Installation, printing, barcode input and offline behavior depend on the device, browser and app implementation. Verify them before buying equipment or moving all your work.

What if a change does not work as expected?

Send a clear example of the expected and actual result without real customer data. Ask for a correction or the limits of undo. Check the quoted refund terms rather than assuming an automatic refund in every case.

Can I manage several branches?

This example starts with one business or branch. Specify separate stock or branch permissions before ordering. A second app does not automatically combine both branches; shared reporting and integration need a separate agreement.

Start with the version your business needs

Prepare your request, start with one important workflow and test it with your team. Send the build command on its own first and wait for confirmation.

Reference

Gammal Tech official reference covers accounts, staff sign-in, records, sync and pricing. Also review the terms and privacy policy. Confirm service amounts and scope in your account and quote when ordering.

All Articles & Guides