You can’t know without asking, or fix without measuring
What store teams and customers think is usually learned once it shows up in the sales figures. Surveys and Experience keeps a regular pulse with short questions, turns answers into a score store by store, and ties a low score to a task.
A question is asked, the answer becomes a piece of work, and the team hears the result.
A pulse survey is like a dental check-up: decay caught at the check-up is cheap to fix; decay found when the pain starts is not.
Figures show the result, not the reason; the reason is only learned by asking.Head office is the last to know what happens in store
As a chain grows, the voice of the shop floor thins out on its way to head office. Which store team is worn out, how a new shift or incentive rule landed, whether the customer was happy after an alteration: often nobody knows.
Quiet leaving
A good sales associate is worn out months before leaving. Head office finds out when the resignation arrives.
Filtered news
A problem softens as it travels from manager to area to head office. Mostly good news is carried upward.
Once-a-year survey
By the time the annual survey is reported, the person asking, the person answering and the problem itself have all changed.
Late figures
When revenue, returns and staff turnover move, the cause is long past.
Staff and retail customers: two pulses, one system
The question, channel and measure differ for employees and customers; survey design, delivery, scoring and action run in the same place. The two scores never mix, and are read side by side for the same store.
The pulse of the store and its team
Measuring the team’s week with short, regular questions; recording the answer against the store, not the person; tying a low score to work, not to blame.
- Weekly pulse survey
- Anonymity and the five-response threshold
- Store happiness score
- Instant feedback
- From score to task
The pulse of the customer
Instead of sending everyone the same survey: one short question to the right customer, at the moment they meet the store.
- In-store QR survey
- After alterations and service
- Buyers of a model or brand
- Channel order and reminders
- Consent-based delivery and approval
The same five steps in both categories
- 1Ask
A short survey in the designer; eleven question types, branching, ready templates. A published version never changes.
- 2Deliver
Audience, wave schedule, reminders. In the app for employees; by link or QR for customers.
- 3Measure
Happiness, eNPS, CSAT, NPS, effort score. By store, area and period, with the change from the previous period.
- 4Act
A rule for scores below the threshold: a task or support ticket is opened for the person responsible.
- 5Report back
The team hears what was said and what was done. This is where participation in the next survey is earned.
The pulse of the store and its team
A long survey happens once a year and arrives late. A pulse survey is short, comes at the same time on the same day, and takes a minute on the employee’s phone.
Three questions, one minute, every week
- Wave schedule: for example every Friday at 16:00; 72 hours to answer, a reminder after 24 hours. No reminder goes to those who have answered.
- In the employee’s pocket: the Today card and Feedback screen in Yetkin Mobile Plus; My Surveys in the Portal.
- Audience: stores only, a role, a location or individuals; the list is frozen with that day’s staff for each wave.
- Ready templates: employee happiness, end of shift, after training; you change the wording to your own.
Honest answers come through a safe channel
An employee who is not sure the answer won’t come back to them writes “everything is fine”. The identity mode is chosen when the survey is set up and stated at the top of the form.
Identified
Who answered is known. For training evaluations, the manager’s weekly form, feedback after a task.
Anonymous
The answer is not linked to a person and its time is rounded to the day. The weekly pulse and store happiness score work in this mode.
Pseudonymous
One person’s answers are followed over time without showing the name. Revealing identity takes a separate permission, a written reason and a record.
- Five-response threshold: results and breakdowns are not shown for a store with fewer than five responses.
- No working it out: a single hidden store is hidden together with the smallest visible one, so nobody can be found by subtracting from the total.
- The manager does not see who said what; only the total score and free-text comments in shuffled order.
The store is measured, not the person
In every wave, pulse answers become a score from 0 to 100 for each store. The score is read together with the question that pulled it down.
- Question by question: is it the shift plan, the workload or manager support that lowers the score?
- Below-threshold alert: the manager who started the campaign is notified when a store falls below the threshold.
- Comparison: store, area and segment; change from the previous period; CSV and Excel.
- Participation is a measure too: a store with falling participation deserves as much attention as one with a falling score.
Illustrative screen; sample data.
No waiting for Friday: say it when you see it
A faulty scanner, a missing size, a rule that doesn’t work. The employee doesn’t wait for the weekly survey; two taps on the phone and it is written.
Always open
No invitation needed; sent from the Feedback screen in Mobile Plus or My Surveys in the Portal.
The right people hear
A notification goes to selected roles in the employee’s store; for example the store manager and area lead.
Can be anonymous
If the form is set up as anonymous the sender appears as “Anonymous”; the name is shown on no screen.
Who can start it
The survey defines which roles can send instant feedback.
Which question, when?
Many surveys mean few answers. Each survey has a frequency, an identity mode and a measure; the calendar is set up at the start.
| Survey | Frequency | Identity | Measure | Who looks |
|---|---|---|---|---|
| Weekly pulse3 questions: week, shifts, workload | Every week · open 72 hours | Anonymous | Store happiness score | Area manager, HR |
| Manager formThe store manager assesses their own store | Weekly or monthly | Identified | Result by question | Area manager |
| Recommendation question“Would you recommend working here?” | Once a quarter | Anonymous | eNPS | HR, management |
| After an eventTraining, store opening, end of season, rule change | One wave after the event | Identified or anonymous | CSAT | Owner of the topic |
| When a support ticket closes“Was your issue solved, and how easy was it?” | Automatic · 1 hour after closing, once per person in 30 days | Identified | CSAT, effort score | Support team |
| Instant feedbackWhenever the employee wants | Any time | Identified or anonymous | Topic and count | Store manager |
A low score becomes a task
Seeing the score is half the job. The rule is written once; for a store below the threshold the work opens by itself, with an owner and a due date.
- Action rule: “if the happiness score is below 60, open a task for the store manager” or “open a support ticket”.
- One piece of work: it is not opened a second time for the same store and wave.
- Tracked: open, ongoing and closed work on the Actions screen, each with the score it came from.
- The loop closes: the team hears what was done; the next wave shows whether the score moved.
Illustrative screen; sample data.
What to ask, and what to do with the answer
“Was your plan shared fairly?” Where the score is low, shift distribution and headcount are reviewed with the area manager.
“Did you learn what you need to do your job?” A missing topic goes to training; someone left alone gets a mentor.
“Can you use this training in store tomorrow?” A low-rated section is rewritten.
“Do you know how your target is calculated?” A rule that is not understood is explained again.
“What makes your job harder?” A faulty device, missing supplies, the break area; each becomes a support ticket.
“Do you get feedback from your manager?” The result is used for coaching, not for ranking.
These are suggested uses; you decide the questions and the rules.
The pulse of the customer
The question to ask a customer depends on the moment they meet the store. Each moment has its own question, channel and measure; set up together, the scores of the store, the service and the product do not mix.
On the way out of the store
“How was your experience today?”
Alterations, returns, support
“Was it done as promised, and was it easy?”
Weeks after buying
“Did the product meet your expectations; would you recommend it?”
In-store QR: no login, no name, ten seconds
The customer points the phone camera, gives a rating and, if they wish, writes a sentence. No app to install, no sign-up.
- Tied to the store: each store has its own code; the answer is recorded against that store.
- Where it goes: by the till, in the fitting room, at the bottom of the receipt, on a card in the bag.
- Repeat rule: for example one answer a day from the same device; bot protection and an hourly limit.
- Measured separately: customer answers do not mix into the employee happiness score; they form their own.
The alteration is handed over; the job isn’t finished
An alteration is the moment a customer trusts the store a second time. Was it ready on the promised day, did it fit, was the process easy: three questions after collection.
- TodayQR on the collection slip: an open form for alteration collection, tied to the store; the customer answers at collection or at home.
- TodaySending from the collection list: the week’s collected alterations are uploaded to an audience with Excel; a personal link goes by SMS or WhatsApp.
- TodayLow rating: a task opens for the store manager; the customer is called and the alteration redone if needed.
- RoadmapAutomatic sending: the survey going out by itself when an alteration is marked as collected. The same mechanism works today when a support ticket closes.
- 1Alteration recordPromised day
- 2Ready noticeMessage to customer
- 3CollectionIn store
- 4SurveyQR or link
- 5ActionTask on low rating
Ask the buyer of a specific model, after they have used it
A product’s real rating appears not at the till but after two weeks of use. The question goes not to everyone, only to those who bought that model or brand.
- TodayAudience from a file: the list of “buyers of this model in the last 30 days” from your ERP is uploaded as Excel or CSV.
- TodayPersonal link: single-use and time-limited; e-mail, SMS and WhatsApp are tried in order and stop at the first that gets through.
- TodayShort and product-specific: fit, comfort, expectation, recommendation; no more than four questions.
- RoadmapAutomatic audience: building the buyer list by itself from purchase records.
Who to ask?New-season modelModel with high returnsFirst buyers of a new brandFirst-time shoppers
Illustrative screen; sample data.
The survey doesn’t end at the answer: three scenarios
Pick a scenario and step through it. A rule attached to a question turns a low rating into a task or a support ticket, and the work continues in the module where it belongs.
From alteration to re-alteration · Apparel · a low rating becomes a store task
-
An action is attached to the “Were you happy with the result?” question of the alteration survey: a rating of 1 or 2 opens a task for the store manager.
-
If you use the Alterations module the audience is already there: collected records are connected to the survey and the process runs automatically. If you don’t, no need to worry; you can upload the list from Excel, or integrate it from your own application or your ERP. Each customer gets a personal, single-use survey link.
How an alteration record moves › -
The customer taps the link; no app, no sign-up. The link is theirs alone and expires.
-
The customer rates the result and says why. What goes unsaid at collection is said here.
-
The task opens as soon as the answer arrives; who answered which question, and how, is in the description. The manager calls the customer.
-
The manager talks to the customer and opens a new alteration record for the same item. This time the process runs in the Alterations module, with the link the customer follows.
Go to the alterations scenarios ›
- Question
- Were you happy with the result?
- Condition
- Rating 2 or below
- Action
- Open a task · store manager
- Title
- Unhappy with alteration: call the customer
- Due
- 2 days
- Audience
- Alteration collections · week 46
- Source
- Alterations module · collected records
- Without the module
- Excel · your own application · ERP
- Channel order
- SMS → WhatsApp
- Survey
- Alteration satisfaction · 3 questions
You have collected your alteration. Were you happy with the work? Three short questions, one minute: [link]
“The hem is still too long; I’ll have to come in again.”
- TaskUnhappy with alteration: call the customer
- SourceSurvey question · rating 2
- Due2 days · store manager
- Item
- Wool trousers, navy
- Note
- Shorten hem by 1 cm more · free redo
- Promised day
- Thursday
- Task
- Closed · new record opened
An answer routed to customer service · Department store · a low rating becomes a ticket
-
In the same survey a second action is attached to “How easy was the process for you?”: a low rating opens a support ticket for customer service.
-
The customer is happy with the result but not with the process. A single “satisfaction” question would not have shown it.
-
The ticket opens by itself; its source is the survey and the requester details are the customer who answered. The team sees the question and the answer in the ticket.
-
Customer service calls the customer and finds the cause: the ready notice went out before the item reached the store. The ticket is closed with the fix.
-
Which answer led to which piece of work, with whom, in what state: tasks and tickets are tracked together on the Actions screen.
-
Alteration satisfaction is tracked store by store. Whether the change worked shows in the next period’s score.
- Question
- How easy was the process for you?
- Condition
- Rating 2 or below
- Action
- Open a support ticket
- To
- Customer service
“The jacket turned out well, but I came in twice for nothing on the day it was supposed to be ready.”
- Ticket
- Complaint about the alteration process
- Source
- Survey · Alteration satisfaction
- Customer
- S*** K*** · personal link
- Answer
- Ease 2 / 5
The customer was called and we apologised. The ready notice will now be sent after the item is received in store.
Close ticket| Task | Hem redo · Kadıköy | closed | |
| Ticket | Process complaint · customer service | closed | |
| Task | Sleeve length · Ankara | 1 day |
- Ease3.6 → 4.2 · out of 5
- Ready on time82% → 93%
- Work opened11 → 4
Only to buyers of that product · Footwear · product experience is asked of its buyers
-
The list of “buyers of this model in the last 30 days” from the ERP is uploaded as the audience. The survey goes to nobody else.
-
With more than two hundred recipients and an external channel, the campaign does not start until an authorised person approves.
-
The question arrives not at the till but after the product has been used.
-
Fit, comfort, expectation, recommendation. The answer comes from someone who has actually used the product.
-
Answers are gathered by product: recommendation score, satisfaction and fit distribution.
-
A task opens for the product manager: “half a size up recommended” is added to the product information and announced to store teams.
- Audience
- Buyers of the tan leather loafer
- Source
- File (CSV) · 312 people
- Survey
- Product experience · 4 questions
- Identity
- Identified · personal link
312 recipients · e-mail, SMS, WhatsApp in order; stops at the first that gets through.
Approve and startHow is the loafer you bought two weeks ago? Four short questions on fit, comfort and whether you’d recommend it: [link]
“Very comfortable but a tight fit; I should have gone half a size up.”
- Recommendation (NPS)+38 · 118 responses
- Fit41% “tight”
- Product satisfaction81%
- Task
- Add the fit note to product information
- Owner
- Product manager
- Announcement
- To store teams
- Status
- Closed
Illustrative screens with sample data.
The right channel, the right frequency, with consent
A customer survey is not a marketing message, but it spends the customer’s patience from the same account. The rules are set when the campaign is created.
Channel order
E-mail, SMS and WhatsApp are tried in order and stop at the first that gets through. The customer does not get the same survey three ways.
Reminders and frequency
A measured reminder for those who haven’t answered; none for those who have. For event-based surveys, once per person in a set number of days.
Campaign approval
A campaign going to more than two hundred recipients or to an external channel does not start until an authorised person approves.
Delivery Centre
Who it went to, whether it arrived, why it didn’t; tracked wave by wave. Numbers that could not be reached appear in the list.
Consent: surveys are sent to customers who have given messaging consent; the consent record comes from your own customer data. Audiences built from your contacts take e-mail and SMS consent into account.
Which score answers which question?
| Score | What it asks | How it is calculated | Category | Example |
|---|---|---|---|---|
| Happiness | How was the team’s week? | Points given as a share of the maximum possible · 0–100 | Staff | Weekly pulse |
| eNPS | Would you recommend working here? | Share giving 9–10 minus share giving 0–6 | Staff | Quarterly recommendation question |
| CSAT | Were you satisfied? | Share choosing the top two options | Both | Store QR, alterations, training |
| NPS | Would you recommend us? | Share giving 9–10 minus share giving 0–6 | Retail customers | Buyers of a model or brand |
| Effort score (CES) | How easy was it to get it done? | Average · higher = easier | Both | Alterations, returns, support tickets |
| Custom | Whatever you define | Average weighted by the weights you give the questions | Both | Store standards |
Reading together: employee happiness and customer satisfaction sit side by side for the same store; one screen shows how the customer rating moves in a store where the team’s score is falling. The system does not calculate cause and effect between the two.
Name the topic; let the assistant draft the survey
Setting up a survey means writing questions, choosing an audience and scheduling. The assistant produces a draft from one sentence; publishing takes your single approval.
- A draft from one sentence: a survey of about seven questions, a suggestion from existing audiences, schedule and measure.
- Shows first, then saves: nothing is saved until the draft is approved; the approval card shows the number of recipients, the channel and the first send dates.
- Same rules: a campaign with many recipients or an external channel does not start without approval from the assistant either.
With 412 recipients, campaign approval is required.
No trust, no answers
Anonymity is protected
The five-response threshold and protection against subtraction. An anonymous answer is not linked to a person and its time is rounded to the day.
The question asked doesn’t change
A published survey version is frozen. If a question must change, a new version is opened; old answers stay with the old question.
Approval
Content approval can be switched on. A campaign with many recipients or an external channel does not start without approval.
Personal data
In an identified survey a single response is permanently deleted on request. Export needs a separate permission; both are written to the audit log.
Who sees what
Viewing results, exporting, starting and approving campaigns are separate permissions; each role does only what it has been given.
Honest use
Our advice: pulse results are not used to punish anyone or to rank managers. Use them that way once and the next survey goes quiet.
It starts with one question and grows by habit
Rather than opening every survey on the same day, start by asking one question regularly. In the first month the aim is not a high score but a reliable baseline and high participation.
- Pilot · weekly pulseTwo or three stores, three questions, anonymous. The same day and time for four weeks; a baseline forms.
- Threshold and actionA threshold for the store happiness score, a task rule for low scores; the first “you said, we did” announcement.
- The customer sideQR in stores, three questions at alteration collection. Store and alteration satisfaction are tracked separately.
- Product and recommendationAn ownership survey for buyers of selected models; a quarterly recommendation question for employees; new surveys with the assistant.
Frequently asked questions
Can a manager see an employee’s answer?
Not in an anonymous survey. The answer is not linked to a person; the manager sees only the store total and free-text comments in shuffled order. Results are not shown at all for a store with fewer than five responses.
Does a customer need an app or an account to answer?
No. The QR code in the store is scanned with the phone camera and the form opens in the browser; no name or number is asked. In a personal survey the customer taps the link they receive.
Do staff and customer surveys feed the same score?
No. The two categories are measured separately; customer answers do not mix into the employee happiness score. Results can be read side by side for the same store.
Is a survey sent automatically when an alteration is collected?
Today there are two ways: the QR on the collection slip, or uploading the collection list with Excel and sending an SMS or WhatsApp link. Automatic sending at collection is on our roadmap; the same mechanism works today when a support ticket closes.
Where does the list of buyers of a product come from?
You upload the buyer list from your ERP as Excel or CSV. Building the list automatically from purchase records is on our roadmap.
Is consent needed to send a survey by SMS or WhatsApp?
Surveys are sent to people who have given messaging consent; the consent record comes from your own customer data. A campaign with many recipients or an external channel also starts only with approval.
Is Surveys and Experience a separate module?
Yes; it is a separately licensed module that runs inside Yetkin Portal and Yetkin Mobile Plus. In a demo we can design a pilot around your own store structure.
A scale is zeroed first: the first weighing is the basis for every one after it. The pulse is the same; the first month’s value is the measure for every week that follows.
Let’s keep the pulse of your stores together.
In a demo, let’s design a pilot with two stores and three questions.