What this guide covers

Keep each lead’s stage, next follow-up and assigned rep alongside calls, visits and deals. This is a sales follow-up app. It does not automatically import WhatsApp conversations or Facebook leads, and a recorded deal value is not the same as money collected.

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 CRM for my company, Horizon Air Conditioning in Cairo: leads with stage, source, owner and next follow-up date with a due follow-ups alert, activities (calls and visits), deals with amount and stage, and expenses. Name it horizon-crm 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:

Sales repManager

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:

  • 🎯 LeadsName, Phone, Company, Stage, Source, Next follow-up, Assigned to🔔 Follow-ups due
  • 📞 ActivitiesLead, Type, Date, Outcome, Next step date
  • 🤝 DealsLead, Deal, Amount, Stage, Expected close, Notes📈 daily and monthly reports
  • 💸 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:

  • Leads: Eng. Khaled (a contracting company): phone, company, stage New, source Facebook, next follow-up tomorrow, assigned to Youssef.
  • Activities: Lead Eng. Khaled, type Call, date today, outcome "wants a quote for 6 AC units", next step in 3 days.
  • Deals: Lead Eng. Khaled, deal "6 AC units 1.5 HP", amount 90000, stage Quote, expected close end of month.
  • Expenses: Facebook ads 3000, type Other. So you know what each Facebook lead cost you.
Step 5

Use the app in daily work

Morning: each rep opens the app and finds the Follow-ups due box at the top with the leads whose follow-up is today or overdue by less than 30 days. They work through them one by one.

After every call or visit: record an Activity with the outcome and the next step date, and move the lead's stage (contacted, interested, negotiating, won, not interested). A lead who agreed becomes a Deal with its amount.

The manager: in Leads taps the stage buttons above the list (new, interested, negotiating…), and in the deals report sees the number and value of deals per rep for any period.

Alerts the app raises for you

  • Follow-ups due in Leads

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 requested product field to leads

Adapt this example, then send it:

add a section called quotes with lead, items, amount, status (sent, accepted, rejected) and sent date

Adapt this example, then send it:

let the sales rep role see only the leads they registered

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 Horizon Air Conditioning in Cairo: a home page with our services (supply, installation and maintenance) and brands, a prices page, a projects page, and a request a quote on WhatsApp button 01000000000. Name it horizon 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 leads due yesterday, today and next week. Verify the follow-up list, including how older overdue leads are found outside the dashboard window.
  2. Assign a lead to one rep but create it from a manager account. Confirm that the intended rep can access it; assignment and record ownership must not be confused.
  3. Move a deal through Quote, Won and Lost in sample records. Verify that a won-deals report excludes lost deals and uses the agreed attribution field.

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

Do leads from WhatsApp or Facebook enter by themselves?

No. The rep records them in the app (name, number, source). Automatic connection to Facebook pages is not available yet.

A rep left, do his leads go with him?

The company records remain in the app when a team member leaves. Remove their access, reassign the work and review shared devices and exports. Removing access does not erase copies the person may already have exported.

How are due follow-ups calculated?

From the "Next follow-up" field on the lead. Anyone due today or overdue by less than 30 days shows in the box at the top by itself, and disappears when you set a new date. Not interested? Clear the follow-up date.

Can I see what each rep closed?

Yes. The deals report gives the number and value of deals per rep (whoever recorded them), and the stage buttons in Deals show the ones marked "Won".

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