When a customer responds, your team should know what to look at next.
After a service visit, a survey can collect satisfaction, recommendation, and comments. MapMyStaff then connects those responses to an operational view so the team can spot what needs attention, return to the individual file, and organize follow-up.
Connect the signal to what needs to be examined
Organize the responses that need your attention.
The management centre and detailed table let the team move from a global signal to the files that need review. Status, priority, age, reason, latest action, and the activity log provide working context without reducing the response to a single average.
Average age of open records
Change visible
Leading reasons
Activity log
Action recorded
• Latest action recorded
! New record #8427 created
| Respondent | Score | Reason | Status | Priority | Age | Action |
|---|---|---|---|---|---|---|
| CustomerEmail address | — | Service issue | New | High | — | |
| CustomerEmail address | — | Billing / Price | In progress | High | — | |
| CustomerEmail address | — | Customer experience | In progress | Medium | — | |
| CustomerEmail address | — | Delays / Delivery | In progress | Low | — | |
| CustomerEmail address | — | Other | Pending | Low | — | |
| CustomerEmail address | — | Service issue | In progress | High | — |
| Customer | Date | Employee | Status | Priority | Satisfaction | NPS | Action |
|---|---|---|---|---|---|---|---|
| CustomerEmail address | Date | Employee | Not followed up | Normal | Score | Promoter | |
| CustomerEmail address | Date | Employee | To address | Normal | Score | Passive | |
| CustomerEmail address | Date | Employee | Not followed up | — | Score | Promoter | |
| CustomerEmail address | Date | Employee | To address | Critical | Score | Detractor | |
| CustomerEmail address | Date | Employee | To address | Normal | Score | Passive |
The next step can differ by response — and it remains governed by your rules.
NPS distinguishes promoters, passives, and detractors. Depending on the features configured, that reading can support a retention or recovery action, or present a Google review invitation after submission when the provider has a relevant link. The survey is a starting point for the post-service customer relationship, not a guarantee of an outcome.
Offer the Google review journey after submission when the provider has configured a relevant link.
No request is sent until the provider triggers sending.
The automated workflow can now verify the appointment and prepare the send.
Collect a structured response without making the experience heavy.
The configurable module supports closed questions, numeric scales, text fields, and long comments. The questionnaire can cover satisfaction, recommendation, and contextual questions while keeping a consistent structure across multiple languages.
The questionnaire structure can be driven by administrator configuration: sections, question types, translations, available choices, progress and validation. The module can also distinguish required, optional and qualitative feedback within the same experience.
Interaction with the employee
Recommendation
Context question
Move from the overview to the files that explain the signal.
The dashboard brings together response volume, coverage, NPS, comments, and access to triage. Filters by period, territory, employee, and package keep the right scope visible before a result is interpreted, with the option to move down to the individual detail when needed.
Retention and lifecycle
Semantic analysis of comments
Spot what keeps recurring without jumping to conclusions.
The 360° matrix can compare packages, teams, and territories with NPS, volume, and average score. Survey coverage, freshness, snapshot scope, and reading warnings remain visible so the team can distinguish a trend worth examining from a signal that is too fragile to interpret confidently.
The analysis also keeps response volume, survey coverage, data freshness and the exact or partial scope of the loaded data visible so situations that require cautious interpretation can be identified.
Customer health
Change in overall score
Frequently asked questions
Detailed answers remain available in the Help Centre when configuration or interpretation needs more context.
How does the survey reach the customer?
The manual describes a post-service request: the provider chooses the recipient, checks the contact details, and triggers the request. The system then generates a unique and secure link for that customer.
View the complete answerHow are responses routed?
NPS distinguishes promoters (9–10), passives (7–8), and detractors (0–6). Retention or recovery actions then depend on the features and rules being used; the segment alone does not guarantee an action or an outcome.
View the complete answerCan a Google review be offered after the survey?
Yes. When the provider has a relevant link, the configurable journey can present a separate Google invitation after submission. Internal feedback and the public review remain distinct steps.
View configurationHow do we avoid drawing conclusions from too few responses?
Volume, coverage, freshness, and reading scope remain visible. Warnings flag cases where the view relies on a subset or a signal that is too fragile to interpret without caution.
View the complete answerLet’s start with a customer response your team no longer wants to leave without follow-up.
See how to move from the signal to the individual file, examine what needs attention, and organize the next step without confusing recorded processing with the real customer outcome.
