Customer Inquiries in a CRM: Every Channel in One Inbox

A unified CRM inbox brings WhatsApp, calls, website forms, social media messages and email into one list, where every inquiry has an owner, a status and a reply deadline your business sets for itself. In part two we built the single customer record; this third part of Digitizing CRM, a 7-part series, routes everything arriving through the five doors into it: how each door enters the inbox, 5 routing rules that decide who takes which inquiry, why conversations belong on the company's number rather than an employee's, and where a chatbot helps and where it must hand over to a person, with an exercise that exposes the channels nobody watches after hours.

One inbox for every door: what it means in practice

A unified inbox does not shut any channel down. Your customers keep messaging you on WhatsApp, calling, and filling in the form on your website as they always have. What changes is what happens after their message arrives: instead of settling on the phone of whoever read it, it appears in one list the team can see, linked to the sender's record if they are known, or creating a new record if this is a first contact. Each door comes in its own way:

• WhatsApp. The company number is connected to the inbox through the official interface, so more than one employee can answer it from one place, and the conversation stays filed under the person who wrote rather than on a particular phone.
• Calls. When the phone system (the PBX) is connected, every missed call becomes an inquiry waiting for someone to call back, and every answered call becomes a line with a short summary written by whoever took it.
• Website forms. Every submitted form creates an inquiry directly, instead of going to a general mailbox someone opens when they remember.
• Social media messages. Direct messages to the company's accounts land in the same list, rather than staying with whoever runs the account, who is usually not the person who sells.
• Email. The company's general address forwards into the inbox, so every email becomes an inquiry with an owner.

When a form or a chatbot collects someone's details for the first time, that is a moment of personal data collection. Article 12 of the Personal Data Protection Law requires the controller to adopt a privacy policy and make it available to data subjects to read when their data is collected, and Article 13 lists 7 elements the data subject must be informed of when collection begins, including the legal basis, the purpose of collection, the identity of the collector and their rights under Article 4 (our reading of the official Arabic text). In practice: a clear link to your privacy policy next to the form and in the first automated message, and ask the form only for what you need to reply, as Article 11 requires.

Every inquiry gets an owner, a status and a reply deadline

Gathering messages in one place is only half the answer. A shared inbox with no owner turns into a place where every employee assumes a colleague will reply. So every inquiry carries 3 things from the moment it arrives:

• One named owner, not a department or a group. They can pass it on, but the hand-off itself is recorded and shows who holds it now.
• A clear status, and 5 are enough: new, assigned, waiting on us, waiting on the customer, and closed. Closing has a reason too: answered and done, turned into a lead we follow in part 4, or into a service request or complaint we follow in part 5.
• A reply deadline, sometimes called an SLA (service level agreement): a time commitment the business sets for itself, covering how soon the first reply goes out during working hours and what happens to anything that arrives after them.

There is no single correct reply deadline that fits every business, and we will not hand you a number from outside your own operation. What works is measuring your current first-reply time for a week, choosing a deadline your team can genuinely keep, and deciding what happens when it is missed: the inquiry turns red, then moves to the supervisor if it is still unanswered. Each month, compare the deadline with reality, and tighten it once the team has shown it can keep it.

Routing rules: who takes which inquiry

When an inquiry arrives, who decides where it goes? If the answer is the manager when they have a moment, we are back to waiting. Routing rules are written once, then the system applies them automatically. Start with five rules in this order:

• A known sender goes to their owner. If the sender has a record with a relationship owner, as described in part two, the inquiry goes straight to that person.
• A new one goes by request type. A product question to sales, a maintenance request to the service team, a complaint to whoever handles complaints. If you have branches, city becomes an extra rule.
• Rotation among those available. When more than one employee qualifies, inquiries are shared out in turn, so the work does not pile up on the fastest responder.
• A backup for absence. Every employee has a backup set in advance for leave and outside their hours, so nobody waits for a colleague to come back from holiday.
• The supervisor's queue for anything no rule covers. No inquiry is left without an owner: whatever matches no rule goes to the supervisor to assign by hand.

After hours in particular, write an explicit rule: does someone on duty reply, or does an automatic message tell the sender when they will really hear back, with the inquiry waiting at the top of the list in the morning? The only wrong answer is leaving it undecided. We discussed what a message that waits until morning costs you in your customer is asking on WhatsApp right now: who is answering?

The company's number, not the employee's

The most dangerous door on the list is the salesperson's personal mobile, not because salespeople misuse it, but because the whole relationship is built on a number the business does not own. When the salesperson leaves, their customers keep messaging that number, and nobody in the company can see what was promised or what each of them is waiting for. The answer is not to stop salespeople talking to customers; it is for the conversation to happen from the company's number connected to the inbox, so it stays with the business when people change, and the backup picks it up with the full history in front of them.

The company number itself is an asset that needs protecting: use each channel's official interfaces, and do not rely on unofficial sending tools that can get the number banned. We covered why bans happen and how to prevent them in WhatsApp account bans: why they happen and how to protect your account.

There is a legal reason too. Article 1 of the Personal Data Protection Law counts as personal data any data, whatever its source or form, that leads to identifying an individual, including names, addresses and contact numbers. Article 19 requires the controller to take the necessary organisational, administrative and technical measures to safeguard personal data, including when it is transferred. A conversation on a personal phone, outside any permissions, achieves none of that. In the inbox, permissions are written down: a salesperson sees their own inquiries and their customers' inquiries, the supervisor sees everything and reassigns, and export is limited to a few people, with a log of who did what and when. This is not legal advice, so confirm the details with SDAIA or a lawyer.

Chatbots: where they help and where they hand over

A chatbot, an automated responder that understands a message and answers it, is useful in a unified inbox provided it knows its limits. It helps in 4 places:

• Confirming receipt immediately, and telling the sender when the real reply will come according to the deadline you set, not with a promise you will not keep.
• Answering repeated questions from answers the business has approved: opening hours, location, required documents, the status of an existing order.
• Collecting the basics before an employee steps in: name, need and city, saved to the customer record so the employee does not ask again.
• Routing the inquiry to the right team under the rules above.

It must hand the conversation to a person in 4 situations: a complaint or an upset customer; a request for a discount, an exception or any commitment on price or date; a question it cannot find in the approved knowledge, so it never invents an answer; and an explicit request to speak to someone. A proper hand-over passes the whole conversation to the owner, so nobody has to tell their story again from the start. We explained what can be automated and how it is built in automating customer service with WhatsApp and AI chatbots. And if the inbox or the chatbot is run by an outside provider, Article 8 requires you to choose a processor that provides the guarantees needed to apply the law, and to verify that it complies.

The Origami view

We are a technology company that builds custom systems, apps and integrations, and in customer management projects we do not start with a screen but with a map of the doors: every number, account, mailbox and form a customer reaches you through, who watches it today, and where its conversations go. Then we connect those doors to the inbox through their official interfaces, and write the routing rules and deadlines with your team before switching them on.

We design the inbox to write into the customer record described in part two, with permissions and a change log from day one, and we add a chatbot where it genuinely saves time, with a clear hand-over to a person. What we build is described on our services page.

Exercise: every door and who watches it after hours

This is an exercise you can run in one session with your team, and it shows where your customers stand with nobody there:

• List every door a customer can reach you through today: WhatsApp numbers, landlines, salespeople's mobiles, social media accounts, email, website forms, and the number published on Google Maps, on invoices and on your vehicles.
• Give each door 4 columns: who watches it during working hours, who watches it after hours and on holidays, where its conversations are kept, and whether a manager can see them.
• Send a test inquiry from a number the team does not know to every door on a working-day evening, and record when the first reply arrived and from whom.
• Mark every door with no one watching after hours, and every door whose conversations live on a personal phone.

The number of doors with no one watching, and the number living on a personal phone, are the two figures you start from. The list itself is your connection map for the inbox: every line on it is a door that must feed the one list.

In the next part

Every inquiry now has a place, an owner and a deadline. What remains is everything after the first reply: many inquiries come from prospects who need following up for days or weeks. Part 4, Lead Follow-Up: Clear Stages Instead of Memory, turns follow-up into defined stages from new inquiry to won or lost deal, with a next step and a date on every opportunity.

Sources

• Personal Data Protection Law — Saudi Data and AI Authority (SDAIA) — Article 1 on the definition of personal data, Article 8 on choosing a processor, Article 11 on minimum data, Article 12 on the privacy policy, Article 13 on informing the data subject at collection, and Article 19 on safeguarding data, including when it is transferred.