A customer writes an email in the morning, sends a message at noon, and calls by phone in the evening. These three messages coming from three different channels sit in three different places.
The result is familiar: two different answers are given to the same question, or no answer is given at all.
In this article, we explained the single inbox structure, the sequence logic, and the auto-stop rules.
Table of Contents
What is a unified inbox?
A unified inbox is the gathering of messages coming from different channels into a single list.
Messages are grouped by customer, so the entire conversation is seen together regardless of which channel it came from.
This structure eliminates duplicate replies and unanswered messages.
It also provides internal team visibility; everyone knows who is handling a message.
The conversation history is also logged into the customer record; see the customer 360 view article.
Message distribution and ownership
The biggest risk of a shared inbox is that a message everyone is responsible for is no one's responsibility.
Therefore, every message must have an owner. Ownership can be assigned manually or via rules.
If the customer has an existing representative, the message should be directed straight to them; relationship continuity requires this.
For new customers, round-robin distribution or topic-based routing can be used.
A time alert should be set up for unanswered messages; a pending message must be caught before it turns into a lost message.
What is a sequence?
A sequence is a communication flow consisting of predefined steps. Each step is sent automatically with a specific delay.
The goal is to ensure follow-ups are not forgotten. Most sales close not on the first contact, but on the third or fourth.
Manual follow-up is the first thing skipped during busy periods. Sequences fill this gap.
However, sequences do not replace humans; they merely automate reminders and initial steps.
We covered message content and channel selection in the outreach article.
Step design
A good sequence consists of a small number of steps. Three to five steps are sufficient for most scenarios.
The time between steps should gradually increase; the first follow-up a few days later, and subsequent ones at wider intervals.
Each step should offer a different angle. Repeating the same message does not increase interest.
Human tasks can also be added between steps; a phone call is more effective than an automated message.
The final step should include the closure of the flow; it must be clear where the record goes when no response is received.
Auto-stop rules
The most critical setting for a sequence is when to stop. A poorly configured stop rule causes serious damage.
When a customer replies, the flow must stop immediately. Sending an automated follow-up message to someone who has already replied damages the relationship.
When an opt-out request is received, the flow must also stop and the permission record must be updated.
It is also logical for the flow to stop when a customer places an order or opens a service request; the context has changed.
These rules are defined by automation; refer to the automation rules article.
Tone and frequency balance
The biggest risk of automated flows is appearing pushy. The fine line is determined by frequency.
Sending three messages in the same week increases annoyance rather than interest.
The content of the messages must also carry value; instead of asking for something in every message, sometimes providing information establishes the balance.
It must also be ensured that the same person does not enter multiple flows; overlapping flows produce a bombardment of messages.
This control is done with a per-person flow count limit.
Measurement
Sequence performance should be measured on a step-by-step basis. Knowing which step brings responses provides the opportunity to shorten the flow.
In most flows, the majority of responses come from the first two steps; subsequent steps provide diminishing returns.
The rejection rate should also be monitored step by step; increasing rejections after a certain step indicate that the frequency is too high.
Response time in the inbox should also be measured; fast response directly increases conversion.
Reports are monitored in the CRM module.
Setup steps
The first step of setup is determining which channels are actually used. Connecting an unused channel only adds complexity.
The second step is clarifying the account structure of the channels. Communication conducted through personal accounts should be moved to corporate accounts.
Correspondence remaining in personal accounts is lost when an employee leaves; this is one of the most frequently experienced data losses.
The third step is defining distribution rules. Which message will fall to whom must be determined from the beginning.
The fourth step is setting the response time target. A target that is not measured does not change behavior.
The final step is reviewing existing templates; old texts are often outdated.
Common use cases
Proposal follow-up. A two- or three-step follow-up flow after a sent proposal noticeably increases the response rate.
Customers who have not made a purchase for a long time.An automated flow that kicks in after a certain period revives dormant relationships.
New customer onboarding.Informational steps sent after the first order reduce the support load right from the start.
Post-fair follow-up.Processing collected business cards in the first few days directly impacts conversion.
Payment reminder.A polite reminder before the due date prevents a significant portion of delays.
The common feature of these scenarios is that the flow pauses at points requiring human intervention.
Frequently asked questions
Which channels can be gathered in a single inbox?
Common email and messaging channels can be configured; we determine the scope together during setup.
Can there be manual intervention in the middle of a sequence?
Yes, it can; the flow can be paused and continued with a personal message. This often yields better results.
Are phone calls also logged?
They can be saved as call notes, so the entire contact history is gathered in one place.
Can messages be transferred within the team?
Yes, they can; the change of ownership is logged, and the history is transferred to the new owner.
A unified inbox and sequence are two complementary structures that make communication both organized and trackable.
The most critical setting during setup is the pause rules. Sending automated follow-ups to someone who has replied causes you to lose earned interest.
Configure every message to have an owner from the start; an unowned message means an unanswered message.
Keep the number of flows limited as well. Sending messages from multiple flows to the same person is the quickest way to get rejected.
Do not neglect step-by-step measurement; most flows stop delivering returns after the first two steps and drag on unnecessarily.
Start the setup small: a single channel, a single flow, and three steps. A system established at this scale is much more suitable for expansion.
By talking with the EQLEM teamyou can plan your communication flows.