Skip to content
LET'S TALK
EN
Marketing

Why the Client Writes Today

Do not confuse a long-standing need, a discovery channel, and the event that made waiting uncomfortable.

By GrandMa Agency
Editorial & Growth
2026-09-05
Updated 2026-09-05
4 min read
EST. READING TIME  4 minutes·LAST UPDATED  2026-09-05·REVIEWED BY  GrandMa Editorial & Evidence

The owner of a small service business looks at several new chats and is almost ready to credit the latest ad or referral. It is an understandable move: the channel is visible first. But it does not answer the word “today.”

1. An enquiry contains three different things

Need answers “what is needed?” Discovery channel answers “where did they find us?” Trigger answers “what changed so this needs attention now?” Record them separately: they are different questions, not three synonyms for a “lead source” field.

The channel helps someone find a provider. The trigger explains why postponing became more costly or inconvenient.
A working distinction for the client conversation

One enquiry, separated without attribution magic

Before: A ceramics studio asks for new product photos after a friend’s recommendation.

Decision: Record the need, the channel, and what changed immediately before the enquiry separately.

After: Need: better photos. Channel: recommendation. Trigger: confirmed participation in a market, for which the old images no longer fit.

2. When the answer is only “urgent”

“Urgent” describes the temperature of a conversation, not its cause. If the trigger is unclear, do not assign it to an ad, search or referral. Return to the specific change before the enquiry.

The client’s words first, your version second

Write down the client’s wording separately from your own interpretation. This is not bureaucracy for the sake of three fields; it keeps an inference from dressing up as a fact. If you hear a repetition, retain the differences between the conversations too.

ARTICLE TOOL

Find the real ‘why today’

Two questions give you the next move for the conversation or record.

Without JavaScript: record the need, channel and event separately. If the event is unknown, ask: ‘What changed before you decided to deal with this now?’

One vivid case can suggest a working hypothesis. It is too early to call it a pattern for all clients: that requires several separate conversations and attention to what does not match between them. The next move is simple: in the next chat, save the need, channel, the client’s words, and the specific change before the enquiry.

FIND AN ADVANTAGEYOU CAN PROVE.

We turn generic promises into a specific, verifiable reason to choose you.