Skip to main content
GullySystem
AI for Marketing · Solutions

See what your buyers want and say.

Customer Insights joins enquiries, orders, website visits, replies and survey comments into one profile per buyer, then groups similar buyers and reads their feedback for themes and mood. Personas are summaries, not people. Marketing decides what to act on. It works only with data you may hold, so a consent record and a customer ID shared across your tools matter more than any model.

What it is

Marketing holds one picture of the customer. It lives in the head of whoever has been there longest, while the CRM, the billing system and the newsletter list each spell the same customer’s name differently.

Customer Insights matches records from every system into one profile per buyer and reads the words customers use, in reviews, surveys and chats, for themes and mood. Who bought twice, who reads every mailer without buying and who went quiet after one quote can each be listed on request.

Where it goes wrong today

The problems this is meant to ease.

Four tools, four customers

The CRM, billing and newsletter each hold a different spelling of one buyer, so counting customers means arguing about which list is right. Nobody trusts the count.

Feedback nobody has time to read

Hundreds of survey comments, reviews and chat messages pile up in separate places, and only the loudest complaint reaches the marketing meeting. Quiet themes are missed.

Campaigns planned from guesses

The team writes for an imagined average buyer, so the trade customer and the one-off gift buyer both receive a message meant for neither. Neither buyer feels addressed.

Unmet demand goes unnoticed

Buyers ask for a size, a model or a service you do not offer, and the request ends in one rep’s notebook. Nobody counts the asks.

Customer data used without clear permission

Contact lists get copied between tools with no record of who agreed to what, and a campaign reaches someone who opted out. Lost trust is hard to rebuild.

Satisfaction noticed only after churn

A slow decline in survey mood across one product line goes unseen until orders thin out, because no one tracks it month by month. The warning came early.

Inside the module

What AI customer insights does.

One profile from many systems

Records are matched on phone number, email and name variants, and a person confirms matches so two buyers with one surname are not merged. Careful matching comes first.

Personas built from behaviour

Groups such as repeat trade buyers, one-off gift buyers and quote-shoppers who never order are found from what people did, then named by your team. You name them, not the software.

Feedback read in bulk

Survey answers, reviews, chat messages and ticket text are grouped by theme, such as delivery delays or sizing, with sample comments kept beside each theme. Every theme links to its source.

Satisfaction trends over time

Mood in feedback and survey scores are tracked by month, product and channel, so a dip after a price change is visible. Mood readings are indications only.

Unmet needs and rising interests

Enquiries for products you do not stock, site searches with no result and questions repeated in chats are counted and listed. Rising interests show before sales do.

Questions asked in plain words

Ask which persona buys most in the festival season, or which source brings enquiries that never reply, and records back the answer. Every answer can be checked.

Recommendations for the marketing team

Each finding arrives as a suggested action with its evidence, such as a persona to target, a message to test or a product gap. The team accepts or drops each.

Consent kept per profile

Each contact carries a consent flag and a source for every field, and any activity without a permission is left out of that contact’s profile. An opt-out always wins.

Where it gets used

What this looks like in a working week.

A clothing store with three channels

Showroom visits, website browsing and WhatsApp enquiries are matched to one profile, and the team sees which buyers browse often but never order. The owner decides what to try.

A digital marketing agency for a client

Reviews and survey comments from a client’s customers are grouped by theme, and the account lead brings the themes to review. Each theme links to comments.

A furniture showroom learning from enquiries

Enquiries for a product line the showroom does not stock rise through the year, and the count appears on the unmet-needs list. The owner decides whether to range it.

A SaaS company reading support tickets

Ticket text from one product module shows a repeated confusion about setup, and the product and marketing teams see the same theme. Both teams act from one view.

A travel agency before the season

Past bookings and enquiries show which kinds of traveller ask early and which ask late, and marketing plans the mailers around those groups. Consent is checked first.

Who touches it

The people who open this every day.

Marketing lead

Reads the persona summaries and feedback themes before planning a campaign, tests each against a sample of real customers and rewrites the names in the team’s language. A persona nobody recognises gets dropped.

Sales manager

Sees which kinds of buyers convert from enquiries, and through which channel, before deciding where the reps should spend their calls this month. Calls go where buyers are.

Owner of the customer data

Keeps the matching rules and consent flags in order, reviews uncertain matches weekly and decides which fields may feed a persona. Sensitive fields stay out.

Customer service lead

Reads the complaint themes beside the satisfaction trend and passes recurring issues to the teams that own the product or the delivery. Fixes come before campaigns.

How it is set up

From first conversation to daily use.

  1. Discovery with marketing and service

    We list which customer questions the team cannot answer today, which systems hold the answers and who owns each, before any data is moved. Consent rules come up early.

  2. Data readiness across the tools

    Exports from the CRM, billing, email and survey tools are matched on a sample, and the customer ID and consent flags are checked. Gaps are listed, not guessed.

  3. Trial on one slice of data

    Profiles, personas and feedback themes come from a single product line or region. They use live records, and nothing goes out to customers. Marketing reads the output.

  4. Checking the output with the team

    Marketing, sales and service test each persona and theme against customers they know, and rename or drop the ones that nobody recognises. Uncertain matches are reviewed too.

  5. Going live with a weekly view

    The profile screen, feedback themes and plain-question box open to the marketing team, with consent rules and the review queue switched on. More channels join later.

  6. Reviewing what was acted on

    After a few campaign cycles the team reviews which recommendations were taken up, which personas proved useful and which data fields should be dropped. Definitions change with the review.

Measuring it

How you would know it is working.

Record where you stand before it goes live, so the change is measured against your own figures.

  • Insight adoption is the count of recommendations that marketing accepted and acted on, taken from the review log, and it has no baseline because the log starts at go-live.
  • Customer satisfaction is the survey score or feedback mood by product and month. For the baseline we use the latest surveys and reviews collected before go-live.
  • Campaign performance is the response and order rate of each campaign against its audience, and the baseline comes from reports of campaigns run before go-live.
  • Matched profiles is the count of customers whose records from different tools are joined into one, and the baseline comes from a sample match run before go-live.
  • Unmet-need requests counts enquiries and searches for things you do not offer, and the baseline is a manual tally from recent months before go-live.
Used responsibly

Where a person stays in charge.

Consent comes before analysis

Every field has a source and a permission, activity without one is excluded, and opt-outs apply across tools. Profiles hold only permitted data.

Rules differ by country

What you may track and keep depends on where your customers live, so your own lawyer should sign off the setup. Product text is not legal guidance.

Groups describe patterns

A persona describes a pattern across records and says nothing certain about one buyer, so nobody is refused service because of it. Treat them as patterns only.

Thin profiles are shown as thin

Where a profile rests on one phone call the screen says so, and thin profiles are counted instead of padded with guesses. Gaps are never hidden.

People decide what to act on

Recommendations are suggestions with evidence, and the marketing lead accepts or drops each, so nothing is sent from here. Sending happens in your own tools.

How it fits

It is one part of a system, not an island.

A module earns its place by what it passes to the next one. These are the connections we set up most often.

  • CRM contacts and accounts
  • Website analytics
  • Email marketing tool
  • WhatsApp and chat
  • Order and billing records
Common questions

Questions owners ask about AI customer insights.

Does tracking buyers need their consent?

What you may track, and what consent you need first, depends on where your customers live, so a lawyer you appoint signs off the setup. In practice consent is recorded against each contact, and any activity without a permission is left out of that contact’s profile entirely.

How many customers do we need?

Several hundred buyers, each with a few recorded actions, is a sensible floor before the groups stop changing every time you refresh them. Below that, a good salesperson’s notes will tell you more than any clustering run, so improving how data is captured comes first.

Will it decide who gets which campaign?

It proposes groups and lists what their members have in common, and the marketing lead chooses who receives which message after reading the evidence behind each group. Nothing goes out from the screen.

What if records sit in three tools?

That is the normal case, so the first piece of work is connecting them and agreeing which tool is right when they disagree, before any persona work starts.

How does it read customer feedback?

Survey answers, reviews, chat messages and ticket text are grouped by theme and given a mood reading, with sample comments kept beside each. Sarcasm and mixed feelings are often misread.

Which tools does it connect to?

It needs read access to your CRM, order records and email tool, and website analytics, chat and survey tools add more, depending on what each product allows. We check each link before quoting.

What effort and cost should we expect?

Most of the effort is agreeing a customer ID, cleaning duplicates and deciding which fields may be used, and your team does that with us at the start. Cost depends on tools and data. We quote after seeing both.

When is it not worth doing?

When you sell to a few dozen accounts and know each buyer personally, personas add nothing, and a conversation with the account owner is the better source.

Talk to us

Tell us how you handle AI customer insights today.

A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements