It doesn't just tell you how.
It does the task.
Mahadrone performs simple, defined actions inside your connected tools: booking rooms, pulling reports, drafting summaries, filing requests. The employee asks once and gets a finished result.
Arjun
Pull last month's regional sales report
Mahadrone
September's regional sales report is ready and shared with you as a sheet.
Reports · 1 export shared
Reports
Dashboards and exports
Exporting September by region
The tasks it can perform.
Tasks are defined actions, not open-ended automation. Each one is switched on by an admin for the teams that should have it.
Calendar
- Book or release a meeting room
- Find a time that works for attendees
- Move or cancel a meeting
Reports
- Run a saved report
- Export a period or region as a sheet
- Share a figure with the requester
Docs
- Draft a summary from notes
- Create a document from a template
- Find and share a file
HR System
- Submit a leave request
- Check a leave balance
- Look up the holiday calendar
IT Desk
- Raise an access or hardware ticket
- Attach device details
- Relay status updates to chat
Routing
- Hand a request to the right team
- Notify the owner with context
- Keep the requester updated
Worked example
Request in, action done, confirmation out.
A leave request normally means opening the HR portal, finding the right form, and filling in dates. Here is the same request through Mahadrone.
- 1
Request
Meera types “apply leave for this Friday” in a direct message.
- 2
Route and check
It is routed to the HR System. Meera's own account is used, so only her leave can be filed.
- 3
Confirm the detail
Because a leave request changes a record, Mahadrone confirms the date and leave type first.
- 4
Act
The request is submitted in the HR System, exactly as if Meera had filled in the form.
- 5
Confirm and log
Meera gets the confirmation in chat. The action is written to the audit trail.
Apply leave for this Friday
Filing this in the HR System:
- Date
- Friday, full day
- Type
- Annual leave
- Approver
- Your manager
Submitted. Your leave for Friday is waiting on your manager's approval. I'll let you know here when it's approved.
HR System · 1 request submitted
New tasks are added deliberately, not discovered.
When a team wants a new kind of request handled, such as ordering stationery or requesting a parking pass, the task is defined with your admin: which tool it runs in, what inputs it needs, what it is allowed to change, and who can use it.
Once switched on, it shows up for the right people immediately. Nothing is enabled without an admin turning it on.
- Defined inputs, so requests are complete before acting
- Confirmation step for anything that changes a record
- Limited to the teams you choose
- Task
- Request a parking pass
- Runs in
- Facilities request form
- Needs
- Date, vehicle number
- Changes
- Creates one request
- Confirm first
- Yes
- Available to
- All employees, Pune office
Can it take any action in a connected tool?+
No. It can only perform the defined tasks an admin has switched on, and only within the requesting employee's own permissions.
Does it ask before changing things?+
For tasks that create or change records, such as submitting leave or cancelling a meeting, it confirms the details before acting.
What if a task fails in the tool?+
The employee is told plainly what happened and what to do next. The failure is recorded in the audit trail alongside the request.
How are new task types added?+
Your admin defines the task with us: the tool, required inputs, what it can change, and who can use it. It is off until switched on.
Your first request is one message away.
Book the 4th floor room for Thursday 3 PM
Sign upPrefer a walkthrough first? Talk to us