Coordinate service questions during a site move

A site move often reaches a Customer Success Manager after a customer selects an opening date and sends a brief announcement. “We move next month” starts a conversation but does not give a service team enough detail for a useful review. Your role involves organizing verified information, showing unknowns, and bringing together people who own separate parts of the move. This work supports coordination. No one should treat an early discussion as a promise about timing or readiness.

Start with the business event. Ask which group enters the destination first and what work must occur on opening day. A call center, warehouse, clinic office, and training room have different operating needs. Ask whether all staff arrive at once or whether a small group opens first. A date without an operating sequence gives weak guidance. A staged move might involve overlap between locations. A weekend cutover raises another set of planning questions.

Verify location identity before discussing service work. Ask for the full street address, suite or floor, building name, and source for every detail. A lease document, facilities contact, or building manager might give different information. Do not combine conflicting entries into one confident record. Preserve both versions and assign someone to confirm them. A request with the right street and wrong building entrance wastes time for everyone involved.

Access needs a separate discussion. Ask who controls access, who approves a visit, which entrance visitors should use, and whether rules change by day or hour. Ask whether security needs advance notice and who meets a visitor. Do not rely on a prior location. Each building has its own procedure. An access question needs a named person who accepts responsibility for a current answer, not a vague reference to facilities.

In a fictional account review, Tessa sponsors a call center move. She says, “Our team moves in six weeks, and we need service ready.” Malik replies, “Let us separate confirmed facts from items facilities still owns. What is the full destination address, who controls building access, and when does the first group begin handling calls?” Tessa provides a street address and says facilities selected the building. She does not know whether a suite number has been assigned or who meets visitors at reception.

Malik records the address as partly confirmed rather than filling missing fields from memory. He asks which facilities colleague owns the lease and site access. Tessa names Jonah, a facilities manager. Malik then asks who knows the staffing sequence. Tessa names Ren, the call center manager. Malik proposes a short review with Tessa, Jonah, Ren, and the customer technology contact. Every invitee has a reason to attend and a decision area to clarify.

Before the meeting, Malik shares a move sheet. The sheet has rows for destination address, floor, suite, opening date, first business function, building access contact, site visit approval, power status, equipment location, old site plan, and customer owners. Every row carries a source, an owner, a confidence label, and a next action. A source might read “Tessa, account sponsor, 6 September” rather than “customer confirmed.” Names and dates make later corrections easier to trace.

The move sheet should separate a goal from a fact and a request. “Open call center on 18 October” describes a goal. “Facilities has provided a verified suite and access contact” becomes a fact only after owner confirmation. “Customer requests a service review” describes a request. Clear labels prevent a desired outcome from looking like evidence all dependencies have closed. They also show the customer where attention belongs during a busy move.

At the working session, Malik asks Ren to describe the first operating day. Ren says a supervisor group arrives Friday morning. Agents arrive Monday. Malik asks what the supervisor group needs during Friday. Ren names phones, customer record access, and a way to reach the help desk. Malik places those activities beside the relevant dates. He then asks who owns readiness information for each activity. The conversation gains useful context without assuming a technical design.

Jonah explains construction continues on part of the floor. He knows power testing has a scheduled date. He does not know whether final furniture placement affects the equipment room. Malik records an open item: Jonah will confirm the equipment room location after a facilities walk through. He does not write “equipment room available.” A pending field protects everyone from a false handoff when an owner and next step appear beside the gap.

Ask early about the old site. Customers sometimes focus on the new address and overlook existing service. Ask whether the old location stays active during overlap, whether another department uses part of the space, and who has authority to request a change. Do not infer an end date from a lease discussion. Tessa says the call center leaves the old site on Monday, while training staff stay through month end. Malik records two business groups and asks Tessa to name the person who owns the old site decision.

Equipment questions need plain language. Ask what equipment already sits at the destination, who knows its location, and whether staff have access to the related room. If a customer mentions a floor plan, ask whether the drawing is current and who controls updates. A draft drawing should retain a draft label. Do not make technical claims from a sketch. Malik asks Jonah to share the current room designation after his walk through instead of interpreting a construction plan himself.

Customer ownership matters when an item crosses teams. Facilities owns physical access. The technology group owns network information. The business sponsor decides opening priorities. Security owns visitor procedure. Give one person each next response, even when several people need awareness. “Facilities team” is not an owner. “Jonah will confirm access instructions by Thursday” gives the group an item to follow without distributing responsibility across an unnamed group.

After the review, Malik sends the move sheet to attendees. He asks for corrections to facts rather than approval of a polished narrative. His message reads, “Please reply beside any row where the source, owner, or status is wrong. Jonah, please update suite and access. Ren, please confirm first day activities. Tessa, please name the old site decision owner.” A narrow request lowers the effort needed for a response and points each person to a useful action.

When Tessa asks, “Is everything set for our move?” Malik avoids an unsupported answer. He says, “We have the opening sequence and named owners. Suite access and the equipment room are open with facilities. Once Jonah confirms those details, our next service discussion will have a clearer record.” The answer recognizes progress without speaking for work outside the group knowledge. Malik then sends Jonah the move sheet with the equipment room row highlighted and asks for his update after Friday’s facilities walk through.