What will users see?

With Gammal Tech phone sign-in, users can access your app with a phone number and a code delivered through WhatsApp.

  1. Open your website or app. They select its sign-in button.
  2. Enter their phone number. The app checks whether that number is allowed under your chosen access setting.
  3. Receive a six-digit code on WhatsApp. They enter the code in your sign-in screen.
  4. Continue into your app. Gammal Tech verifies the code and saves the app session on that device.

The built-in sign-in screen supports Arabic and English. You can also create your own screens and use the documented code-request and code-verification methods.

A practical example: a shop owner adds a cashier's phone number and role. The cashier verifies the number through WhatsApp and uses the shop's app without first creating a Gammal Tech account.

Do customers need Gammal Tech accounts?

They do not need one when you use a member list or open phone access. The project owner chooses who may request a code:

The three access settings for phone login.
SettingWho can receive a code?
members
Default
The owner and phone numbers on the owner's member list. Listed users do not need Gammal Tech accounts. Useful for staff, teams or a selected customer group.
accountsPhones belonging to Gammal Tech accounts, plus the owner's listed members and the owner. This keeps the account requirement for unlisted users.
anyoneAny phone number, subject to funding and usage limits. Users do not need Gammal Tech accounts. Use this when your app should accept new phone users openly.

The owner needs a verified Gammal Tech account in all three settings. The owner controls the project and its budget. That requirement is separate from the end user's sign-in.

The managed member list holds up to 500 phone numbers. This is the list limit, not a stated limit on every user who can sign in through anyone mode.

How to add WhatsApp phone login to your website

  1. Create and verify the owner's Gammal Tech account. Start at gammal.tech/join if the owner has not joined.
  2. Open Developer Mode and create a project. The first project is free; the console shows the fee for additional projects.
  3. Register the HTTPS website addresses that will run the app. Up to four domains are supported. Add both the www and non-www addresses if you use both.
  4. Fund the project. Add money to the owner's wallet, then transfer it to the project balance. Each sent phone-login code costs 0.50 EGP.
  5. Have your developer load the Web SDK and connect phone sign-in. The entry point is GammalTech.app.signIn(). It opens the built-in screen or reuses an existing session.
  6. Sign in as the owner and choose the access setting. The owner uses the phone on their Gammal Tech account. App settings are managed through GammalTech.app.settings.set(). Keep members for a selected list, or choose anyone when new users should not need Gammal Tech accounts.
  7. Set the budget and try the complete journey. Add the intended members when using the list. Check sign-in, return visits, sign-out and removal of a member.

The phone screen opens inside your page. The Login Callback URL used by the separate account-login popup is not how this phone overlay returns its result.

Open the current SDK reference and find “Phone sign-in for apps (staff and customers)” for the implementation details.

Use the built-in screen or your own screen

Documented methods for your developer.
What you wantUse this method
A ready-made phone and code screenGammalTech.app.signIn(). Optional settings include the screen title, country calling code and language.
Your own phone-number formGammalTech.app.requestCode(phone, options). Keep the returned challenge for the code step.
Your own code-entry formGammalTech.app.verifyCode(challenge, code). It checks the code and saves the app session.
Check the current user on page loadGammalTech.app.me(). It confirms the session and current role with the server. A 401 response means sign-in is needed again.
Sign outGammalTech.app.signOut() for this device, or GammalTech.app.signOut(true) for every device of that phone.

The user result includes phone, phone_masked, name, role, is_owner and is_member. Names and roles come from the owner's member list where applicable.

If you already keep customer accounts, connect this verified phone sign-in to your records through a deliberate account-linking process. Existing orders and permissions are not automatically imported.

Phone verification shows control of the number during that check. It does not, by itself, establish a person's legal identity.

Returning users, staff roles and shared devices

Returning users: app sessions last 30 days on the device, with a sliding expiry that can extend through continued use. A valid saved session can be reused without a new code. Sign-out, expiry or removal can require sign-in again.

Staff access: assign roles such as cashier, manager or driver. The owner controls administrator access; admins manage non-admin members. Changes are reflected on the next server check, and a removed number is signed out.

Your application must enforce the relevant permissions before returning private information or allowing restricted actions. Hiding a button is not an access check.

Shared devices: after a device has signed in with a code, the owner and listed staff can switch using their phone number and a 4-to-6-digit PIN. This avoids requesting a new WhatsApp code for each staff change. It is a staff feature for previously verified devices.

What does WhatsApp phone login cost?

0.50 EGP for each code that is sent. There is no free allowance for this method. Refused requests are not charged.

Illustrative code costs, excluding other project services.
Sent codesCost
2010 EGP
10050 EGP
500250 EGP

The default spending cap is 50 EGP per app per day, equivalent to 100 codes at the current rate. The owner can change it through app settings. Other request limits still apply.

When the daily cap is reached, new codes pause until the next UTC day and the owner receives one email. If the project balance runs out, new codes pause; devices with valid existing sessions keep working. The owner receives at most one empty-balance email per day.

Count sent codes when estimating cost. A returning device may use its saved session without another code. The 200-code free allowance for Gammal Tech account login does not apply to this phone-login method.

What happens when a code expires or a user retries?

  • Code expiry: five minutes. A new code can be requested after 60 seconds, subject to the other limits.
  • Request limits: three codes per phone per hour, ten per phone per day, and twenty code requests per device per hour.
  • Wrong codes: five incorrect attempts lock that phone for one hour.
  • Wrong staff PINs: five incorrect attempts lock that phone's PIN for one hour.

These limits reset automatically. Explain the wait or funding requirement in plain language so the user knows what to do next.

Common questions

Can users sign in without an email address or Gammal Tech account?

Yes. Phone login asks for a phone number and a WhatsApp code. Use members for listed users or anyone for open access. The accounts setting requires an existing Gammal Tech account for unlisted users. The owner still needs a verified account.

Is this the same as signing into a Gammal Tech account?

No. GammalTech.app creates an app phone session. GammalTech.login() creates a Gammal Tech account session. Do not assume the phone session grants access to account-based user storage, logged-in AI or wallet payment methods; follow each feature's documented requirements.

Can I keep my own customer database and login design?

Yes. Use the request-code and verify-code methods with your own screens, then connect the verified result to your application. Your app remains responsible for mapping existing records and enforcing its business permissions.

Add phone sign-in to your app

Create your project, fund its code budget and choose who can sign in. Your users can then use WhatsApp codes under the access setting you selected.

Sources and related guide

Product details checked 1 November 2026.