Telegram Workflow
Talk to the tracker. Review it here.
RAIDC tracks Risks, Actions, Issues, Decisions, and Changes across projects. Telegram is the fast capture layer; PocketBase remains the source of truth; this web dashboard is where you review, clean up, and scan project health.
The everyday rhythm is simple: capture something, review what is open, update an item, then close or reject anything that no longer needs active tracking.
@zraidc_bot
Projects
Use project keys as short handles
Every item belongs to a project. In private chat, include the project key when creating or querying records. In a linked group, the bot can use the group project as default context.
tesda
eastdev
ebilling
estore
tctrade
meralco
wedding
/open tesda
/project meralco
/linkproject tesda
/action chase signed docs by Friday
Capture Items
Create RAIDC records fast
Slash commands are the predictable path. They work well when you know the item type and want the bot to create exactly one record.
/risk tesda accreditation documents may slip
/action tesda hire instructor by friday high
/issue tesda supplier quote too high
/decision tesda use rented classroom
/change tesda move opening date to september
Natural capture also works when the message clearly names the project, RAIDC type, title, due date, priority, or assignee. In groups, start with the bot mention so normal conversation is ignored.
tesda action hire instructor by friday high @zenners
@zraidc_bot tesda action chase accreditation docs by friday high
Query From Chat
Pull project and item views
Use these commands when you are in a meeting, on mobile, or inside a project group and need the current state without opening the web app.
/open tesda
/project tesda
/item ACT-007
/today
Open lists active items. Project summarizes the RAIDC mix. Item shows the detail card and recent updates. Today surfaces items needing immediate attention.
Update Items
Move work without opening the web app
Use item codes directly when you know the code. The bot records changes as item updates, so the activity history stays visible in Telegram and the dashboard.
/update ACT-007 waiting on mayor signature
/due ACT-007 friday
/assign ACT-007 @zenners
/priority ACT-007 high
/status ACT-007 blocked
For assignment, the bot must already know the Telegram user. If it does not, ask that person to send a message where the bot can see it, or reply to one of their messages with the assign command.
/assign ACT-007 @zenners
/assign ACT-007
Reply Shortcuts
Use natural chained edits
Reply to an item card and leave out the item code. In groups, mention the bot so it knows the message is meant for it. This is the fastest way to maintain items during chat.
@zraidc_bot waiting on finance reply
@zraidc_bot due friday
@zraidc_bot assign @zenners
@zraidc_bot high
@zraidc_bot status blocked
You can chain multiple updates in one reply. The bot applies recognized changes first, then saves leftover text as a note.
@zraidc_bot due friday assign @zenners high waiting on mayor signature
Natural Language
Know when the parser acts
In private chat, you can speak more naturally. In group chats, natural language must start with the bot mention. Normal group chatter is ignored and is not saved to PocketBase.
Some phrases are protected so the bot does not over-interpret ordinary notes. For example, due to stays part of a note unless you explicitly use the due command.
@zraidc_bot candidate declined due to harassment
@zraidc_bot waiting on mayor signature
@zraidc_bot status waiting
Group Setup
Bind a Telegram group to a project
Invite the bot to the group, check the chat, then link the group to a project. Once linked, the group can capture and query that project without repeating the project key.
/chatinfo
/linkproject tesda
/members tesda
/unlinkproject
Add members by replying to one of their messages, or include the project key explicitly. Owners can manage membership and group links. Members can create and update. Viewers can review but not change items.
/addmember member
/addmember tesda member
owner
member
viewer
Close, Reject, Reopen
Keep history clean
Close means the item is done being tracked. The bot sets a type-appropriate outcome: actions become done, issues resolved, decisions decided, changes implemented, and risks retired.
/close ACT-007 secured
@zraidc_bot close done 1m secured
Reject means remove the item from active tracking because it is not being pursued. Reopen brings the item back to its active default state.
/reject ACT-007 no longer pursuing
/reopen ACT-007 back in scope
action -> todo
issue -> open
decision -> pending
change -> proposed
risk -> identified
Review And Undo
Find quiet items and recover mistakes
Use stale review for open items with no recent movement. In private chat, stale review can check all your projects. In a linked group, it checks the group project.
/stale tesda
/stale tesda 14
/stale 7
/review tesda 14
Undo reverses your latest linked bot action. It can reverse field changes such as due date, priority, status, owner, close, reject, and reopen. Notes are marked undone instead of deleted, and a just-created item is cancelled rather than removed from history.
/undo