Skip to content
GullySales

Granite processors · Customer satisfaction, NPS and feedback programmes

Find out what is putting your next customer order at risk.

Customer satisfaction, net promoter score (NPS) and feedback programmes collect structured feedback about a purchase, service experience, or ongoing relationship, with a defined response to what customers say. GullySales designs the questions and survey timing, sets up the feedback record, and assigns follow-up responsibilities so poor experiences reach someone who can act.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A supervisor shows granite and marble slabs to an architect

Start with the buying decision

What does the customer need after the first commitment?

Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief.

Your team approves the scope and any commitments to buyers. GullySales does not assume authority over pricing, staffing, or delivery promises unless a specific responsibility is agreed in writing.

The context for Granite processors

Start with the decisions in your own enquiry records.

Read the accepted scope and the subsequent service record. Separate adoption, complaints, repeat requirements, and renewal decisions before selecting a follow-up programme.

How people choose in this industry

Colour comes first. A buyer searches for a granite by its trade name, such as Black Galaxy, Absolute Black, Tan Brown, Kashmir White or Steel Grey, and wants to see how the slab looks polished, not the block. Dealers and fabricators keep a mental list of processors who send honest photos and who deliver the same shade twice. Architects and interior designers ask for sample pieces and pick from a physical sample book.

After colour, the buyer checks thickness tolerance, polish quality, breakage in transit and how the bill and e-way bill are raised. Builders buying for a project compare rates across a few processors, then settle on the one that can supply the full quantity from one lot. Credit period and the truck booking arrangement settle the final choice.

The decision before implementation

Resolve an outstanding delivery issue before asking for advocacy or another purchase. Respect contact preferences.

Existing industry priorities to review

  • Colour-wise slab listings with polished photographs
  • Lot photographs sent with thickness and slab count
  • Dealer and fabricator price list that stays current
  • Quotation follow-up with a record of who asked what
  • Container sample plan for export buyers

These describe the industry's wider priorities. The written scope identifies which this service will address.

Industry application review

Test the service against a problem in your own records.

These review scenarios connect the industry context to a possible output and a checkable next step. They are scope questions, not client results or a promise that every industry problem belongs in this engagement.

Photographs live on one person's phone

The yard supervisor sends the same slab photos to every buyer by WhatsApp and nothing is stored. When the supervisor is away, the office cannot answer a dealer asking for a colour.

Output to assess: Low-score response guide

Review whether “Low-score response guide” addresses this specific issue. Confirm that connection from the example before including the work in the scope.

What to bring

Bring the accepted commitment and the later service or contact record, with permission to use the example for review.

Proposed completion check

Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

Dealers compare us only on price

Buyers see a polished slab as the same product everywhere, so they ask for the lowest rate. Our consistency of lot, polish and thickness never gets said.

Confirm the scope first

Check whether this issue belongs in the customer satisfaction, nps and feedback programmes engagement or requires different work. The industry problem alone does not establish that this service will solve it.

What to bring

Bring the accepted commitment and the later service or contact record, with permission to use the example for review.

Proposed completion check

Record the scope decision and its reason. If the issue is outside this engagement, identify the responsible team or the separate work required.

The problem

What customer satisfaction, nps and feedback programmes is meant to address.

  • “Our score looks good, but customers still leave”

    The survey reaches regular buyers but misses customers who stopped ordering or left before completion. The result describes the people who replied, not your whole customer base.

  • “Nobody reads the comments”

    A dashboard shows an average, while specific complaints remain buried underneath it. The person responsible for the service never receives the customer's explanation.

  • “We asked, but nobody called back”

    A customer describes a poor experience and hears nothing. There is no assigned caller or record of what happened next.

  • “Every branch asks a different question”

    Different wording and survey timing make branch scores difficult to compare. A change in the question gets mistaken for a change in satisfaction.

Who it is for

Check your operating model against the scope.

  • Manufacturers and dealers receiving repeat orders without a clear view of delivery or installation satisfaction
  • B2B service firms whose account managers hear about dissatisfaction only at renewal
  • Banks and branch-based businesses comparing feedback across locations
  • Hospitals, dental clinics, and hotels collecting feedback after a visit or stay
  • Teams with survey responses in a spreadsheet but no agreed follow-up responsibility

Before you decide

When this may not be the right fit.

  • You need detailed interviews about customer needs or buying decisions. Customer research and voice of customer is separate work.
  • Nobody in your team can take responsibility for responding to critical feedback.
  • Your existing programme already reaches the right customers and produces documented action.

Choose the right scope

Start with the work your business needs.

  1. Feedback after delivery or installation

    For manufacturers and dealers, a short post-event survey checks the experience while it is still fresh. Delivery or installation concerns go to the responsible person before an account manager discusses another order.

  2. Relationship feedback for repeat accounts

    For B2B services and distributors, a relationship survey collects feedback beyond the latest transaction. Account-level comments give the account manager a specific issue to discuss rather than an unexplained score.

  3. Branch or visit satisfaction

    For hospitals, banks, and hotels, consistent questions allow useful comparisons across agreed locations or services. Results retain response counts, and sensitive comments follow the approved internal route.

  4. Repair of an existing survey programme

    If surveys already run, the starting scope can focus on missing customer groups or responses left unattended. Existing questions are retained where useful, with changes documented so comparisons remain understandable.

What we do

Agree the outputs before work begins.

These are the customer satisfaction, nps and feedback programmes deliverables available for granite processors. Your written scope identifies the included work and responsibilities.

  1. Survey selection and purpose

    A written recommendation for relationship NPS, post-event satisfaction, or a customer-effort question. You can check what decision each survey supports before approving it.

  2. Approved question set

    Short questions with defined scales and an open comment prompt, prepared in the agreed languages. Your team approves the meaning and wording before customers receive them.

  3. Audience and trigger rules

    A record of who receives each survey, when it is sent, and which customers would otherwise be missed. Repeat-contact rules make it possible to check who is being asked too frequently.

  4. Channel and message plan

    Survey messages for the agreed WhatsApp, SMS, email, or calling process. The plan includes the purpose notice and opt-out handling for your approval, with compliance review assigned to your adviser.

  5. Feedback and follow-up log

    A record linking the response to the relevant customer or visit where identification is agreed. Fields cover the issue, assigned owner, follow-up status, and recorded outcome.

  6. Low-score response guide

    A callback script and routing rules for critical responses. Your team can check who receives an issue and where it goes when the first person cannot resolve it.

  7. Baseline and reporting view

    Scores shown alongside response counts and agreed branch or service splits. The view separates customer comments, follow-up completion, and recurring causes so an average does not hide unfinished work.

How the result is measured

  • Survey invitations and response rate, with reply counts
  • NPS or satisfaction trends against the baseline
  • Response coverage by agreed customer group or branch
  • Critical responses assigned and followed up
  • Unresolved issues and repeat causes
  • Qualified repeat-order opportunities and completed orders recorded separately from survey activity, where records are available

Recorded as a baseline before work starts, so every later report has an honest comparison.

Industry baseline

Keep the industry's wider measures beside the service measures.

Use the existing baseline to understand the context. These figures are not all targets for this engagement, and a change must not be attributed to the service without evidence.

  • Enquiries by granite colour and by source
  • Quotes sent against orders confirmed
  • Enquiries where lot photographs and a rate went out together
  • Orders from fabricators who bought before
  • Export samples sent and trial orders received
  • Overdue balances on dealer and builder accounts

This or a nearby service

Which piece of work fits your situation.

These services sit close to each other. The line between them, in plain words.

Customer research and voice of customer
Choose customer research and voice of customer when you need interviews that explain how people decide and buy. Choose customer satisfaction, NPS and feedback programmes when you want a standing survey after a purchase or visit, with a named person who answers poor scores.
Service recovery programmes
Choose service recovery programmes when you already know a customer was let down and need rules for repairing the relationship. Choose customer satisfaction, NPS and feedback programmes when you need to find out who is unhappy in the first place and route it to someone.
Online review generation and management
Choose online review generation and management when you want public ratings that new buyers can read. Choose customer satisfaction, NPS and feedback programmes when the feedback is private, meant for your own team, and the aim is to fix problems before they reach a review site.

A sample of the output

A survey trigger sheet says when each customer is asked, what is asked, and who answers back.

This sheet lists each survey moment in one row. Read across to see what starts the survey, the question used, who owns the reply, and the condition that stops further requests to that customer.

Illustrative example, not client data. Yours is built from your own records.
Survey momentQuestion askedReply ownerStop condition
After installationHow easy was the installation, and what would you changeService coordinatorCustomer replies or the single reminder is sent
After a branch visitDid you find what you came for, and was the staff helpful?Branch managerCustomer replies or declines to take part
Repeat account check-inHow likely are you to recommend us to a colleague, and why?Account ownerAnswer received, or an open complaint exists
After a complaint closesWas the problem resolved to your satisfaction?Complaints leadCustomer answers or marks the matter closed
Low-score alertIs there anything else we should know about how we served you?Sales headOwner logs a call and the outcome

Before we start

What we need from you.

The work depends on these. Each says why it is needed and what happens when it is missing.

A list of recent buyers with contact details
The survey can only reach people you can contact. Names, a working phone or email, and the purchase or visit each belongs to should sit in one sheet. Without that, the pilot has no audience and stalls.
Permission to contact customers
Customers need to have agreed to be contacted for feedback, or your adviser must confirm that service messages cover it. Where permission is unclear, those customers are left out of the pilot until your team settles the point.
One person who answers low scores
A poor score is only useful if someone reads it and calls back. Name one responsible person and a deputy before launch. If nobody owns replies, collected feedback sits unread and customers notice.
The survey tool you already use
If you already run forms, a messaging tool or a CRM, we build inside it. Give us login access and say who administers it. Without access, the feedback record cannot be connected and stays a separate spreadsheet.
Decisions on what feedback is for
Say what you will change if customers complain about delivery, price or staff behaviour. Questions that lead nowhere waste customers' goodwill, so we need your leadership to confirm which topics can result in action.

Marketing and sales together

Your sales team receives the issue before asking for another order.

The agreed handoff gives the account manager a feedback record containing the customer's concern, the responsible service owner, and follow-up status. An unresolved complaint remains a service issue, not a sales opportunity. If the customer raises a genuine purchase requirement, it is recorded separately for sales qualification, with any completed order tracked in your sales records.

Decisions to make before the work starts

  1. Customer records and permissions

    The programme depends on usable contact details and reliable visit or order records. Your team approves data access and contact permissions; sensitive information requires your own compliance review.

  2. Languages and delivery costs

    The number of survey versions, language requirements, and chosen channels affect the scope. Tool subscriptions and message or calling costs are identified before approval.

  3. Work beyond feedback collection

    Deep customer research, operational fixes, and Google review management are separate services. Public review requests should not be restricted to high scorers or tied to a reward; survey replies are not automatically publishable testimonials.

How it works

How customer satisfaction, nps and feedback programmes runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Records and ownership review

    You share existing forms, response records, and examples of complaint follow-up. We identify gaps in who gets asked and agree who has authority to respond.

  2. 2

    Survey and audience approval

    Your team approves the survey purpose, wording, audience, and timing. Language checks and any required compliance review happen before the survey is released.

  3. 3

    Pilot and follow-up check

    A small customer group receives the survey first. We check whether questions are understood and whether a critical response reaches its named owner.

  4. 4

    Live response handoff

    The agreed survey process starts, with responses recorded and assigned for follow-up. Your responsible team handles customer conversations and records what was done.

  5. 5

    Findings and action decisions

    Results are compared with the baseline, and repeated issues go to the team authorised to address them. Reporting frequency is agreed in writing before work starts, alongside the confirmed scope and term.

Approval and acceptance

Use an observable check before accepting an output.

These are proposed review checks for the named outputs. Agree the final conditions in the written scope, then record any missing requirement before accepting the handover.

  • Survey selection and purpose

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Approved question set

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Audience and trigger rules

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Channel and message plan

    Use the draft in the selected enquiry scenario. The reviewer can identify the intended reader, verify the statements against supplied facts, and point to the next action without adding an explanation.

  • Feedback and follow-up log

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Low-score response guide

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Baseline and reporting view

    Trace a finding to the supplied evidence. Separate observations from assumptions and identify the decision or action that follows from the finding.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

How is customer satisfaction, nps and feedback programmes scoped for granite processors?
Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief. Resolve an outstanding delivery issue before asking for advocacy or another purchase. Respect contact preferences.
Do we need NPS, or will a simple satisfaction question do?
A satisfaction question is a better starting point when you need feedback on a specific delivery or visit. NPS asks about willingness to recommend and suits an ongoing relationship. We choose the measure according to the decision you need to make.
Can we use our existing spreadsheet or survey tool?
Yes, if it supports the agreed questions and follow-up record. We review what you already use before recommending changes. Paid tools, message charges, and any separate technical setup are identified in the written scope.
Will GullySales resolve every complaint?
No. This service defines the callback process and records the handoff, but your authorised team decides remedies. A wider service recovery programme or formal complaint escalation process is separate work.
Can the survey run on WhatsApp?
Yes, subject to the agreed setup and your approval of contact permissions and message handling. Your adviser must review applicable requirements before launch. For a bank or healthcare provider, your own compliance team must also approve the questions and information collected.
Will higher satisfaction scores prove that sales have improved?
No. A survey score is not an order, and people who reply may differ from those who do not. Where your records allow it, feedback is reviewed alongside repeat enquiries and completed orders without treating the survey as their sole cause.

Your brief

Tell us what you need, and we will read it before we call.

Eight short steps about your business, what you want and who decides. Most questions are a tap, and you can skip any you would rather answer on the call.