Keep support connected.
Bring incoming mail into your helpdesk. Work through incidents, public replies and internal notes, with organization context close at hand.
IncidentsEmailWorklogs
Work through an incident v0.1.2-beta.17Explore the current preview Your service desk.
Create a team workspace Resolved
Self-hosted service desk
Your service desk.
Under your control.
Incidents, email and service requests in one place. Connect your helpdesk to automation and AI, with your infrastructure and access rules.
Open source · Self-hosted · AI optional
rateldesk / service workspaceExample workspace
Every request. A clear next step.
Example organizationOpen incidents
08 in viewService requests
05Resolved today
12 completed| Ticket | Subject | Status |
|---|---|---|
| INC-1042 | VPN connection issue | In progress |
| REQ-2031 | New team workspace | Resolved |
| INC-1041 | Shared drive access | New |
A useful form. A configured job.
Example requestCollect the request detailsRatelDesk form
Run the configured jobMapped inputs · NetRatel
Follow the run and its resultLinked request
Example input: team = Research
Run completed · Result available with the request
Run completed · Result available with the request
Keep the conversation in context.
Example ticket chat● Organization-scoped accessSelf-hosted. Fully yours.
Illustrative workflows with sample data · Explore the helpdesk guides ↗
A connected support workflowEmail Microsoft 365 · IMAP · POP3Self-service NetRatel automationAI assistants Netclaw · MCP
The service workspace
Make the next step
obvious.
Keep the request, the conversation and the work together. Give your team the context to move things forward.
Make self-service useful.
Build request forms that collect the right details. Map their inputs to a configured NetRatel job and follow the execution from the request.
Forms for your servicesExplicit job and input mappingsRun status and results
Build a self-service request Bring AI into the work.
Use Netclaw for ticket conversations. Give external assistants a defined role through MCP, with permissions tied to their configured access.
Ticket chat → Connected Netclaw
Assistant tools → RatelDesk MCP
Your access rules → Every operation
Explore AI connections Assistant tools → RatelDesk MCP
Your access rules → Every operation
RatelDesk + NetRatel
From a request
to a finished job.
A request form can be the front door to your automation. Collect the details in RatelDesk, map them to a reviewed NetRatel job, and follow its progress.
Your helpdesk owns the service request. Your orchestrator runs the configured work. The connection keeps them together.
Connect forms to automationIt works in the other direction too: turn a NetRatel monitoring alert into a RatelDesk incident. See the integration →
Example self-service workflow
Create a team workspace
TeamResearch
Workspace nameProject Atlas
Details collected by your request form
NetRatel · Configured job + inputs
Follow the resultRun status linked to the RatelDesk request
Define the job. Review the mapping. Make the service available.
Meet people where they work
Your helpdesk assistant.
In Microsoft Teams.
Connect a Teams-enabled Netclaw deployment to RatelDesk through MCP. Let people ask questions and work with the helpdesk data and actions their configured identity can access.
The guide covers the Teams connection, the RatelDesk credential and a first permitted read.
Set up Teams + NetclawHelpdesk assistantMicrosoft Teams + Netclaw
ExampleIllustrative conversation · Requires a Teams-enabled Netclaw deployment
Connected by design
One helpdesk.
More ways to work.
Use the browser, your terminal or an assistant. Connect mail and automation through explicit configurations, with access you can review.
Find your integration pathStart here
A clear path
to your first request.
Deploy your helpdesk. Connect a mailbox. Add the tools you need.
01 / SERVERDocker Compose · Self-hosted
Start with the release bundle.
Download the deployment files, verify the checksum and follow the first-run setup. These guides target the current v0.1.2-beta.17 preview.
curl -fLO https://github.com/BostonTechnologies/rateldesk/releases/download/v0.1.2-beta.17/rateldesk-deployment-0.1.2-beta.17.tar.gzChoose your storage, configure the instance and create the first administrator.
Follow the deployment guide02 / EMAILMicrosoft 365 · IMAP · POP3
Bring the support mailbox with you.
Choose a mailbox connection and its organization routing. Configure incoming and outgoing mail, then follow a test message through the helpdesk.
1. Connect the mailbox
2. Review routing and delivery settings
3. Test a new message and a reply
2. Review routing and delivery settings
3. Test a new message and a reply
The mail guides cover authentication, threading, imports and delivery history.
Set up email support03 / ASSISTANTScoped tools · Explicit access
Give your assistant a defined role.
Choose remote HTTP MCP or a local stdio connection. Use the correct credential purpose and bind access to the intended organization and account.
HTTP Assistant → RatelDesk MCP → API
stdio Assistant → local process → API
stdio Assistant → local process → API
Start with authentication and a permitted read before using actions.
Choose an assistant connectionDocumentation that gets to the point
Find the next thing you need.
01 / DEPLOY
Run it your way.
Compose, storage, HTTPS, backups and upgrades. Choose the setup that fits your environment.
Deployment scenarios 02 / AUTOMATEMake requests actionable.
Build service forms and connect them to the right NetRatel job, with useful inputs and visible results.
Self-service automation 03 / UNDERSTANDSee how it fits together.
Understand the architecture, identity model and integration boundaries before extending your setup.
Architecture & referenceBuilt by Boston Technologies
Own your service desk.
Deploy RatelDesk. Connect your team. Give every request a clear next step.
