Hashting.
#ConsumerCare by Hashting: Always-On Programme

A small refund shouldn't become a big job.

Your care team solves the complaint. But paying the customer can mean Finance requests, approvals, bank details and days of follow-up. Hashting gives your team a simpler way to arrange consumer refunds, without turning customers into suppliers or touching your ERP.

1,800+ refunds paidNo ERP integration
See how it works
How it worksExample
Maria complains"I'm so sorry, we'll make this right."Step 1
Agent starts a €4.50 refundStill on the call.Step 2
Approver adds a codeYour rules, your decision.Step 3
Maria gets her money back"Thank you, that was easy."Step 4
No emails to Finance
Happy customer
Live since 2023
Real teams use it every day
Safe and certified
ISO 27001 and GDPR. Agents never see bank details
No IT work
Nothing to plug into your systems
5 languages
Forms and messages in your customer's language
The problem

Your agent did the work but can't close the case.

The problem isn't your team. It's a refund process that won't let them finish.

"Five, ten departments, just to pay one person. It's a mess."
Consumer Care lead, European pet food company active in 5+ countries
The case stays open

The customer is happy with the fix. But the refund waits on a system or an approval, so the ticket stays open.

One refund, many departments

Finance, master data, treasury. A small refund turns into forms, sign-offs and a customer set up as a supplier.

The customer can't get paid their way

Many people won't share an IBAN by phone or email. Your agent has no other way to offer.

How it's done today

Three slow ways brands pay refunds today.

Workaround 1

Send a product pack

Warehouse requestPickPackShipTrack
Hidden cost: Packing, shipping, tracking. And the customer just wanted their money.
Workaround 2

Manual bank transfer

Create supplierERP master dataFinanceApprovalPayment run
Hidden cost: Your customer becomes a supplier in your books. Up to 10 departments for a few euros.
Workaround 3

Voucher / gift card

Buy voucherSend codeConsumer must shop again
Hidden cost: It feels like an insult: "You messed up, and now I have to shop with you again?"

The Hashting C.A.R.E route

  1. 1Customer complains
  2. 2Agent clicks once
  3. 3Boss says yes
  4. 4Customer adds bank details
  5. 5Money arrives in days
How it works

Your agent can start the refund while the customer is still on the line.

Your agent's part is done

Your agent starts the refund from the call. The approver and the customer take it from there, so your agent is not chasing anyone.

One request, one approver

No supplier setup, no master data, no payment run. An approver adds a code and Hashting pays.

The customer picks how to get paid

Bank, PayPal, Bizum or Twint, depending on the country. They type it in themselves.

Customer care agent with headset creating a refund request during a call
Your agent
  • Starts the refund on the call.
  • Never hears bank details.
  • No emails to Finance.
Your Care lead
  • You set the rules.
  • You see every payment.
  • Less refund follow-up for the team.
Your consumer
  • No account, no app.
  • Pays the way they like.
  • Gets updates by SMS or email.
Your company
  • No IT work.
  • Used by FMCG brands for 3 years.
  • Works in 5 languages.
The agent form

One short form starts every refund.

  • Case number, customer name, brand and amount.
  • In English, Spanish, Portuguese, French or Italian.
  • The approver adds a code later. Your agent is done.

Example form for a pet food brand.

  1. 1Your agent fills in the form
    Refund request form an agent fills in during a call
  2. 2Your customer gets a link
    SimulationSimulated text message telling a customer their refund is ready
See the full flow
Case study · European pet food company, 5+ countries

Your team stops chasing other departments for refunds.

Multiple brandsMultiple languagesMultiple agents
One shared screen for agent, approver and customer.
1,800+ refunds
paid without adding customers as suppliers
One small refund
  1. 01Agent sends it during the call
  2. 02Boss says yes with one code
  3. 03Customer gets a link and adds bank details
  4. 04Hashting pays from your pot
  5. 05Your team stops chasing the refund
Customer story

Six agents and four approvers handle refunds in four languages.

The team sells online across France, Italy, Spain and Portugal. They work per language, not per country, so they never know where the next complaint comes from.

A refund outside the euro zone meant adding the customer to their systems as a supplier. Five to ten departments, for one payment. And many customers simply didn't want to share their bank number.

Now the agent sends a link. The customer adds their own details. In Spain they can choose Bizum, which even older customers already use. "Some people are very happy because they receive the payment back very fast."

Payment methods & coverage

Customers pick how to get paid. You pick the countries.

SEPA Bank TransferPayPalBizumTwint

It's simple. Mix any countries, languages and payment methods. Each customer sees the payment options that work in their own country.

For your colleagues

Your Finance, Legal and IT teams will ask this.

Here are the short answers.

Finance

  • You fill one pot up front. Refunds come out of it.
  • You see every payment and what's left.
  • No customer ever becomes a supplier.

Legal & privacy

  • ISO 27001 certified and GDPR safe.
  • Customers type their own bank details.
  • Agents never see bank data.

IT & security

  • Nothing to plug in.
  • Runs outside your systems.
  • Bosses approve with a code.
Pricing

Refunds that sort themselves out, every day of the year.

No campaign to launch. No project to restart. The programme is always on, so your team never has to think about how the next refund gets paid. The refund money comes from your own pot.

Pilot
€5,000

Up to 2,500 payouts for one team, brand or country, excluding the refund money. No IT work.

  • Cases close without waiting on finance.
  • No customer set up as a supplier.
  • Customers choose how they get paid.
FAQ

The questions everyone asks us.

Karl De Beul, co-founder of Hashting, explaining the platform Hashting.

"This approach is absolutely revolutionary."

Karl De Beul, co-founder Hashting

Let's draw your current refund path together. Most teams are shocked how long it is.

You set the amounts and the rules. Your bosses approve with a code. Hashting never decides who gets paid.

20-minute working session

Let's draw your refund path in 20 minutes.

Bring your refund rules, who approves, and how many cases you get. We show you the old way and the fast way.

  • Your rules, checked
  • Your approvals, cut to one code
  • Your price, clear
See the free demoDiscuss your programme

Or email Adriana, commercial lead: adriana@hashting.com

Check your CARE score

C
Complaint
A
Approval
R
Refund
E
Execution

How fast a complaint turns into a paid refund.