1. Map the work before setup
Start with a recent real example and the people who handled it. Describe where the enquiry or task began, the decisions made along the way and the outcome the customer expected.
Write down the workflow below as a starting point. For each stage, agree an owner, entry condition and the information needed to move forward.
- Enquiry
- Lead
- Site Visit
- Unit Selection
- Booking
- Payment
- Handover
2. Agree records and responsibilities
Choose how projects, towers and units are identified. Define available, held and booked states, who can change them and how expired holds are released.
Keep buyer requirements and channel partner attribution on the buyer record. A site visit should carry the project, host and next follow-up.
Agree booking documents, payment schedules and handover requirements. Assign an owner for exceptions rather than hiding them in general notes.
3. Prepare existing information
Choose the records the team needs at launch. Remove obvious duplicates, check contact details and map old statuses to the new workflow. Keep a recoverable copy of source information and review a small import sample before moving the rest.
Agree who may view, edit, approve or export the relevant records. Test access using an ordinary team member’s account, rather than relying on an administrator’s view.
4. Configure a small working flow
Begin with the fields and actions needed for the chosen process. Add a reminder only when its trigger, recipient and stopping condition are clear.
For integrations, confirm the available interfaces, matching identifiers and error handling. A proposed connection is not a confirmed integration until scope and implementation are agreed.
- Choose one record type and one team.
- Configure stages, owners and required information.
- Set the first reminder or handoff rule.
- Agree who reviews incomplete or failed actions.
5. Test normal work and exceptions
Run one ordinary example from start to finish, then test a missing contact, reassignment, cancellation and overdue action. Check what the customer and each team role can see.
Review reports against the underlying records. Confirm what counts as an enquiry, completed action or successful outcome before using totals to guide decisions.
- Can a colleague find the history without asking for a separate message?
- Does each active record have an owner and next action?
- Can the team recover from an incorrect update?
- Are unresolved exceptions visible to a named person?
6. Launch with a review plan
Give the team a short walkthrough using its own workflow. Name the person handling setup questions and explain how requests for changes will be collected.
Review the first working cycle before adding fields or automation. Bring the agreed workflow to a Melorite demo to confirm product fit, configuration needs and the support included in the proposed setup.
