Ask residents while it still matters.
When a request is closed, a case is completed or someone visits a service centre, residents are asked about it while the experience is still fresh.
Every manager sees their own numbers.
Part of Customer Voice.
Waste collection
Waste Services
Phone
a day
→
Annual feedback arrives too late to act on.
An annual survey asks for feedback months after the event. By then, people remember a feeling, not a phone call.
Consultation handles the big decisions. Triggered surveys track day-to-day delivery.
-
Asked too lateBy the time the survey arrives, the details of the request are gone.
-
Closed isn't always fixedYour system says the request is closed. You can't see whether the resident agrees.
-
Too general to act onAsking how people find your services in general doesn't tell a team what to fix.
From a closed service request to an answer in your reports.
We set it up once. Every night after that, residents are asked about the interaction they just had.
Council CRM. Resolved requests, calls or cases are exported every night.
Secure shared folder. The file lands in an SFTP folder set up for your council alone.
AskYourTeam matches. Each record is matched to the right survey.
Survey invitation. Residents get an email or text. Do-not-contact flags are honoured.
Answers in your reports. Responses are tagged by request type, team and channel, so each manager sees their own numbers.
No contact details needed. Anyone can respond.
Public link. One link for your website, social media and newsletters.
QR code. On counters, posters and cards at libraries and pools.
Works with the systems you already run
Built first for TechnologyOne. Suits any system that can schedule a consistent export, such as MAGIQ, Civica, Datascape or a Genesys contact centre. The export is file-based, so there's no API build.
Three moments worth asking about
A service request is closed
A call or case is completed
Someone visits a counter or venue
Every manager sees their own numbers.
Each response carries details from the original request. So you can see results by request type, team, channel and time taken. A head of service sees their own area. Your executive team sees the whole council.
Waste collection, missed bin
Waste Services, City Services
Phone
2 days
0
Evidence for your service KPIs
Month by month, see whether requests closed in the system were fixed for the resident.Feedback about something they remember
Invitations name the interaction, such as “About your recent waste collection request”.Themes and sentiment
Topics and sentiment drawn from free-text comments.Heatmaps
Results by service and location, so problem areas stand out.Actions with owners
Raise an action, assign it and set a due date.
We set it up and run it for you.
1. Scope it together
2. Your secure folder
3. Schedule the export
4. Configure surveys and reports
5. Test and go live
What councils ask us
Straight answers on effort, consent and security.
Does our IT team need to build an integration?
No. There's no API build. Your CRM team schedules a daily export of finished interactions into a secure SFTP folder set up for your council alone.
It's standard reporting work. We supply the file spec.
Who sets it up and runs it?
We do. We set up your folder, the survey and the reports with you. Then we run it for you. Your team sees the surveys and the results.
How do you respect residents' contact preferences?
Anyone your file marks as do-not-contact is never invited. You also choose which interactions to survey.
Where is the data hosted?
In Sydney, Australia. Data is encrypted in transit and at rest. ISO 27001 certification is in progress, targeted for the end of 2026.
Can we survey people after a phone call?
Yes, where the call is logged as a request in your CRM. We trigger the survey from that record.
General enquiries that aren't logged as requests can get a text invitation, after a consent check.