Every thali, every day, on one register.
fmbthali.com runs the Faiz ul Mawaid il Burhaniyah thali for a mohalla. Members stop and start their own thali, the kitchen cooks to a count fixed at the cut-off, trip lists go out, and the office keeps takhmeen and receipts in the same place.
Today 1,528 thalis on the register across three mohallas. The first came on in 2017.
1 · Before the cut-off
Members stop and start their own thali.
A family away for a week stops its thali for those days and starts it again when it is back. Nobody has to ring the office.
- A day, a range, or until further notice
- A stop covers any dates. One entered today counts from tomorrow.
- Weekly stop days
- No thali on chosen weekdays, every week, set once.
- A different size for a while
- The office sets a size for chosen dates; it returns to normal after.
- On Telegram, in an app, or by the office
- @FmbThaliBot, a jamaat's own app through the API, or staff on a member's behalf.
2 · At the cut-off
At the cut-off, tomorrow's count is fixed.
Each mohalla picks its hour. Until then members change tomorrow's thali as they like; after it, the count the kitchen cooks to stays put.
- An hour for each mohalla
- Set per mohalla, and moved whenever the kitchen needs.
- Late changes are refused, with the reason
- The bot and the API say the cut-off has passed, never fail silently.
- The office can still step in
- Staff can make a late change when the kitchen agrees.
- Every change is confirmed
- Members get a message for each stop and start, so nobody wonders.
3 · In the kitchen
The kitchen knows the menu and what is in the stores.
Each day's menu is planned ahead and shared with members, and the stores keep pace with what is cooked.
- A menu for every day
- The main dish, its sides and the day's khidmat, planned on a calendar.
- Shared where members are
- Each menu is posted to the mohalla's Telegram channel and Google Calendar.
- Stores, in and out
- Items received and issued by unit, with the current stock at hand.
- Dishes kept for next time
- A list of the kitchen's dishes makes the next menu quicker to plan.
4 · On the road
Trip lists and dispatch, ready for every run.
The day's thalis come sorted by route and by size, so each trip leaves with the right count.
- Trip lists by route
- Short and long forms, for the kitchen and for the driver.
- A dispatch summary
- The day's thalis by size, so the kitchen fills exactly.
- Sizes your mohalla defines
- Each mohalla sets its own sizes by the servings they feed.
- A log of every change
- Every stop, start and size change, with who made it and when.
5 · At the door
Members always know where their thali stands.
From the chat they use to stop and start, members see tomorrow's status, their account and receipts, and tell the kitchen how the food was.
- Status, any time
- Is tomorrow's thali coming? The bot answers at once.
- Their own account
- Takhmeen, statement and receipts, on Telegram.
- Notices from the office
- Reminders and messages by Telegram and SMS.
- A word on the food
- Members rate the day's thali and vote on the menu.
Beyond the day
One register behind it all.
Takhmeen, receipts and statements
Each household's takhmeen for the Hijri year, the receipts against it and a statement that adds up, without a second spreadsheet.
- Takhmeen by Hijri year
- Receipts on Telegram
- Statements and dues
- Niyat, expenses, vendors
Many mohallas, each fenced
Every mohalla runs as its own sector. Its staff work only with its own thalis, and @FmbThaliBot knows which mohalla each thali belongs to.
- Its own sizes and cut-off
- Its own menu and stores
- Its own staff
- Its own books
Your jamaat's own app
FMB API v1 reads and changes thalis under the same rules as the bot. Each key is limited to the mohallas and actions it is given, and every call is recorded.
- GET/v1/thali/{id}
- POST/v1/thali/{id}/stop
- POST/v1/thali/{id}/start
- POST/v1/thali/{id}/size
On fmbthali.com today
- Vajihi Bangalore, India Since 2017
- Burhani Masjid Bangalore, India Since 2019
- Saifee Nagar Bangalore, India Since 2020
Questions
What mohallas ask before they join.
What does a mohalla need to start?
A list of its thalis, the sizes it serves, its cut-off hour and the staff who will run it. Thalis can be brought in from ITS by MuminID. We set the mohalla up as its own sector, so its records stay its own.
How do members stop or start their thali?
On @FmbThaliBot on Telegram, once they have linked their thali with its own key. A jamaat's own app can do the same through the FMB API, and the mohalla's office can act for any member.
What happens at the cut-off?
Each mohalla sets the hour after which tomorrow's thali can no longer change, and the kitchen's count is fixed. A stop entered today counts from tomorrow. Late requests are refused with the reason; the office can still make a change when the kitchen agrees.
Can our jamaat's own app connect?
Yes. FMB API v1 gives your app a key limited to your mohalla: it can read thalis, stops, menus and calendars, and stop, start or change a size under the same rules as the bot. Every call is recorded.
Can one mohalla's staff see another mohalla's thalis?
No. Each mohalla is its own sector: staff accounts belong to one mohalla and work only with its thalis, takhmeen and receipts.
Where do members sign in?
Members use @FmbThaliBot today. Signing in on this site with ITS OneLogin opens soon, and staff keep using the back office until their new area opens here.
Bring your mohalla
Bring your mohalla on.
Tell us your mohalla and who will run it. We set it up as its own sector and help your members onto the bot.
Write to us
Your mohalla, its Jamaat, and the person who will run it.
We set it up
Sizes, cut-off hour, menu calendar and staff accounts, with thalis brought in from ITS.
Members link the bot
Each thali links @FmbThaliBot once, with its own key.
Write to us info@fmbthali.com