What this guide covers
Start with a small operational app that joins customer accounts, supplier bills, expenses, employees and attendance. Its scope is deliberately limited: manufacturing planning, consolidated multi-branch accounts, statutory payroll and tax integration need separately specified solutions.
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
- 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.
- 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.
- 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.
- 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.
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.
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:
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.
Open the app and add staff
- Open the delivered link in a current browser and check the app name before entering data.
- Sign in with an authorised phone number and the code received on WhatsApp. Initial sign-in needs a connection and sufficient login-code balance.
- 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.
- 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:
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.
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:
- 👥 CustomersName, Phone, Address, Tax ID, Notes💳 balance per person (owes / credit)
- 🧾 Sales invoicesCustomer, Description, Amount, Paid, Due date, Date, Notes📈 daily and monthly reports
- 💰 ReceiptsCustomer, Amount, Date, Method, Notes📈 daily and monthly reports
- 🏭 SuppliersName, Phone, Address, Notes💳 balance per person (owes / credit)
- 📥 Purchase billsSupplier, Description, Amount, Paid, Due date, Date, Notes📈 daily and monthly reports
- 💸 Supplier paymentsSupplier, Amount, Date, Notes📈 daily and monthly reports
- 💸 ExpensesDescription, Amount, Date, Type, Notes📈 daily and monthly reports
- 🧑💼 EmployeesName, Phone, Job title, Salary, Status
- ✅ AttendanceEmployee, Date, Status, Notes
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:
- Customers: Al Nour Packaging: phone, address, tax ID. Every invoice and receipt for them shows on their page with their balance.
- Sales invoices: Customer Al Nour, description "10000 one-litre bottles", amount 85000, paid 40000, due date in 30 days.
- Suppliers: Polymers Co.: phone. Then a purchase bill "2 tons of raw material", amount 120000, paid 60000, and a supplier payment when you pay the rest.
- Employees: Sameh: job title Machine operator, salary 7000, status Active. Attendance daily from the Attendance section.
Use the app in daily work
Sales: every sale is an invoice under Sales invoices with customer, amount, paid and due date, and every later payment is a Receipt. The customer page shows the balance before you accept a new order.
The accountant: Purchase bills when raw material arrives, Supplier payments when you pay, and Expenses (rent, electricity, salaries, transport). Each supplier's balance is calculated by itself.
HR records attendance for each employee. The manager reviews section reports, receipts and expenses for the month, with customer and supplier balances on their pages. Test each department’s permissions before use.
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.
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.
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:
Adapt this example, then send it:
Adapt this example, then send it:
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.
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:
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.
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.
| 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.
- Record one customer invoice, its payment, one supplier bill and its payment. Check customer and supplier balances without mixing receipts with sales totals.
- Test the sales, accountant and HR roles on the same sample data. Verify that salary and supplier sections are restricted according to the agreed plan.
- Compare each section report with its source records for one period. Agree which report is operational cash movement and which, if any, is a reviewed accounting result.
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
Is this a full ERP like the big systems?
It is a focused internal operations app, not a full enterprise ERP. The initial plan covers the listed customer, supplier, expense and staff records. Manufacturing, multi-company consolidation, tax integrations and automatic payroll require separate requirements and validation.
I want a stock of items with quantities?
Ask with one sentence as in step 7 (a products section with quantity and a low stock alert). If selling stock items is your main business, the inventory and sales guide below fits you better.
The government electronic invoice?
Not available. The program is for your internal books, and you can export CSV for your accountant.
Does each department see only its own part?
Yes. The ready roles are sales, accountant, HR and manager, and one sentence changes what any role can see or edit.
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.
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.