|
|
| Line 1: |
Line 1: |
| = Using My Move with Customers =
| | #REDIRECT [[Using the Customer Portal]] |
| | |
| This guide is for staff. It explains when to invite a customer, what to expect them to do, and what staff still need to manage in Standout.
| |
| | |
| For the full feature reference, see [[My Move Customer Portal]].
| |
| | |
| == When to invite ==
| |
| My Move is useful for:
| |
| | |
| * applicants who want to maintain requirements and matching;
| |
| * buyers completing Buyer Ready/onboarding;
| |
| * sellers following viewings/offers/progression;
| |
| * landlords following tenancies/compliance/repairs;
| |
| * tenants reporting repairs and viewing tenancy information.
| |
| | |
| The contact needs a usable email address.
| |
| | |
| == Send the invitation ==
| |
| Open the Contact and click the prominent '''Send My Move link''' button to the left of '''More actions'''.
| |
| | |
| The customer receives a time-limited secure sign-in link.
| |
| | |
| == First login ==
| |
| On first secure-link access, the customer is encouraged to create a password. Returning customers can then sign in using email + password.
| |
| | |
| If they forget the password, the secure email link remains available as a recovery/passwordless route.
| |
| | |
| == What customers can update ==
| |
| Depending on their role/transaction, customers can maintain or submit information such as:
| |
| | |
| * property requirements;
| |
| * Buyer Ready information;
| |
| * solicitor information;
| |
| * onboarding/identity details;
| |
| * secure documents;
| |
| * viewing requests;
| |
| * repair reports;
| |
| * repair quote decisions for landlords.
| |
| | |
| Some of this updates existing Standout records directly; other submissions are presented to staff for review.
| |
| | |
| == Review customer submissions ==
| |
| Use:
| |
| | |
| '''Contact → More actions → My Move submissions'''
| |
| | |
| This view can contain onboarding, buyer position, AML information, secure uploads and viewing requests.
| |
| | |
| Do not assume information is correct simply because the customer entered it. Review important transaction/compliance data.
| |
| | |
| == Property requirements ==
| |
| My Move requirements use the same underlying Standout requirements records as the staff CRM. If a customer changes their search, staff will see the same change.
| |
| | |
| == Viewing requests ==
| |
| A My Move viewing request creates a tentative diary viewing. Staff should confirm the slot/parties before treating it as booked.
| |
| | |
| == Repairs ==
| |
| Current tenants can report repairs. Landlords can respond to recorded quotes where the repair has a quote awaiting a decision.
| |
| | |
| == Customer communication ==
| |
| My Move reduces routine chasing only if the underlying CRM is kept current. Update progression, viewing feedback, offers, tenancy/compliance and repair states promptly so the portal tells the truth.
| |
| | |
| == Security principle ==
| |
| Customers can only access records to which their authenticated contact is genuinely linked. Never try to work around portal permissions by sharing another customer's link.
| |
