A Sample Message Sheet for Rehearsing a Reception Greeting Before a Keyphone Quote

Why rehearse the greeting before the quote conversation

A keyphone quote conversation starts before anyone discusses equipment. It starts when a caller reaches the front desk and hears the first sentence. If that sentence is vague, the caller fills the gap with assumptions, and those assumptions travel into the quote discussion as if they were facts.

This sheet is a rehearsal tool, not a script to read aloud word for word. It gives a reception team two fictional situations to practise, a short opening they can adapt, and an observer checklist that focuses on two things only: how the call opens and where mistaken assumptions creep in. It deliberately leaves out fault handling, callback ownership, routing, telephone numbers, settings and technical instructions. Those belong to other documents and other conversations.

Use it as an office role-play in a Sarawak setting. One person plays the caller, one plays reception, and one observes with the checklist. Ten to fifteen minutes is a reasonable example length for a first run; treat that as an author heuristic, not a researched standard.

Eyonic Security Systems, trading as Eyonic CCTV, plans, supplies and installs CCTV systems for homes, offices, shops and industrial sites in Sarawak. That identity matters here only as context: the same discipline of checking assumptions before committing applies whether the enquiry is about a phone system or about CCTV security systems.

How to set up the room and the roles

Keep the setup simple. Three chairs, one table, one printed sheet per person. No screens, no sample hardware, no product brochures on the table. The point is wording, not demonstration.

Assign three roles. The caller reads one situation card and stays in character. Reception answers as they normally would, using the opening they prefer. The observer holds the checklist and says nothing until the run ends.

Run each situation twice. In the first run, reception answers naturally. In the second, reception tries one deliberate change, such as naming the premises earlier or asking one clarifying question before describing anything. Compare the two runs out loud.

Agree two ground rules before starting. First, nobody invents details about the caller's site, budget or timeline. Second, if reception does not know something, the correct move in this exercise is to say so plainly and note it, not to guess. Guessing is exactly the behaviour the observer is watching for.

A short debrief after each pair of runs is enough. Ask the observer to read only the checklist items that were triggered, then ask reception which sentence felt least natural. That sentence is usually the one worth rewriting.

Situation one: a caller who assumes the quote is already agreed

Caller card, situation one. The caller opens with something like: "I spoke to someone last week, so the quote should already be done, right? Can you just confirm the price?"

The trap in this situation is the word "confirm". Reception may feel pressure to agree that a quote exists, or to repeat a figure from memory. Neither is needed in this rehearsal. The useful greeting acknowledges the caller, avoids confirming anything unverified, and moves the conversation toward what the caller actually needs to describe.

A workable opening shape, to be adapted rather than recited: greet the caller, give the premises name, thank them for calling back, then say plainly that you want to make sure you are looking at the right enquiry before discussing anything. Then ask one open question about the site.

Observer focus for this situation: did reception avoid agreeing that a quote exists? Did reception avoid quoting a figure? Did reception ask at least one question about the caller's premises before describing anything? Did the greeting include the premises name early enough that the caller knows who they reached?

This is where mistaken assumptions usually appear. A caller who says "last week" may be thinking of a different office, a different site or a different conversation. The greeting does not need to resolve that. It only needs to avoid hardening the assumption.

Situation two: a caller who describes a site in general terms

Caller card, situation two. The caller says something like: "We are setting up a new office and we need to sort out the phones and the security. Can you tell me what we need?"

The trap here is different. The caller is inviting a description of a whole solution before anyone has seen the site. Reception may start listing items, which sounds helpful but builds assumptions on both sides.

A workable opening shape: greet the caller, name the premises, acknowledge that the enquiry covers more than one area, then say that the next step is to understand the site before discussing specifics. Ask one question about the premises, such as whether it is a new fit-out or an existing office being adjusted.

Observer focus for this situation: did reception avoid listing products or packages? Did reception avoid implying a site visit has already been arranged? Did reception avoid promising a timeline? Did the greeting stay short enough that the caller had room to speak?

This situation is also a fair place to mention, in general terms, that a site survey is a normal early step for security work. Eyonic's published service list includes site survey and camera placement alongside CCTV installation and NVR setup, which is a useful reminder that assumptions about a site are usually checked on site rather than over the phone.

The observer checklist

The observer uses the same short checklist for both situations. Score each line as met, partly met or not met. The scores are a discussion aid, not a measurement of anything.

Opening. Did the greeting include a welcome and the premises name within the first two sentences?

Clarity. Was the purpose of the call restated in the receptionist's own words before any description began?

Assumption check. Did reception avoid confirming an unverified quote, price, appointment or timeline?

Question quality. Did reception ask at least one open question about the caller's premises or need?

Restraint. Did reception avoid listing products, packages or technical details?

Handover wording. Did reception say clearly what would happen next without naming a person, a number or a system setting?

Tone. Did the greeting sound like speech rather than a form being read?

After the run, the observer reads only the lines that were partly met or not met. Reception then rewrites the weakest sentence in their own words and tries it once more. Two rewrites in a session is plenty; more than that tends to blur the lesson.

Common mistaken assumptions to listen for

The checklist is easier to apply if the observer knows what to listen for. These are the assumptions that most often slip into a first greeting.

Assumption of continuity: treating a caller as already known because they say they called before. The greeting can acknowledge the call without confirming the history.

Assumption of scope: hearing "office" and picturing a standard layout. A caller's office may be a shop unit, a converted house or an industrial space, and the greeting should not narrow the picture prematurely.

Assumption of budget: hearing a general enquiry and mentally placing it in a familiar range. Published package prices exist for some items, but a greeting is not the place to raise them.

Assumption of timing: implying that a visit, a quote or an installation will happen soon. The greeting can describe the next step without dating it.

Assumption of authority: treating the caller as the decision-maker, or assuming they are not. Neither helps the conversation.

For context on why this matters beyond phones, Eyonic's published smart lock guidance notes that smart locks work best when door condition, user roles and backup method are reviewed before installation, and that for business use the company usually checks whether a standalone smart lock or an access-control panel is more appropriate. That is the same principle in a different setting: check before committing.

Turning the rehearsal into a one-page message sheet

After the role-play, condense what worked into a single page that reception can keep nearby. Keep it to four blocks.

Block one, the opening. Two or three sentences: welcome, premises name, thanks for calling.

Block two, the bridge. One sentence that restates the caller's purpose and signals that you want to check you have it right.

Block three, the question. One open question about the premises or the need, with two or three alternatives so it does not sound mechanical.

Block four, the next step. One sentence describing what happens next, with no names, numbers or settings.

Leave a margin for handwritten notes. The sheet should look unfinished, because it will keep changing as the team hears how callers actually respond.

Review the sheet after a few real calls and strike out any line nobody uses. A short sheet that gets read beats a thorough one that gets filed.

Where this fits alongside the rest of a premises project

A reception greeting is a small piece of a larger picture. The same premises manager may be handling a phone enquiry, a CCTV security systems review and a door access question in the same week, and the discipline of checking assumptions carries across all of them.

Eyonic's published project notes describe practical support for a public office in Kuching focused on arrival flow, staff areas, visitor movement and dependable daily operation, and support for an engineering consultancy in Kuching covering staff movement, visitor handling, tidy cabling and clearer daily site control. Those descriptions are about site work, not about reception scripts, but they show the kind of detail that a first conversation cannot settle on its own.

If the rehearsal raises questions about the wider setup, the keyphone system page is the natural next stop for the phone side of the enquiry. For security work, the published service list covers CCTV installation, camera placement, NVR setup and remote CCTV viewing, and the smart lock door access review covers door condition, user roles and backup entry. Eric Yong is named in Eyonic's published material; any expert view belongs to him rather than to the company as a whole.

When the team is ready to talk through a specific requirement, the published contact route is to WhatsApp about the product in question. Keep the rehearsal sheet separate from that conversation: the sheet is for practising the opening, and the conversation is where the details get checked.