Skip to main content
Fruxon for customer support

Take the load off your support team.

AI agents answer your customers on WhatsApp, chat and email, and do the work in your systems: the reset, the refund, the order fix. What needs a person reaches your team ready to work.

  • One inbox for the agent and your team
  • You choose what it does alone

Works with the tools your support already runs on

WhatsApp
Gmail
Outlook
Slack
Microsoft Teams
Stripe
Shopify
HubSpot
Salesforce
Confluence
Notion
Telegram
Jira

Live in production

Already taking real support load.

businesses served
330
requests worked
5,000+
of hand-offs arrive with the customer already identified
87%
of hand-offs closed by the team
93%

Real production figures from one customer, June to November 2026.

Why the queue grows

The fix takes a minute.Getting to it takes a day.

A locked account. A double charge. An order that won't go through. Each one waits until someone reads it, asks the customer who they are, checks three systems, and then fixes it or forwards it.

Most of your team's day goes into looking things up and passing them on.

Support inbox · Monday 09:004 of 312
#48213
Can't log in, account locked
Waiting for a first reply
3 h
#48207
Charged twice this month
Forwarded to billing
1 day
#48190
Order fails at checkout
Asked the customer for an account ID
2 days
#48166
Change the account owner
Nobody owns it
4 days
What it takes off your team

The repetitive work, done end to end.

Not just the reply. It does the work in your systems, on the channel the customer used.

Questions and how-tos

Answers from your docs, policies and past conversations, and turns new answers into articles. When nothing covers the question, it says so instead of making something up.

ConfluenceNotionGoogle DriveSharePoint

Accounts and access

Unlocks accounts, resends reset links, changes emails and seats, within the permissions you allow.

Your admin systemHubSpotSalesforce

Billing and refunds

Finds the charge, explains it, and refunds it up to your limit. Above the limit, it asks whoever owns billing.

StripeSlack

Orders and delivery

Order status, address changes, failed orders. It retries what it's allowed to and sends the tracking link.

ShopifyYour admin system

Screenshots and voice notes

Customers send a photo of the error or a voice message. It reads the screen and transcribes the audio.

WhatsAppTelegramChat on your site

Ready hand-offs

What needs a person lands in your team's inbox, at the right desk, with who, what and what's been tried. Your team can take over any chat and hand it back.

Team inboxSlackMicrosoft Teams
When it needs a person

It doesn't guess.It asks the owner, once.

When a ticket isn't its call, it asks the person who owns that call, where they already work, then finishes the job.

It finds the gap.

Northwind Café was charged $149 twice. It finds both charges and the cause. The refund is over its $100 limit.

Ticket #48207 · double charge
Customer found · Northwind Café · admin
Two charges of $149 · Nov 3 and Nov 4
Cause: a payment retry after a card update
Refund $149 · over its $100 limit
Refunds over $100 are Emma's call.

It knows who owns the call.

Billing goes to Emma, failed orders to the Ops desk, bugs to engineering. Not to a shared inbox.

Who owns what
Refunds over $100ECEmma ClarkeSlack
Plan and pricing exceptionsDMDavid MillerTeams
Failed ordersOPOps deskTeam inbox
BugsENEngineeringJira

She answers in a line. It does the rest.

One message with everything she needs. It refunds, answers the café and solves the ticket.

Slack · to Emma Clarke, billing
Fruxon agent10:15
Northwind Café was charged $149 twice (a payment retry). Refund the second charge?
Refund itDon't refundI'll take it
EC
Emma Clarke10:22
Refund it. Double charges are always ours.

Emma answered once. She won't be asked again.

Her answer becomes a rule, reviewed before the agent uses it. The next double charge is refunded on its own.

The first double charge

7 min

Asked Emma on Slack

The next one, a week later

40 sec

Same case · nobody asked

Every answer works that way. Your team is left with the cases nobody has seen yet.

You stay in control

You decide what it does alone.

Only what you allow.

Refunds up to $100, yes. Plan changes, never. Anything not on its list goes to a person.

Take over any chat.

Anyone on your team can step in on the same thread, and hand it back when they're done.

Everything on the record.

Every message and action, who approved it and in what words, and what each conversation cost.

Security, certifications and subprocessors, kept current in one place.

Visit the Trust Center

Questions support teams ask

Have more questions? Contact us

Start free

Start with the tickets your team is tired of.

Connect your docs and one channel, test it on real questions, and go live when you're ready.

Start Free