Move from HelpDesk to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
HelpDesk tickets and their events come over its API, up to 100 tickets a page, or through its read-only MCP. HelpDesk publishes no API limit and has no help center, but its team will raise your limits for a large migration.
| Conversations | Time to read them from HelpDesk |
|---|---|
| 1,000 | no per-minute limit to time it by |
| 10,000 | no per-minute limit to time it by |
Limit used: no per-minute number (no published limit, higher limits on request), about 2 per conversation. Rinhelp takes up to 3,000 conversations a minute.
Free. Importing never emails your customers, never runs Rin and never counts toward a plan.
Needs a person. Make a HelpDesk Personal Access Token, which uses your account ID as the user name, or set up OAuth 2. For a big history, ask HelpDesk’s team to raise your API limits before the AI agent starts.
Paste one prompt
Connect your AI agent to Rinhelp first, then paste the prompt for the app you use. It reads this page’s Markdown and follows Rinhelp’s steps.
Connect HelpDesk’s official read-only MCP at mcp.text.com (in Claude, under “Settings” → “Connectors”) and follow https://rinhelp.com/migrate/helpdesk.md. Bring the tickets and ticket tags I can see into Rinhelp as conversations and tags.
Follow https://rinhelp.com/migrate/helpdesk.md to move every HelpDesk ticket. Sign in with my Personal Access Token, my account ID as the user name, and send a user-agent header on every request. Page tickets 100 at a time and keep following the next cursor to the end, then read each ticket’s events.
Their words and ours
| In HelpDesk | In Rinhelp |
|---|---|
| Ticket | Conversation |
| Ticket events | Message |
| Agent | Teammate |
| Canned responses | Saved reply |
| Tags | Tag |
What stays behind
- Automations
- Reports
- Ticket rules
- Integrations
HelpDesk facts that shape the move
HelpDesk’s API signs in with a Personal Access Token, using your account ID as the user name, or with OAuth 2. Source, checked .
HelpDesk asks every API request to carry a user-agent header, since services in between may block requests without one. Source, checked .
The HelpDesk ticket list pages by cursor, 20 tickets by default and up to 100. Source, checked .
A HelpDesk ticket carries its events, the messages and changes, as a list. Source, checked .
HelpDesk accepts a next or a prev cursor but never both, so the AI agent follows next until the list ends. Source, checked .
HelpDesk includes spam tickets only when asked, and its VIP filter stops counting at 10,000 tickets. Source, checked .
HelpDesk publishes no request limit, and suggests contacting its team to raise API limits for a migration. Source, checked .
HelpDesk’s official MCP finds and lists tickets and their tags, cannot create or change them, and sees only the tickets the connecting person can see. Source, checked .
HelpDesk calls saved replies canned responses, pasted into messages with shortcuts. Source, checked .
Questions
How fast can HelpDesk tickets move?
HelpDesk publishes no request limit, so the time depends on yours. For a large history, ask HelpDesk’s team to raise your API limits, then the AI agent reads 100 tickets a page.
Why does the AI agent miss tickets I can see in HelpDesk?
Spam tickets come back only when the request asks for them. Through the MCP, the AI agent also sees only the tickets the person who connected it can open.
HelpDesk had no knowledge base. What does Rinhelp answer from?
The AI agent reads your public help pages or website into Rinhelp as articles and a knowledge source, so Rin has something to answer from.