Following a script versus having a structure in a conversation

6 days ago
3 min read

Updated: 3 days ago

Introduction

Small businesses tend to reject scripts, correctly, and then operate with nothing at all. Every conversation is improvised, the questions asked depend on who answered the phone and what they remembered, and the quality varies enormously between one enquiry and the next. The rejection of scripting is right; the absence of any structure is not.

The distinction is between prescribing words and prescribing coverage. A script tells you what to say and produces something audibly rehearsed. A structure tells you what must be established before the conversation ends, in any words and any order, and it produces consistency without the artificiality that makes scripts unusable.

1. Following a script versus having a structure is a difference in what is fixed

The distinction.

A script fixes the words. A structure fixes the outcomes: the things you need to know and the things they need to know before either of you can proceed. Only the second survives contact with a real conversation.

2. Write down what must be covered, not how

The practical form.

Six items on a card. What they need, why now, timing, who decides, budget or price indication, and the next step. Any words, any order. Keep it beside the phone rather than in a document nobody opens.

3. Let the conversation go where it goes

The flexibility.

Following an unexpected answer is where the useful information is. A structure allows this because it does not specify a sequence. The most valuable part of most calls is a digression.

4. Check the list at the end, not during

The technique.

Glance at it before closing and ask whatever is missing. Consulting it throughout produces the stilted quality everybody objects to in scripts. Ten seconds at the end covers everything.

5. Scripts fail because people can hear them

The reason for the distinction.

A rehearsed conversation signals that the other person is being processed. This costs more than the consistency it gains, particularly in a small business where personal contact is the advantage. Buyers frequently choose a small supplier precisely to avoid this.

6. Some things genuinely should be consistent

The exception worth allowing.

The response time promised, the terms explained, the safety or regulatory points. These benefit from consistent wording, and that is a checklist rather than a script. Getting these wrong has consequences beyond the conversation.

7. Structure helps most when somebody new is answering

The organisational benefit.

A new person with a structure covers the essentials. Without one they omit different things every time and nobody discovers what was missed. It is also far easier to hand over than a set of instincts.

8. Review the structure against lost deals

The improvement loop.

If a recurring problem is discovered late, the thing that would have surfaced it belongs on the list. The structure should evolve from experience rather than being written once.

9. Keep it short enough to remember

The constraint.

Six items can be held in mind. Twenty becomes a form being completed, at which point it has turned into the thing you were avoiding.

Be careful about structures that become interrogations. The order and the tone matter as much as the coverage, and six questions asked in sequence with no conversation between them produces the same impression as a script.

Conclusion

Fix what must be covered, not the words used to cover it.

Write six items on a card rather than a sequence of sentences, follow the conversation wherever it goes, check the list before closing rather than during, accept that people can hear a script and that this costs more than it gains, allow consistent wording for response times, terms and regulatory points, use the structure particularly when somebody new is answering the phone, revise it when a recurring problem is discovered late, and keep it short enough to be held in mind.