Planning shutter control groups: what should respond together?

When a customer wants to operate several shutters together, your business has a specific advisory task. Which systems should respond to the same command, which should remain individually accessible, and what does the customer expect from a future extension? This decision goes beyond choosing a handheld transmitter. A clearly described control concept helps you offer the desired scope and explain operation that fits the customer’s rooms and habits.

Start with everyday situations. A shared living-room command may be welcome while the bedroom follows a different routine. The customer does not need to understand radio technology. They should describe which shutters they want to move together and when. Your specialist then translates those wishes into a technically checked combination. This consultation process structures the service decision; it replaces neither compatibility assessment nor setup instructions.

Explain a shared command through an everyday situation

Ask for one situation in which shared control would help. “When you sit in the living room in the evening, which shutters would you like to close together?” is more specific than asking about channel numbers. Have the customer name the windows included and those excluded. This creates an initial understandable scope. It confirms neither technical implementation nor every future control group.

Then consider other recurring situations. The customer might want to open the kitchen in the morning while bedrooms follow later. A study might be used differently during the day. Collect only wishes actually mentioned. You need not propose a complete automation package when shared manual control already describes the goal. Your quotation stays focused on the decision the customer wants to make today.

Distinguish a shared command from an automatic action. “All down” might mean a button someone deliberately presses or a timed sequence. Ask before turning the phrase into a function. Short expressions can hide several expectations. Explaining the difference helps the customer define the wish and prevents your team from inferring unrequested automation from a general comfort promise.

Name rooms and systems consistently

Create a small mapping of the systems with the customer. Living room left and right, kitchen and bedroom are clearer than changing numbers. If existing documents use different names, link both sets once transparently. This mapping serves your consultation; it is not an additional customer-enquiry feature. Its value is that quotation, setup and explanation later refer to the same systems.

Record known existing controls for each system. The customer might report a wall switch, remote control or manual operation. Mark this as preliminary information. A visible transmitter proves neither the exact system nor compatibility with another device. Your specialist determines the identification and documents required. Sales should expose that need rather than infer a common technical basis from similar casings.

If different construction phases or previous suppliers were involved, keep those differences visible. Ask when systems were added and whether documents exist. Record missing documents as a specific task. Customers need not experiment with old programming or open devices. Your business can first establish the information required for its proposed assessment and the result the specialist should derive.

Discuss group control alongside individual operation

Restate the group in plain language: “These two living-room systems should respond together.” Then ask whether each should also remain individually operable. A wish for one shared button does not answer that. A customer might change one window side during the day and close both in the evening. Both situations together adequately describe the desired operation for specialist assessment.

Ask the customer to decide whether, on a typical morning, they want to adjust one system differently after a shared command. Record this exception against the relevant group so your specialist can assess both operating routes together.

Discuss overlaps explicitly. A shutter might belong to the living-room group and a later whole-house group. Record both wishes without confirming implementation. Establish whether the customer really needs two levels or simply means all living-room windows once. This prevents additional equipment whose benefit was never clearly established in the conversation.

Agree understandable group names. The name should identify the systems actually assigned. “Ground floor” works only when the customer knows which systems are included. If the kitchen is excluded, discuss another name or explain the exception. This concerns understandable use, not a particular device interface. Your business checks which naming options the offered system supports.

Select controller, app and feedback separately

Show the options your business actually offers against the situations described. A transmitter can answer a different need from app control. Ask who wants to use it and when, not just which device they prefer. An occasional visitor and a personally used phone represent different situations. Discuss suitability through the actual offer rather than infer it from “smart home”.

On its radio-control page, Somfy distinguishes individual and group operation from app operation with the specified smart-home hub. It also explains different feedback capabilities of its radio technologies. These distinctions justify asking about the specific system. They do not establish that every existing motor can be integrated or every controller can display an actual position. A firm statement requires assessment of the selected combination.

If feedback matters, ask the customer to describe the expected information. Do they want to see that a command was sent, or expect information about the position of particular shutters? Do not merge those expectations. Pass the specific question to your specialist and include only the verified function in your quotation. A display is neither a safety confirmation nor a promise to know every building condition at all times.

Separate today’s scope from future extensions

A possible extension can influence today’s selection without belonging to the order. Ask which shutters the customer actually plans to add later and what remains undecided. A plan for the upper floor warrants a different note from wanting to keep every option open. Show what is being assessed and offered now and which future combination has not been evaluated.

Do not promise unlimited expandability. Product generations, existing components and the eventual wish must fit specifically. For now, pass a named extension wish to your specialist. They can assess its implications for today’s proposed solution. Where information is missing, explain that gap instead of selling an open future wish as an already promised feature.

Setup also forms part of the service scope. Clarify whether your business configures the agreed groups, explains operation and performs other agreed steps. A later room-layout change is not automatically included. You need not invent a general pricing rule. Describe the actual offer so the customer understands the groups and controls planned for handover and how additional wishes will then be discussed.

Advise a fictional home with two routines

This example is entirely fictional. A customer wants to operate two living-room shutters and one kitchen shutter together. Bedroom operation should remain separate. They explain that only the kitchen should open in the morning, while living room and kitchen should close together in the evening. “Ground floor together” therefore describes their need only partly. Your employee records two situations and asks about additional individual operation.

The customer confirms individual operation and asks about an app. Your employee establishes whether the app should be quoted now or is only a future interest. In this example, the customer wants to compare operation with the device actually offered and a separately explained app variant. Your business assesses the existing systems and describes only technically supported combinations. Neither the enquiry nor this example confirms a common radio technology in the building.

Suppose your specialist can offer a suitable configuration after assessment. The basic variant names the three systems, agreed individual controls and shared evening command. The app variant explains additional components and services for those same systems. The bedroom stays outside both scopes. The customer can decide the actual difference rather than compare totals with different hidden assumptions.

Before execution, the customer chooses the basic variant. The group wishes go to the responsible team with identical room names. During the agreed explanation, you walk through the described situations together. If the customer later wants to include the bedroom, that is a new specific question. Your specialist assesses it; the earlier decision for three systems does not silently become a commitment covering the entire house.

Finish with an understandable choice

Summarise without technical abbreviations. Which systems are included, which respond together, what individual operation is planned and what additional wish remains open? Ask the customer to explain one everyday situation using this description. Misunderstandings can become visible before they guide execution. This checks shared understanding of the offer; it does not transfer technical assessment to the customer.

Record the choice alongside the technically checked product version. If a component changes later, you can identify which statement requires reassessment. This maintains the link between wishes, offered devices and agreed setup. With several shutters, that clear mapping provides the value: the customer decides on operation for actual rooms, and your team can proceed with precisely that scope.

If a decision remains open, identify it individually and agree who will answer it. The next quotation conversation can then address the outstanding choice directly.

Bring new operating preferences into a specialist conversation

The webRichtung roller shutter page explains the customer-enquiry service. The stated operating preference is a starting point; specific groups, manufacturer compatibility and app scope are not promised. You clarify those questions in consultation. Register your specialist business and view the current price in webRichtung Customer before commissioning.

Sources

Somfy: radio shutter control describes individual/group operation, app connection and radio-technology differences. The consultation process is editorial advice, not technical approval of a system.