Move from Gladly to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
Gladly conversations with their items, customers, topics and Answers move to Rinhelp. Gladly can’t list every customer, so the import starts from a list of emails, phone numbers or external IDs, or from an export made by Gladly Support.
| Conversations | Time to read them from Gladly |
|---|---|
| 1,000 | about 4 minutes |
| 10,000 | about 34 minutes |
Limit used: 600 requests a minute (10 per second for each kind of call), 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. Only Gladly Support can make a raw transcript export reaching further back than 7 days, so ask them early. Someone also creates a Gladly API token for your AI agent.
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.
I haven’t found an official Gladly MCP server, so I’ll upload the zip from Gladly’s export tool here. Follow https://rinhelp.com/migrate/gladly.md, import the conversation items and topics from its JSON Lines files, and copy my Answers from the public Gladly help center.
Use my Gladly API token over basic auth and https://rinhelp.com/migrate/gladly.md to bring every conversation into Rinhelp. Look customers up by email, phone or external ID, 50 at a time, then fetch each customer’s conversations and each conversation’s items, up to 1,000. Stay under 10 requests a second for each kind of call.
Their words and ours
| In Gladly | In Rinhelp |
|---|---|
| Conversation | Conversation |
| Conversation item | Message |
| Customer | Customer |
| Agent | Teammate |
| Topic | Tag |
| Answer | Article |
What stays behind
- Routing and inbox rules
- Sidekick and AI settings
- Reports
- Lookup adaptors
Gladly facts that shape the move
Gladly’s default limit is 10 requests a second for each kind of call. Source, checked .
The whole organization shares one limit, each response shows what is left, and going over returns an error. Source, checked .
The self-serve export tool covers only the last 7 days. Source, checked .
A raw transcript export for all time, or for several days, comes only from Gladly Support. Source, checked .
Each export job is a zip of JSON Lines files for teammates, conversation items, customers and topics. Source, checked .
Gladly’s export tool is still a beta feature. Source, checked .
There is no call to list all customers; you look them up by email, phone number or external ID, at most 50 profiles at a time. Source, checked .
A customer’s conversations come from one call with no pages, then each conversation’s items from another, up to 1,000. Source, checked .
Answers can be listed over the API, along with a help center’s answer titles by section. Source, checked .
The Gladly API takes a token with basic authentication over HTTPS. Source, checked .
Questions
Can my AI agent pull all my Gladly customers at once?
No. Gladly only finds customers by email, phone number or external ID, 50 at a time, so your AI agent needs that list first, or an export from Gladly Support.
Is Gladly’s export tool enough for my history?
Only for the last 7 days, and it is still in beta. For anything older, ask Gladly Support for a raw transcript export.
Do my Gladly Answers come across?
Yes. They list over the API and become Rinhelp articles, and links to the old answers redirect to the new pages.