Hi, I wanted to know how much it costs…
ABIERTODIGITAL MANAGEMENT · FICTIONAL CASE STUDY
The problem was not a lack of messages.
It was not knowing what needed to happen after each one.
A small company handles enquiries through Instagram, WhatsApp, email and a web form. People write. The team replies. Even so, some conversations begin to demand too much memory.
The company, people and conversations in this sample are fictional. The case demonstrates a customer-care and follow-up logic; it does not claim real sales, response times or commercial results.
Do you have availability on Thursday?
READHi, I wrote to you last week…
PREVIOUS THREADI’d like a quote for a service…
PENDINGSENSORY DEMO · OPTIONALDemo sonora opcional
01 · MONDAY · 09:12 — 11:43
Messages do not arrive as a system.
They arrive by interrupting things.
Before talking about tools, we observe what happens to attention when each conversation appears in a different place and at a different time.
“Hi, I wanted to know how much it costs…”
You open it over breakfast. It remains pending.
“Do you have availability on Thursday?”
You read it while doing something else. It no longer appears as new.
“Hi, I wrote to you last week…”
To reply, you have to find the previous thread and reconstruct what they had asked for.
“I’d like a quote for…”
Another enquiry. Another inbox. Another place where you have to remember something is pending.
Four people had written.
The problem was that each conversation still lived in a different place.02 · THE AUDIT REVEALED THAT…
There was no lack of willingness to reply.
What was missing was a shared logic for knowing what to do with each conversation.
We did not begin by asking which CRM to install. We began by asking what the team needs to know so a conversation does not depend on one person’s memory.
Entry
Enquiries arrived through different channels with no common point from which to understand what had come in.
Status
Reading a message did not tell you whether it was resolved. There was no visible difference between new, replied, waiting for information or pending follow-up.
Context
Every time a conversation resumed, someone had to remember who the person was, what they had asked for and what had been said.
Next action
The conversation could stop after a reply even when something still needed to happen.
THE REVEAL
Replying is not the same as managing.
A conversation is organised when you know where it is, what has happened and what needs to happen next.03 · HOW DID WE ORGANISE IT?
We took memory out of people’s heads
and turned it into a visible sequence.
IGInstagramWAWhatsApp@EmailFForm
→
01Entry
The enquiry enters a common flow.
→
02Context
We know who is writing, what they need and what has happened.
→
03Status
The conversation occupies a clear position.
→
04Next action
What needs to happen next becomes visible.
We designed a logic so every enquiry, whatever channel it comes from, becomes part of the same customer-care journey.
Each conversation retains who is writing, where from, what they need and when it arrived.
We assign it a status the team can understand at a glance.
If something still needs to happen, the conversation keeps a next action.
We also define how and when to reply according to the channel, keeping a coherent voice without treating a DM, email and form as if they were the same thing.
04 · THE SAME CONVERSATIONS. FEWER THINGS TO REMEMBER.
Lucía, Álvaro, Marta and Daniel are still there.
What changes is what the team needs to keep in their heads.
The messages and channels do not disappear. Part of the uncertainty about each conversation’s status does.
IG
LucíaInstagram
Asks about prices.
WA
ÁlvaroWhatsApp
Asks about availability on Thursday.
@
MartaEmail
One piece of information is missing to continue.
F
DanielForm
Quote sent.
BEFORE“Who did I still need to reply to?”→AFTER“Which conversation needs an action now?”
05 · THE SYSTEM IS NOT THE SOFTWARE
Tools change.
The customer-care logic remains.
This sample does not propose a specific platform. Depending on the business, the system could live in tools already in use or require another solution.
What we design here is the logic of customer care, follow-up and continuity: who needs a reply, what context must be preserved, what status the conversation has and what the next step is.
06 · WHAT THIS SAMPLE DEMONSTRATES
Managing messages is not just replying to them.
It is designing what happens from the moment someone writes until their need has been addressed.
STORYTELLING AND VIDEOInside the message.MARKETING AND CONTENTBetween a search and an answer.DIGITAL MANAGEMENTBetween a conversation and the next action.
In a real project, operational improvement would need to be verified with business data: response times, pending conversations, follow-ups completed and commercial results. This sample does not claim those results; it shows how we would design the customer-care and follow-up flow for a brand.
YOUR CUSTOMER CARE · YOUR FOLLOW-UP
Do your clients write through several channels and you feel as though you are always chasing conversations?
We can review how enquiries enter, what needs to be preserved and what system would make the next step clearer.