Smilestones¶
Part of the Aashray Business Logic. Related: Food, Accounts, Identity & Authentication, Custom Forms (Form Builder).
Smilestones staff book group meals for Smilestones guests at the Research Centre. They do this on the staff panel's group food booking screen. The staff panel has a separate Smilestones screen, but that page is empty, and no menu links to it.
The staff panel lists "Smilestones Guest" as one of the guest groups for group meal bookings, beside Research Centre, school, medical, Sanisa, personal and event guests. The Aashray privacy policy names Smilestones as a community service or fund-raising campaign (staff panel public pages).
Members take no part. The member app has no Smilestones feature.
Who uses it¶
- Staff with the Smilestones role. Their home menu has one button: Bulk Food Booking (staff panel).
- Super admins and food admins use the same booking screen for every guest group (staff panel and backend).
- The Form Builder offers a Smilestone department, but the Smilestones role cannot open the Form Builder. Only a super admin can manage a Smilestone form (see Custom Forms).
The Smilestones screen¶
The Smilestones screen is an empty page. It shows nothing and does nothing (staff panel).
Booking group meals for Smilestones guests¶
A group meal booking is a headcount of meals under one person's card, with no per-meal charge (see Food).
- What staff enter (staff panel). A card number or a mobile number, the date (today by default), the guest count, and at least one of breakfast, lunch and dinner.
- Guest group. For the Smilestones role, the guest group is fixed to "Smilestones Guest" and cannot be changed (staff panel).
- Finding the card (backend). The backend finds the card by the card number, the mobile number, or both. When staff fill both, they must belong to the same card. If no card matches, the booking is refused.
- Counts (backend). Each ticked meal gets the guest count. An unticked meal gets zero.
- Cutoff (backend). For the Smilestones role only, the backend refuses a booking for tomorrow after 11:00 AM today.
Viewing and changing bookings¶
- Looking up (staff panel and backend). Staff enter a card number or a mobile number. The list shows that card's group bookings from today onward, for every guest group. Each row shows the date, the card holder's name and mobile number, the guest group, the guest count, and the count for each meal.
- Plate counts. Food staff also see how many plates were issued for each meal. The Smilestones role does not see these columns (staff panel).
- Changing counts. Staff change the count for each meal. The guest count becomes the largest of the three meal counts (backend and staff panel).
- Cutoff (backend). For the Smilestones role only, the backend refuses a change to tomorrow's booking after 8:00 PM today.
- Kitchen staff issue plates for a group booking as a running count (see Food).
Messages sent¶
| Event | Message | Recipient |
|---|---|---|
| A group meal booking is made | WhatsApp with the guest group, the card holder's name, the guest count, the date and the meals | The card holder |
| A group meal booking is changed | WhatsApp with the card holder's name, the date, the guest count and each meal's count | The card holder |
If a message fails, the booking or change is still saved (backend).
How this connects to other domains¶
- Food (05): Smilestones bookings are group meal bookings. They feed the kitchen's headcount, and kitchen staff issue plates against them.
- Accounts, Identity & Authentication (02): the Smilestones role controls access. Each group booking sits under one member's card.
- Custom Forms (11): the Form Builder has a Smilestone department that only a super admin can manage.
Known limitations today¶
- The Smilestones screen is empty. Staff have no Smilestones screen of their own, only the group food booking screen.
- The backend gives the Smilestones role every food staff action except the kitchen count. These include issuing plates, booking and cancelling member meals, editing menus, and reading food reports. The staff panel shows only group meal booking.
- The guest group lock is only on the page. The backend accepts any guest group from the Smilestones role.
- The cutoffs cover only tomorrow. A booking or a change for today or a past date is never refused.
- The two cutoffs differ. A new booking for tomorrow closes at 11:00 AM. A change to tomorrow's booking closes at 8:00 PM.
- The cutoffs use the backend's clock. If the backend does not run on India time, the cutoffs fall at another India time.
- Smilestones staff can see and change other groups' bookings. The look-up shows every guest group's bookings for the card, and the backend lets the Smilestones role change any of them.