Capture Enquiry Context at Intake So Nobody Re-Asks the Customer

Today is 14 October 2026. Dussehra falls on 20 October and Diwali on 8 November (Government of India holiday list for 2026). Between now and then, a customer might fill in your website form on a Sunday evening, take a call from one person on Monday, and then hear from someone else on Wednesday who asks the same questions all over again: which product, what budget, how soon. Each time that happens, the customer learns that your team does not talk to itself.

This piece is about one team habit: write down the context of each enquiry when it first arrives, and keep that note with the lead every time it passes to someone else. If your form enquiries are still scattered across inboxes, start with our guide on where each website form lead should land; this piece picks up from there.

Why context gets lost between first touch and the next reply

Context rarely disappears because someone is careless. It slips away in small steps:

• The first conversation lives in one person's head: whoever took the call remembers what the customer said, but nobody else can see it.
• Notes sit in the wrong place: a paper pad, a personal phone, or a forwarded email that only two people received.
• The lead changes hands: the enquiry moves from whoever answered first to a salesperson, a site visit team or a branch, and only the name and number travel with it.
• Festive rosters change: people go on leave, temporary staff join, and cover is arranged in a hurry.

Customers notice. In The State of Customer Service and CX 2025 by Shep Hyken, based on two online surveys of 2,119 adults in the US conducted in January 2025, "69% of customers are likely or very likely to leave because a company kept transferring them, and they had to repeat the same story again and again." That is US data, not an Indian result, but the pattern will be familiar to anyone who has been passed from one department to another. The same report's advice is direct: "the first person to hear the story needs to document it properly in the customer’s record so they can pick up where the conversation ended with the last employee, rather than having to start over."

What to write down at intake

Agree a short, fixed set of points that the first person writes down for every enquiry, whichever channel it came through. Keep the list short enough that people actually use it on a busy day. A practical starting set:

• What they asked about: the product, project or service, in the customer's own words where possible.
• How soon they need it: a date, an occasion such as "before Diwali", or "just comparing", so the next person knows how urgent it is.
• Where they came from: the form, page or campaign, and how they prefer to be contacted, for example a phone call after office hours or an email.
• What has already been said: any price range, availability or next step already mentioned, so nobody contradicts it later.
• What they agreed to: whether the customer agreed to be contacted, and for what purpose.

If your team already uses a short list of source names, use the same names here; we set one out in Which Ad or Form Brought This Enquiry?.

The last point matters for more than courtesy. India's Digital Personal Data Protection Rules require "standalone, clear and simple consent notices that transparently explain the specific purpose for which personal data is being collected and used" (PIB, 14 November 2025). Write down only what you need to help the customer, and keep the note factual: what they asked and what was agreed, not your opinion of them.

Hand the note over with the lead, not in a private chat

A note only helps if the next person reads it before they speak to the customer. The weak point is usually the handover itself: a quick message to a colleague's phone, a word in the corridor to "call this person back", or a screenshot dropped into a group chat. The context exists, but it has been separated from the lead.

Healthcare teams have worked on this problem for years. The Institute for Healthcare Improvement describes its SBAR tool (Situation, Background, Assessment, Recommendation) as "an easy-to-remember, concrete communication mechanism for framing any conversation", and says the technique "provides a framework for communication between members of the healthcare team". A sales handover carries far lower stakes, but the same shape adapts well:

• Situation: who the customer is and what they want.
• Background: what has happened so far, and where the enquiry came from.
• Assessment: how serious and how soon, in the view of the person handing over.
• Recommendation: the next step, who will take it, and by when.

Then agree one rule: the note lives with the lead, in the place your team works from, not in personal messages. Whoever picks up the lead reads the note first and adds to it after each conversation.

A short handover checklist your team can reuse

Pin this up, or paste it at the top of your team's shared notes. Before a lead changes hands, the person handing over checks that:

1. The note says what the customer asked for, in plain words.
2. The urgency is written down, with a date if the customer gave one.
3. The form, page or campaign the enquiry came from is recorded.
4. Anything already quoted or agreed is written down.
5. The customer's contact consent and preferred way of being contacted are recorded.
6. The new owner's name is on the lead, and they have confirmed they have it.
7. The next step and its date are agreed.

The person receiving the lead checks one thing before the first call: have I read the note? If so, the first question to the customer can pick up from what they already said, rather than starting over.

Follow-up after each conversation is a team practice too. Our piece on pipeline stages and follow-up during the festive rush sets out one way to plan it.

Where Flo fits

In Flo, each website-form enquiry runs a workflow that records the contact and adds a note to its record.

What your team writes down about each enquiry, how a lead is handed over, who reads the context before the next conversation and how follow-up is planned remain decisions your team makes and writes down.

Start this week before the festive peak

Before Dussehra, agree the five points your team writes down at intake, put the handover checklist where everyone can see it, and make one rule clear: context travels with the lead. Try it on the next ten form enquiries, then adjust the list if people are skipping a point or writing too much. Share it with any temporary staff joining for the festive season on their first day. If you'd like a walkthrough of Flo, book a short demo.

Sources: Government of India (DoPT) holiday list for 2026, via ICAR; Shep Hyken, The State of Customer Service and CX 2025; Institute for Healthcare Improvement, SBAR Tool; PIB, Digital Personal Data Protection Rules (14 November 2025).