Event Registration Page: Explain the Programme and Confirm Places Manually

1. Gather these details

• Choose one event with a date, start and end time, and a practical outcome, such as a session on photographing products using a phone.
• Confirm permission to use the venue and obtain accurate address, floor, entrance and lift information. Do not claim wheelchair accessibility without checking the relevant route and facilities.
• Define the intended audience, any prerequisite skills, equipment and appropriate age requirements. Use criteria relevant to the activity and safe organisation rather than unrelated exclusion.
• Set a capacity you can actually serve and decide whether attendance is free or paid. Define confirmation, cancellation and request deadlines explicitly before accepting enquiries.
• Choose your own organiser WhatsApp number and a private record with new, confirmed, waiting and cancelled states. Never publish applicants’ names or phone numbers.

2. Define how the project works

Give visitors enough information to decide

Lead with the event’s purpose, practical result, date, duration, venue and intended audience. Add a concise programme and distinguish what participants bring from what you supply. If charging, state what the fee includes and any separate costs. Describe access arrangements you have verified and how to discuss needs before requesting a place. Use speaker names and photographs only when participation and publication permissions have been agreed, without invented endorsements.

Separate a request from a confirmation

The WhatsApp message should request a name, seat count and an optional practical question. Avoid official identification or unnecessary personal information. Beside the button, explain that the organiser must review the request. After checking suitability and capacity, send a clear confirmation with date, time and count. For paid events, explain payment yourself and verify actual receipt where your policy requires it; a transfer screenshot must not trigger an invented automatic verification process.

Manage capacity and waiting places deliberately

Maintain a private record for each request and count only confirmed seats against capacity. If one place remains and someone requests two, discuss one place or waiting rather than exceeding the limit. When full, update the page to waiting-list status instead of displaying an inaccurate live counter. Use a simple disclosed waiting order, and obtain a waiting applicant’s agreement before marking them attending when another person cancels.

Prepare changes and the arrival process

Define how attendees will hear about a time or venue change and review the confirmed list before sending updates. At the event, use a private attendance record to check confirmations without showing names on a public screen. Provide a practical way to contact the organiser on arrival. Afterwards, ask what was useful and what needs improvement, obtaining permission before publishing photographs or quotations. Close registration so visitors do not request places for an event that has ended.

3. Work through an example

These are illustrative numbers. Venue limits and supervision arrangements may require a smaller capacity; the example does not establish an appropriate attendance limit for your activity.

4. Set up your account and start the build

1. Use your account or register.Visit www.gammal.tech/join. New account activation takes 1–10 days. Use a National ID from a country whose citizenship you hold; the official account guide explains the limited exceptions for Egyptian citizens. Submit identity documents only through the official registration process.
2. Activate the WhatsApp subscription.After approval, open my.gammal.tech and add EGP 200 to your wallet, or use sufficient existing funds. Activate the monthly WhatsApp subscription in your account and check that it is active. Funding the wallet alone does not activate it. This subscription covers light personal use; website creation is charged separately.
3. Open the building conversation.Message +201033998844 and send the following command by itself, including the required square brackets. Wait for confirmation of build mode:

   [mode: build]

   [mode: web] is an alternative for the same mode; you only need one command.
4. Send the request in the next section.Replace its placeholders and ask for exactly one page using an available name of at least three characters. Before execution, request an itemised quote separating the one-time build fee, EGP 100 for the first month of standard hosting and any additional usage. Ask how changes beyond the agreed scope are charged.
5. Check the total and approve the build.Once you understand the quote, return to your account and add any missing funds. Return to WhatsApp and confirm the scope and price. Some simple sites take minutes; requirements and revisions affect timing. Open the resulting address and run this guide’s acceptance checks.
6. Record the renewal date.MeNooN hosting renews manually: select the duration and confirm payment before expiry. Leaving funds in your wallet does not renew it automatically. Send [exit], including brackets, when you finish the building conversation.

Budget: quoted build fee + EGP 100 hosting + EGP 200 for one WhatsApp month if it is not already active, plus agreed usage. Twelve months of standard hosting cost EGP 1,200; adding one WhatsApp month makes EGP 1,400 before build and usage fees. Keeping WhatsApp active for further months costs separately.

Service steps and prices reviewed on 18 October 2026. Check the amount shown in your account before paying. WhatsApp steps · Hosting and renewal

5. Adapt and send this request

Replace every bracketed placeholder with your real details. Copy this request after the assistant confirms build mode. Do not publish the illustrative figures as your own.

Build a public ONE PAGE event page on MeNooN for [event name], in [language]. Show its outcome, programme, date [date], start and finish [times], venue [approved public address] and capacity [count]. Explain the audience, prerequisites, organiser-provided items and participant equipment. Include verified access details [details] without inventing facilities or assurances. Fees are [amount or free] and cancellation terms are [approved wording]. Add a WhatsApp request button to my personal number [number], with an editable message for name, seat count and optional question. No visitor login, identity collection or public attendee names. State that requests are not confirmations; I review capacity and confirm manually. Do not build shared automatic booking, a live capacity counter or automatic verification of InstaPay or wallet transfers. Provide page wording I can update to open, waiting list or closed. Waiting does not reserve a place, and cancellations require my review before offering availability to another person. Use only supplied images and claims, without invented speakers or reviews. Before execution, separately quote the one-time build fee, standard first-month hosting of EGP 100 and any other charge. Await approval.

6. Test the result before relying on it

1. Ask an unfamiliar reader to review the page for a minute and explain whom it suits, when and where it happens.Expected result: They find outcome, requirements, times, address and cost clearly; missing decision-critical information is corrected before launch.
2. Open WhatsApp and submit a test request for two places.Expected result: It reaches the correct organiser as a request, without a message claiming confirmation before your review.
3. Test capacity 12 with 11 confirmed and a request for two.Expected result: Do not confirm both; offer one or waiting and keep the confirmed count within capacity.
4. Change the page status to closed and view it on another phone.Expected result: Visitors see the updated status and suitable enquiry instructions, without an active heading implying new places are guaranteed.

7. Use the project during its first week

During the first week, share the link where the intended audience already gathers, obtaining group-admin permission where needed. Explain the practical outcome instead of posting a generic registration plea. Review requests daily and update status when places fill so people do not wait for impossible confirmations. Record recurring questions and improve unclear page details. The day before the event, reconcile confirmed attendees and send the agreed arrival information. Afterwards, close requests and collect focused feedback for any future event.

An announcement you can adapt

Want to learn [specific outcome]? Join [event name] on [date] at [venue], designed for [audience]. Programme, requirements and fees: [website link]. Send a WhatsApp attendance request; your place is confirmed by the organiser subject to availability.

Questions about this project

Do I need automatic booking?

Not for a small event whose requests you can manage personally. This page explains and structures enquiries while you review capacity. Shared automatic booking needs different rules, permissions and implementation.

What should I say about accessibility?

Describe verified details such as floor, entrance and lift, and provide a way to ask questions. Avoid broad claims that imply facilities you have not checked.

Does joining the waiting list reserve a place?

No. The request remains unconfirmed until availability appears, the applicant accepts the offer and the organiser confirms. Waiting places are excluded from confirmed attendance.