Reputifly editorial · Reviewed 27 September 2026 · 2 min read
Plan how an enquiry is captured, assigned and followed up, with checks that keep the process accountable.
Start with the response process
Reputifly Nexus provides a lead dashboard and enquiry notifications. The useful operational question is who acts on each enquiry and how the team knows it was handled. Software supports that process; it cannot guarantee that no lead is ever missed.
Define the statuses before launch
Use clear meanings for new, contacted, qualified and closed leads. Assign a responsible person and a backup for absences. A confirmation email should acknowledge receipt without claiming a booking or quotation has been approved.
Test the complete path
- Submit a clearly labelled test enquiry through every public form.
- Check that the recorded fields match what was submitted.
- Confirm the intended staff notification and customer acknowledgement arrive.
- Update the lead status and verify the team can find the record later.
- Test duplicates, spam handling and export access before relying on reports.
Keep review requests fair
Invite customers to share honest feedback without filtering public-review invitations by satisfaction score. Do not send only happy customers to Google while intercepting unhappy customers privately. A private support route can exist alongside an equally available public-review invitation.
See Google’s contribution policy when designing review requests.
Review the operation
Look at unassigned enquiries, response gaps and reasons leads do not qualify. Limit access to customer records to the people who need it. Confirm the current integrations and scope with Reputifly before purchase; implementation details and availability can change.
Discuss your enquiry workflow with the team.
