Get every program enquiry to the right person.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
Give your team a clear way to review new enquiries, avoid duplicate follow-up, and route requests by program interest.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
“Review each new enquiry and make sure it reaches the right team for follow-up.”
Clear tasks, with review where it matters.
- Review a new enquiry
- Check that the request is complete
- Check for an earlier enquiry
What this workflow could do
Keeps incoming program enquiries organized so your team can respond without sorting through duplicates or guessing who should follow up.
Keep contact details to a minimum, check for an existing enquiry by email, and route requests with missing details to a person.
How the idea could work
Select an illustrative task to explore its proposed role. No workflow runs here.
-
Capture the prospective customer’s name, email, and program interest so the team has the context it needs to follow up.
-
When key details are missing, send the enquiry to a person to review and decide how to proceed.
-
Look for an existing request from the same email address before adding another follow-up record.
-
Save the details needed to understand and respond to the enquiry, without collecting extra contact information.
-
Direct enquiries by program interest to the team responsible for follow-up.
-
Let the appropriate person know when an enquiry cannot be recorded or routed as expected.
Review a new enquiry
Capture the prospective customer’s name, email, and program interest so the team has the context it needs to follow up.
Proposed setup considerations
These are planning notes for the concept, not instructions for a currently available template.
- 01
Choose the program teams
Decide which person or team should follow up on each program, including who handles priority enquiries.
- 02
Set the minimum details
Choose the details your team needs to respond, and decide what should count as an incomplete enquiry.
- 03
Assign incomplete enquiries
Name the person or team who will review requests that are missing key information.
- 04
Agree on the follow-up process
Decide how your team will handle repeat enquiries and requests that need attention.
Published templates and verified customer availability remain pending.
A little less busywork.
A little more room for you.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation