Someone is moving in eleven days. They need to close an account, open another, work out whether their service transfers, find out what happens to the equipment, take readings on the day and make sure the final bill goes somewhere they will actually receive it.
They are doing all of this while packing, and almost every answer they need is a fixed fact nobody has published in one place.
What customers ask
They usually ask how much notice is needed, whether the service transfers or restarts, what happens on the day, what readings to take, where to send them, what happens to the final bill, whether equipment must be returned or left, whether any charge applies, what happens if the new property has a different provider and whether they can keep the same number or package.
Build one moving home page
A single page, ordered by what happens when, covering notice, what to do on the day, readings, final bills, equipment and the new property. Scattering this across six help articles is why people call.
Example conversations
These scripts use information a provider might publish. Your answers should come from your own pages.
Customer: I am moving in two weeks. What do I need to do? Assistant: The moving home page sets out the steps, including the notice needed, what to do on the day and the readings to take at both properties. It also explains what happens to your final bill and whether your service can move with you. Could you tell me your move date and whether you are staying in the same area?
Customer: What do I do with the equipment? Assistant: The page explains which equipment stays with the property and which must be returned or taken with you, along with how returns are arranged and the timescale for sending anything back.
Customer: Can you update my address now? Assistant: Changing an account address needs secure identification, so it cannot be done here. The page shows the secure route and the contact details, including opening hours. I can note your move date so the team knows what you need.
Readings are where disputes start
A final bill based on an estimate is the most common complaint after a move. Explaining exactly what to photograph, where to send it and by when prevents most of them.
Say plainly what does not transfer
Some services move with a customer and some restart at the new property, sometimes with a new contract term. Being clear before the move prevents someone discovering a new twenty-four month commitment they did not agree to.
Explain the overlap
Customers worry about paying twice or having no service for a week. Explaining how the dates work at both properties, and whether an overlap is possible, is genuinely reassuring.
Check the new address early
Availability at the new property can differ entirely, and finding out on moving day is too late. Prompting customers to check weeks ahead is better service and protects you from an unwinnable complaint.
Landlords and tenants both contact you
Who is responsible between tenancies, what happens with an empty property and how a landlord account works. Publishing this prevents an unbilled void and an angry new tenant.
Move enquiries arrive in the evening
People deal with this after work and at weekends, which is why capture at any hour matters more here than in most support contact.
New connections behave differently
They are covered in switching and new connection questions for providers.
Keep support separate from moves
Faults and billing queries must not queue behind move requests, which is the problem in service outage and billing questions that swamp support.
The documentary friction is universal
It is the same pattern as account opening questions new customers ask, and publishing beats answering, as argued in proactive support answering questions before customers ask.
Getting started
Publish one moving home page covering notice, readings, equipment and final bills, then capture move dates at any hour while keeping account changes secure. SpideyChat for B2B providers answers from your published pages. Try SpideyChat on your own site, or read about answers on the features page.