All of Rebill's support, connected to all of Rebill.
Rebill is the payments infrastructure for the Americas: companies get paid across the continent, their customers pay in their own currency with their local payment methods, and they receive their funds wherever they want. Billy, its StudioChat agent, serves merchants and their customers over email, widget and Slack from Pylon, queries Rebill's database without asking engineering for endpoints, and Henry runs it from Claude.
Who Rebill isPayments infrastructure for the Americas, with a single API
Rebill is the payments infrastructure for the Americas. With a single API, companies charge their customers in local currency with local payment methods in six countries (PIX, Boleto, PSE, SPEI, bank transfers, QR and wallets), accept cards across the continent and settle wherever they want.
It adds installments, subscriptions and failed-payment recovery. And support designed to never hold anyone back: it uses technology to answer as fast as possible, and there's always a person available when needed.
That breadth is exactly what makes its support hard: the right answer depends on the country, the method, the local provider and how each merchant processes.
Six markets
Local payment methods in six countries and cards across the continent.
Local methods
A refund via PSE in Colombia isn't handled like one via SPEI in Mexico or Boleto in Brazil.
One-time payments and subscriptions
A single merchant can have payments, subscriptions, balances and payouts in several currencies.
Two audiences
Merchants write in, and so do their customers who paid through Rebill.
Henry was solving the same thing, over and over
Henry runs support, operations, providers and merchant integrations. But most of his day went to tickets he already knew how to solve: the same playbook, query after query. Growing the operation was left for whenever there was time, and there wasn't.
The same playbook
Example ticketWhat's the status of my account verification?
- Identify the merchant by their email
- Find the payment, payout or KYB in the database
- Cross-check it with what the provider reports
- Write the reply
- Classify and close the ticket in Pylon
Every ticket, the same steps.
Henry's week
Operations eat the week. What grows the business fits in the gaps.
Illustrative.
Billy works in the same inbox as the team
Rebill already handled support in Pylon, and it stayed there. Billy joins each ticket as one more agent: it replies in the same thread the team sees, with no separate dashboard and no conversations to go find somewhere else.
The highest-volume channel. Billy writes like an email, with a greeting, a full body and a signature, and doesn't greet again in a thread that has already started.
Chat widget
On Rebill's website. Short, direct answers in chat style.
Shared Slack
In the Slack Connect channels Rebill shares with its largest merchants, where a fast answer matters more than anywhere else.
On every ticket, Billy also:
Classifies it
Writes the merchant's tier, the priority and the organization into Pylon before replying, so the SLA is right from the first message.
Filters the noise
Spam, auto-acknowledgements and other tools' surveys get tagged without a reply, so no ticket sits open with the SLA running.
Hands off with context
If the case needs a person, it assigns it inside Pylon with the ticket number, the topic and what it already looked up.
Billy is connected to Rebill's systems
Before replying, Billy sees the real status of every payment, balance, payout, subscription or verification, the same way someone on the team would. And without adding work for engineering.
Connected to operations
Billy answers with each merchant's actual account data, not with generic replies.
Safe by design
Billy looks things up, never changes them, and sees only what it needs to answer.
Grows with every connection
Adding a new connection adds a case Billy resolves on its own, without engineering building anything.
From ClaudeHenry maintains Billy without leaving Claude
Henry already worked in Claude all day: routines, analysis, answers. Instead of asking him to learn another dashboard, we brought StudioChat there. With the StudioChat MCP, Claude reads Billy's conversations, writes skills, builds tools from a spec and prepares new versions.
Nothing reaches production without Henry: every change Claude proposes becomes an approval he reviews and activates, from Slack too.
Looks at real conversations
Claude ranks the support cases and finds where Billy escalates too much or says something that's no longer true.
Changes skills and tools
That's how the handoff message was rewritten, Billy stopped replying to noise, and the knowledge bases that no longer matched the product were switched off.
Henry approves
The change arrives as an approval that says what changes and why. The new version ships when Henry activates it.
“We automated 60% of what reaches our support inbox. Today I'm the only person dedicated to customer support for more than 200 accounts, and that's possible thanks to Billy. The time that used to go into repeated tickets now goes into the business.”
Does your team already live in a helpdesk and in Claude?
Add an agent without switching tools or adding work for your engineering team.
Let's talk