Narrow candidates with alternate identifiers (name, rough purchase date, part of the delivery address) and ask a person to confirm this is the right person, and do not match on your own and expose someone else's data.
Customer inquiry intake
New inquiries, repeat ones, the urgent ones, and real sales opportunities arrive sorted instead of scattered. You answer the ones that count first.
- First response time (FRT)
- First-contact resolution (FCR)
It gathers the signals about new inquiries, repeat inquiries, urgent inquiries, and sales opportunities from across your channels, removes duplicates, and sets priorities.
In a small business, inquiries do not come through one door. WhatsApp, a Google Business Profile message, an Instagram DM, a personal cell, and the shop phone all ring at once, and one person answering them drops some. A new customer's about-to-buy question and an existing customer's complaint land in the same inbox, so an urgent complaint gets buried under a quote request or the reverse. A slow reply is itself lost revenue, and with no record of who asked what and when, every reply starts over from scratch.
An inquiry like this, handled like this.
We gather the work as it actually arrives, and record what each step is judged against.
-
Merge intake across channels
Combine inquiries from WhatsApp, Google Business, email, and DMs into one time-ordered queue, and auto-attach the same customer's past conversation to restore context.
Judgment Judge whether they are an existing customer by their identifier (phone, email, channel ID). First-time means new, a match means returning, tagged early. -
Classify intent
Label each inquiry as new (pre-purchase), returning (checking an open item), urgent (loss if no answer today), or complaint (defect, dissatisfaction, refund).
Judgment Use time-pressure signals like today, now, urgent, or trying to pay, and dissatisfaction signals like scratch, defective, refund, or angry as the priority axis. Urgent and complaint always outrank new and returning. -
Route it
Send quote requests to the quote desk, shipping to order and delivery, defects and refunds to the CS lead, and invoicing to accounting, and apply a backup rule when someone is out.
Judgment Route by who holds the authority the case needs (refund approval, price adjustment), since a first responder who can close it means fewer follow-ups. -
First-touch reply plus info request
Draft a confirmation that it is received and when they will get an answer, along with a request for the minimum info needed (order number, purchase date, photos).
Judgment For simple facts you can answer now (hours, location, stock) draft the reply directly, and for anything with a judgment, cost, or personal data, take it in only and pass to a person. -
Create the case card
Build a case card holding the customer, channel, intent, deadline, owner, and next action, and track it as open.
Judgment State the closing condition (customer satisfied, refund done, quote sent). Do not let it drop out of the queue until the condition is met.
If we cannot confirm identity, we do not open it
We settle the exceptions that actually come up before they do. When a rule doesn't fit, we don't force it through. It goes to a person, with the evidence.
Open the higher-urgency complaint as the main case and branch the new purchase intent into a separate case, keeping both alive.
Do not force a label. Leave it as unclassified, needs a person, but set the deadline timer at the most urgent level so it is not left to rot.
Compensation and personal data are seen by a person
Anything touching money, contracts, personal data, or the brand is drafted and no further. It sends only after a person approves.
-
Sending the final reply on an urgent or complaint case
Tone and whether to offer compensation bear directly on brand trust, so a person reads and sends it.
-
A match that merges history using customer personal data
A wrong match exposes someone else's data, so a person confirms it is the same person.
-
A compensation or exception promise (free reship, partial refund)
It creates cost and a precedent, so it is a person's or the CS lead's call.
-
Special routing of a VIP or key-account case
The relationship context is known to a person, not code.
-
Applying an auto-reply to a new channel
Wording that carries brand voice is approved by a person before release.
How you know it worked
We measure how fast, and whether we closed it in one
53% of U.S. online adults are likely to abandon a purchase if they cannot find a quick answer to their question (Forrester, Customer Lifecycle Survey, 2015)
Measure first-response time and chat abandonment before and after rollout. Even an immediate receipt confirmation cuts abandonment sharply.
Industry average around 70%, best in class 80% plus, retail 78% (SQM Group, 2024)
It rises the more you route the first responder to the person with authority.
The goal is to converge to zero by removing cross-channel blind spots with one merged queue.
Taking in an inquiry means collecting personal information such as names, contact details, and addresses, so you need a lawful basis and a notice at collection. There is no single US privacy law. For US customers, California's CCPA and CPRA require a notice at collection and the country is a state-by-state patchwork, while for EU or UK customers the GDPR requires a lawful basis (Art. 6) and notice at collection (Art. 13). When you merge history across channels, do not combine records without confirming they are the same person, since a wrong match can expose one customer's data to another.
There is less that a person has to hold on to.
Once the scattered checks and repeat replies are drafted and sorted, your staff can spend the day on review and exceptions, and you look only at the decisions that matter.
Get an assessmentChecks pile up on a person.
Inquiries come in over WhatsApp Business, Google Business Profile, phone, and email, and a staffer checks each one, copies it into a spreadsheet, and replies.
The work arrives ready to go.
Every inquiry lands in one queue, sorted and drafted, and staff handle just the checking, sending, and exceptions.
What people ask before they hand this over
The things people actually check first about Customer inquiry intake.
We have five channels, do they all connect?
WhatsApp, a Google Business Profile, email, Instagram DMs, and phone notes all merge into one inbox. A person watches a single queue instead of hopping between apps.
How do you keep an urgent complaint from getting buried under a quote request?
We use time-pressure and dissatisfaction signals as the priority axis to pin urgent and complaint at the top, and alert a person before the deadline timer runs out.
Does AI reply to customers directly?
For factual checks like stock and hours it drafts an immediate reply, and for anything with cost, compensation, or personal data it only takes in and organizes, with a person approving the send.
What to sort out next
First response time
Gathering info before a quote
Gathering info before a quote
Gathering info before a quote can be joined up the same way, on the channels you already use, from intake through to the approval queue.
Handling time
Booking and consultation intake
Booking and consultation intake can be joined up the same way, on the channels you already use, from intake through to the approval queue.
Unanswered inquiries
Order and shipping status updates
Order and shipping status updates can be joined up the same way, on the channels you already use, from intake through to the approval queue.
See every workflow
Inquiries, bookings, quotes, order updates. You can compare the work that keeps a person busy, side by side.