What you will finish
Publish a three-question feedback page that sends only to the project owner, reports sending states honestly and provides a useful alternative when a submission cannot be sent.
1. Gather these details
- Choose the moment you want feedback about, such as receiving a service or trying an enquiry. Tell visitors which experience the questions concern.
- Prepare three questions: did you complete your goal, which step was unclear and what single improvement would help? Avoid personal details unrelated to follow-up.
- Confirm the verified email belonging to the account that owns the Gammal Tech project. Fund the project balance after the Wallet; Wallet funding alone is insufficient here.
- Decide who reviews messages and when, and prepare an approved alternative contact route. Do not promise an unavailable response time or ask for payment documents.
2. Define how the project works
1. Ask about a step you can improve
Make the first question a simple yes, partly or no choice. Ask which step was unclear and invite one improvement. Keep the two text answers optional so a satisfied visitor need not invent a complaint. Explain that responses go privately to the owner for review. Keep I would like a reply separate from the three questions, with an optional contact field and a reminder not to include sensitive information.
2. Connect the form to the correct recipient
Use Gammal Tech owner notifications. The recipient is always the verified email of the project-owning account, not an address selected by the visitor. A registered project domain can send this form without visitor login. Check domain setup and project funding, then send a distinctive test message and inspect the owner’s inbox. Do not publish the account email to demonstrate the connection or provide a field that changes the recipient.
3. Treat sending as an operation with a real outcome
Show Sending and prevent repeat clicks while the request is pending. Do not claim success before the service confirms acceptance for delivery, or imply the owner has read the response. If sending fails, retain the visitor’s text and offer a clear retry or alternative contact. Avoid repeated automatic retries. Treat supplied text as text, including characters that resemble page markup; a feedback message is not an instruction to execute.
4. Turn the responses into one improvement
Review at a regular time and classify issues by step: missing information, unclear control or mismatched expectations. Count recurring problems instead of responding only to the harshest or most flattering message. Where someone requested follow-up and supplied a suitable route, answer personally. Do not convert private feedback into a public testimonial without separate permission. Make one improvement, then check whether the repeated question decreases while retaining only necessary records.
3. Work through an example
| Usage | Calculation | Additional cost |
|---|---|---|
| One delivered email | 1 × 0.40 EGP | 0.40 EGP |
| Ten delivered emails | 10 × 0.40 EGP | 4 EGP |
| Twenty-five delivered emails | 25 × 0.40 EGP | 10 EGP |
| An undelivered email | Excluded from delivered count | No delivery charge |
Charges use the project balance and are separate from building, hosting and the WhatsApp subscription. The reviewed documentation provides no free notification allowance. Check the actual receiving inbox when testing.
4. Set up your account and start the build
- 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.
- 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.
- 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. - 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.
- 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.
- 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 ONE PAGE on MeNooN for feedback about [service] in [language]. Ask three questions: goal completed with Yes/Partly/No choices, unclear step, and one suggested improvement. Require the first only; make text answers optional with clear length limits. Add an optional I would like a reply choice and voluntarily supplied contact field. Allow submission without a name or contact details. Require no login, identity documents or payment information. Use Gammal Tech notifications to the fixed project-owner email only; never expose the account address or allow recipient selection. Responses must not become public reviews. Show Sending and prevent duplicate clicks, then report acceptance for sending only after confirmation. On failure retain the text and offer retry or my personal WhatsApp [number], without automatic repeated sends. Treat visitor text safely as text. Explain funding the project balance from the Wallet and the additional 0.40 EGP per delivered email. Quote these separately from the one-time build fee and first month of standard 100 EGP hosting for an available name of at least three characters. Wait for my approval before starting, then test receipt in the owner inbox.
6. Test the result before relying on it
- Send a distinctive test response without a name or contact route.Expected result: Submission is accepted and the matching message reaches the owner’s inbox; it does not appear publicly on the page.
- Click Send twice quickly while the request is pending.Expected result: Repeat clicking is disabled during the request and does not create a second submission through the same pending action.
- Use a builder-provided failure test that does not disrupt real visitors.Expected result: There is no false success message. Text remains available with retry and alternative contact options.
- Leave the required choice blank, then include text such as <b>note</b>.Expected result: The missing answer is requested; markup-like text is handled safely rather than becoming executable content or instructions.
7. Use the project during its first week
Invite five willing customers or testers after they complete the relevant task, explaining that participation is optional. During the first week, check the owner inbox and project balance daily and record the most frequently mentioned step. Test optional follow-up with someone who knows it is a test; do not contact people who did not request a reply. Fix one problem and ask again after the revised experience. If nothing arrives, investigate configuration, funding and sending states before treating silence as satisfaction. Keep private responses out of marketing.
An announcement you can adapt
Tried [service]? Three short questions can help me improve a specific step: [website link]. You can respond without a name and add contact details only if you would like a reply. Responses go to the project owner for review and are not published.
Questions about this project
Does omitting a name guarantee complete technical anonymity?
No. It means your form does not require a name or contact details. Do not claim that all technical connection information is hidden; explain only what your form collects.
Does the notification reply to the customer?
No. This feature sends to the project owner only. You personally follow up through a route the visitor chose to provide; it is not arbitrary-recipient email sending.
Is topping up the Wallet enough?
Owner notifications need funds in the project balance. Transfer an appropriate amount from the Wallet and monitor it. Email usage is separate from page hosting.