# How to track a client inquiry across email and chat A customer asks a question by email, sends a photograph in chat, and later confirms a visit by phone. A single record helps you keep track of what was requested, what you promised, and who needs to act next. Give the inquiry one record that points to the original messages and follows the current decision. You can keep that record in a spreadsheet, a CRM, or another place your team already uses. Canonical: https://areinum.com/guides/track-client-inquiry-across-channels/ Language: en Updated: 2026-10-31 ## Create one record for the inquiry Record the customer's name, a short description of the request, the date it came in, and the person responsible. Add the relevant messages or their locations, but do not copy a whole conversation when a link and a short description will do. Write the current status as an observable fact: "waiting for measurements" or "quote sent on June 4." Then add the next action, who owns it, and when to check. Avoid a broad label such as "active" if it does not tell anyone what happens next. 1. Capture the request and its source. 2. Link the email, chat, or call note to the same inquiry. 3. Record what has actually been sent, agreed, or received. 4. Assign the next action and a date to review it. ## An example: a repair request moves between channels A fictional repair shop receives an email asking about a damaged gate. The customer later sends a photo in chat and asks by phone whether someone can visit on Friday. The shop records all three details under the same inquiry and notes that Friday is a request, not yet a confirmed appointment. The owner checks availability, sends a proposed time, and records the response when it arrives. If there is no reply, the record says "waiting for confirmation" rather than "visit booked." The quote and any later scope change get their own dates and sources. ## Track follow-up without inventing progress Record a prepared reply as a draft until it is sent. After sending, keep the inquiry open until you have the response or confirmation needed for the next step. If the customer changes the work requested, keep the previous scope and the date of the change. This makes it easier to explain why a new quote or appointment is needed and who must approve it. When the inquiry becomes a project, link the accepted proposal or delivery handoff before closing the inquiry. ## Where Areinum fits The pre-production demo includes a general assistant and a CRM area with fictional company data. It demonstrates a way to ask about available business information and review proposed actions in one workspace. Before using a product workflow for your own inquiry, confirm which sources are available and how the current record is updated. The method above works independently of a particular integration. ## Questions you may have ### What should I record after a phone call? Write the date, participants, the request or agreement, and any next step. If an important term remains uncertain, send or request a confirmation rather than treating your note as proof of agreement. ### What is the difference between a quote and an accepted quote? A prepared or sent quote states a proposal. An accepted quote requires evidence that the customer agreed to the relevant version and terms. Record that evidence with the inquiry. ### How often should I check an open inquiry? Set a review date that fits the customer's request and the next commitment. A brief regular review is useful only if each open item has a clear owner and next action. ### Do I need a CRM to do this? No. A shared spreadsheet or another accessible record can work for a small number of inquiries. Choose a CRM when the work requires capabilities that your current record cannot reliably provide. ## Sources and further reading - [How do you guys manage client inquiries and keep track of relationships? I'm drowning a bit](https://www.reddit.com/r/agencynewbies/comments/1u4tyed/how_do_you_guys_manage_client_inquiries_and_keep/): The post's author says inquiries, WhatsApp conversations, and notes were spread across tools and describes forgetting a follow-up. This is a single self-report. This is one person's account, not evidence of how common the problem is or proof that a particular workflow works. The writer's identity, agency role, account of events, and representativeness are not independently verified. One post cannot establish prevalence or prove that a specific tool or workflow works. (2026-10-18) Download the original worksheet: https://areinum.com/guides/track-client-inquiry-across-channels/client-inquiry-register.csv ## Cross-Channel Client Inquiry Register All organizations, people, dates, and inquiry details in the register are fictional. | Inquiry ID | Organization or contact label | First received | Original channel | Latest channel and date | Current summary | Status | Owner | Next action | Due date | Source thread links | Close reason | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | Q-104 | Maple Street Studio, fictional | 2026-10-16 | Email | Chat, 2026-10-17 | Asked for a range before booking a discovery call | Replied | Jamie Park, fictional | Send two questions needed to scope the request | 2026-10-20 | Email thread and chat thread, fictional | Open inquiry; no close reason | | Q-105 | Northfield Studio, fictional | 2026-10-15 | Website form | Email, 2026-10-16 | Example sent; prospect asks which service fits their next project | Response due | Riley Chen, fictional | Answer the prospect's service-fit question or request the missing project context | 2026-10-21 | Form record and email thread, fictional | Open inquiry; no close reason | | Q-106 | Cedar House, fictional | 2026-10-10 | Email | Email, 2026-10-14 | Declined after receiving the proposal | Closed | Jamie Park, fictional | No further action unless the prospect reopens the discussion | 2026-10-18 | Proposal email, fictional | Explicit decline | 1. Create one row per inquiry and keep that row when the conversation moves to a different channel. 2. Use a short, factual summary and link to the original threads. Do not copy an entire private conversation into the register. 3. Keep the status and next action aligned. Waiting on prospect means the prospect has the next move, while the owner still has a review date. 4. Review the due-date column on a schedule your team can sustain, then update the owner, action, and source links after each meaningful exchange. 5. Treat the names and messages shown here as fictional. A blank reply does not establish that a prospect declined. ### Limits of this method - The source is one Reddit account's self-reported experience, not a verified case study or a measure of how common channel fragmentation is. - This register depends on a person updating it and checking due dates. A saved row does not itself send a reply or guarantee follow-up. - A short summary can omit important context. Keep the original messages available and use them when exact wording or a decision matters. ## Related reading - [Find what is missing before a client project starts](https://areinum.com/guides/missing-client-project-information/) - [Is a spreadsheet or CRM right for your client list?](https://areinum.com/guides/spreadsheet-or-crm-client-list/) - [Review the next step before it affects someone else](https://areinum.com/product/decisions-and-control/) Explore the demo: https://platform.areinum.com/ The demo uses sample business data and is in English. Access may need to be arranged.