Resources · From CRM to CRA
From CRM to CRA. More than a row or a ticket.
CRM gave your customer a row in a database. The omnichannel inbox gave them a ticket in a queue. Pepper, a Customer Relationship Agent, gives them a salesperson who knows them.
CRM
What your customer getsA row in a database
Omnichannel inbox
What your customer getsA ticket in a queue
Pepper
What your customer getsA salesperson who knows them
Built to sell. CRM recorded. The inbox answered.
Each step helped your team. None of them sold for you. CRM and the inbox were built to record and to answer. A Customer Relationship Agent is built to act: to talk to every customer, know each one, and turn the conversation into a sale.
CRM
It stores who bought what. Your team pulls a list, writes a broadcast and sends the same message to everyone.
The customer is a row. Nothing happens until someone runs a report.
Omnichannel inbox
Every chat lands in one place and waits for the next free agent. A bot can route it or answer the common questions.
The customer is a ticket. Served in turn, closed, and started again next time.
Pepper, a CRA
She answers every customer at once, remembers each one, and acts in the chat: the right product, the right reward, the right person on your team.
The customer is a relationship. Every chat makes the next one better.
Four jobs. Done in every chat, at any hour.
The same four jobs your team does today, done in every chat, at any hour, for every customer.
Sells.
BeforeA customer asks, waits, gets a menu, and buys elsewhere.
With PepperShe reads the need, picks one product from your live catalogue, says why, and sends the buy link.
Rewards.
BeforeMembers forget their points and never redeem.
With PepperPoints, vouchers and the best deal they qualify for, right in the chat. New members sign up in about 30 seconds.
Retains.
BeforeThe same broadcast goes to everyone, paid per send.
With PepperAI segments built from what customers actually said, and an offer for each: matched, approved by you, delivered.
Serves.
BeforeMore customers means more headcount.
With PepperAnswers in seconds, in the customer's language. A person on your team takes over when it matters, with the whole chat.
Acts. What a CRM was never built to do.
A CRM waits for your team. Pepper is the one talking to your customers, so what she learns is used in the same conversation, not in next quarter's report.
- Talks to every customer at once, day and night, in English, Malay, Chinese and Tamil.
- Remembers what each one said, on every channel. One memory, one thread.
- Acts inside the chat: the product, the voucher, the nearest outlet, the sign-up.
- Learns from every conversation: what each customer wants goes into their profile and into your AI segments.
- Works through your systems, never around them. She reads your loyalty programme and catalogue, and changes nothing behind your back.
- Gold bangle seekers1,240 members
- Gift buyers under RM1,000860 members
- Quiet for 90 days2,115 members
Row, ticket, relationship. Three ways to look after a customer.
Pepper doesn't replace your CRM or your inbox. She works with both.
| CRM | Omnichannel inbox | Pepper (CRA) | |
|---|---|---|---|
| The customer gets | A row in a database | A ticket in a queue | A salesperson who knows them |
| Memory | Fields your team fills in | Chat history, one ticket at a time | What each customer said and claimed, across every channel |
| Selling | Reports for your team to act on | Agents answer one chat at a time | Recommends from your live catalogue, with a reason and a buy link |
| Rewards | Points stored in the record | Not built in | Points, vouchers, best deal and sign-ups in the chat |
| Marketing | Lists and blanket broadcasts | Broadcasts | AI segments, down to a segment of one. Matched, approved by you, delivered |
| Hours | When your team works on it | When your team is online | 24/7, with a person when it matters |
Why now. Proven abroad. Early days here.
The idea is proven abroad, and most Malaysian retailers using AI are still at the start.
Questions. What CEOs ask us first.
Do we have to replace our CRM or loyalty system?
No. Pepper owns no system, so she connects to the ones you have. She reads your loyalty programme and catalogue, and any change to points or vouchers goes through your loyalty system's own controls, never around them.
How much work is it for my team?
Very little. Fireworks maps your customer journeys, builds Pepper with your persona, knowledge and systems, and runs it. You go live in about five weeks, followed by six months of active tuning.
What does it cost?
It depends on your channels and the systems Pepper connects to, so we quote after the first consult. If WhatsApp is a big channel for you, the WhatsApp cost saver keeps Meta's per-message charges down.
What if she says the wrong thing?
She works inside rules you set: quiet hours, message caps, topics she won't discuss, and she never pushes out-of-stock items or invents a price. Every change is tested on a stand-in customer before it goes live, every product pick shows its reason, and a person on your team can take over any chat.
What about customer data and PDPA?
Pepper reads your loyalty system and changes it only through that system's own controls. You approve every campaign before it sends. Pepper is hosted, secured and backed up by Fireworks.
More reasons. Pepper, from every angle.
Pepper vs inbox AI
Keep your inbox. Pepper is the brain inside it, built for revenue, not routing.
Read more →Pepper vs ChatGPT-style bots
Generic AI is a genius stranger. And Meta's WhatsApp rule has changed.
Read more →WhatsApp cost saver
One paid WhatsApp message, then the chat carries on free. Work out your saving.
Read more →Every customer. A salesperson who knows them.
Book a demo. We set Pepper up with your brand's name and rewards, and you chat with her yourself.
