Where the work gets stuck
Long forms can ask for details the team does not yet need. Heyy can collect information during a conversation if each question serves a clear purpose. Decide which details your team needs to follow up and keep the process short.
What to prepare
- The minimum fields required by the receiving team
- Approved answers and a notice explaining how contact details will be used
- Rules for people who want information without a callback
Follow these steps
- Answer the initial service or programme question where possible.
- Ask one relevant question at a time to understand what the person needs.
- Offer the appropriate next step and request contact details only if needed.
- Save the record and send it to the person responsible instead of leaving it in a queue nobody checks.
An example from everyday work
A local service enquiry might need service type, area, and preferred callback time. A course enquiry might need programme, intake, and contact preference. Neither needs an unrelated personal history just to receive a public answer.
When your team should take over
Do not make access to basic published information depend on unnecessary contact collection. Follow the organisation’s approved consent and messaging rules for later campaigns.
How to check the results
- Complete enquiry records your team can use
- Steps where people stop providing enquiry details
- Follow-ups that needed another round of basic questions
Your next step
Remove any field that nobody uses during the next step. Better enquiry quality is more useful than a bigger pile of incomplete contacts.