Skip to main content
GullySystem

Personalised Offers and Reminders for Customers

AI-powered personalisation decides which offer or reminder each customer receives. Decisions use each customer’s buying history and timing, within rules you set. A group that received the standard message is kept for comparison. Nothing is assumed.

Personalisation without a large website

Many businesses do not run a large online store, so the useful form is quieter and more specific to the customer’s own pattern of buying. A service reminder is timed to when the customer usually returns. A festival offer goes only to buyers of that category. A dealer message lists what the dealer usually reorders and has not. Each is a small, specific decision.

What each decision uses

Purchase history

What the customer buys, how often, and the gap since the last purchase. For most businesses this is the strongest signal held.

Stage

A new enquiry, a first-time buyer, a regular and a lapsed customer each receive a different message.

Your rules

Categories never to promote, customers under dispute, and frequency caps so nobody is messaged twice in a week.

Channel

Where the person actually responds, since a WhatsApp message and an email carry different weight per customer.

Comparing against a control group

A control group keeps receiving the standard message. Without that comparison, a rise in orders during a festival month proves nothing. Results are reported per campaign against the control, including campaigns that made no difference. Those matter too.

FAQ

Frequently asked questions

Does personalisation work without customer logins?

Yes, where the customer can be identified another way, such as a phone number on the bill, a dealer code or a loyalty card number held at the counter. For anonymous website visitors it is limited to session behaviour.

Will customers find this intrusive?

They can, and frequency is usually the cause more than relevance. Caps and quiet hours are set from the start, with a plain way to stop receiving messages. Opting out is simple.

What data is actually needed?

A customer record with a usable identifier and a purchase history with consistent item codes. Where one product sits under three codes, the history is less reliable.

How long before an effect shows?

It depends on the reminder cycle. A monthly reminder needs several cycles for the comparison to mean anything, and a two-week reading reflects the season more than the personalisation.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements