Skip to main content
GullySystem
AI for Marketing · Solutions

Reply, follow up and stop over-messaging.

AI Engagement sets up a chat assistant on your website and messaging channels that answers from approved content, drafts replies for staff and keeps follow-ups on a schedule. Anything it cannot answer, and any upset customer, goes to a named person who reads the whole conversation before replying, so nobody repeats their story. It supports staff, never replaces them.

What it is

Questions arrive when nobody can answer. A salon, gym or restaurant hears about opening hours, package prices and Saturday tables late in the evening, and many of those people never ask a second time.

An assistant can answer the routine questions from content you approved, and take a booking request or a callback number for the rest. Staff then see which channel each customer prefers, when they reply and what they ask about, so the next message fits the person instead of the whole list. Every reply stays on record.

Where it goes wrong today

The problems this is meant to ease.

Questions land when nobody is free

Late questions go cold. A message sent after closing waits until morning, and by then the customer has asked a competitor who replied the same night.

Every channel has its own inbox

Three inboxes, one customer. The same customer writes on the website chat, a messaging app and email, and nobody sees the three threads together, so each reply starts from nothing.

Replies that differ by person

Two staff, two answers. One person quotes last year’s package, another promises a slot that is full, and the customer notices when the two answers disagree.

Too many messages, or too few

Some are nagged, some forgotten. One offer goes out three times to one person, while a customer who has not visited for months hears nothing at all from you.

Enquiries that never get chased

Interest fades without notice. A visitor asks about a package, leaves a number, and nobody calls back because the request lived in a chat window that no one reopened.

No view of conversation quality

Nobody knows how chats went. Staff count messages sent, not whether the customer got an answer, so the same unanswered question keeps arriving and the same confusing page stays on the site.

Inside the module

What AI engagement does.

Answers from approved content

It never guesses an answer. On your website and messaging channels it replies only from a library your team approved, such as hours, policies and directions, and says when it does not know.

Handover to a person

Nobody repeats their story. A customer who is upset, asks for a refund or types something outside the library is passed to a named staff member with the full chat attached.

Suggested replies for staff

A draft, never an automatic send. For messages that reach a person, the software proposes a reply from past answers and the customer’s record, and the staff member edits it before it is sent.

Follow-up workflows

Late enquiries become tasks. Name, phone and the thing wanted are saved to the customer record, and a question asked at night becomes a callback task assigned to one person and due on a set day.

Interests and content preferences

Notes follow the customer’s own behaviour. The topics a customer asks about, the offers they open and the channel they answer on are noted on their record, so staff and campaigns can follow it.

Frequency and timing limits

Quiet hours are respected. Each customer has a weekly message limit and a window when they usually reply, and the software holds back any send that would break the limit.

Nurture and win-back

Staff approve each batch. New enquiries, lapsed customers and nearly-earned rewards each get a short set of messages from your rules, such as a birthday offer or a note after a long gap.

Interaction quality review

Measure how conversations go. Weekly lists show unanswered and handed-over questions by topic, reply times and how customers rated it, so you can add a missing answer or fix a confusing page.

Where it gets used

What this looks like in a working week.

A salon

Late-night booking requests. Prices and opening hours come from approved content, a booking request is taken at midnight, and the receptionist confirms it in the morning with the chat attached.

A gym

Win back quiet members. Members who have not visited for a long gap get a short message from rules the manager approved, and replies come back to a named trainer.

A restaurant

Weekend questions arrive in bursts. Guests ask about tables, allergens and parking on a messaging app, the assistant answers from the approved menu notes, and any allergy question goes to the manager.

A coaching centre

Parents repeat the same questions. Fee schedules, class timings and holiday dates are answered from one approved sheet, and a parent who wants a counsellor is passed to a named person.

A hotel

Stay in touch after a visit. A repeat guest gets a birthday offer and a note before a quiet season, messages are capped per guest, and a reply of stop removes the person.

Who touches it

The people who open this every day.

Front desk or reception

Takes over the handed chats. Reads the whole conversation before replying and confirms the booking requests that came in overnight while the doors were shut, so the morning starts organised.

Owner or manager

Owns the answers. Writes and approves the answer library and the reward rules, and reads the weekly list of unanswered questions, so gaps get filled with proper answers instead of guesses.

Marketing lead

Plans the follow-up rules. Plans win-back messages and offers against the customer list, sets the frequency limit, and reviews each batch with a sample of real recipients before anything reaches customers.

Customer support agent

Takes the hard cases. Handles the difficult cases that arrive with their context attached, and can correct any answer the assistant gave earlier in the same conversation, so hard calls get attention.

How it is set up

From first conversation to daily use.

  1. Discovery

    List every channel first. Owner, reception and marketing lead sit down with us, and together we list the channels where customers write, the questions they ask most and who answers them.

  2. Data readiness

    Write the answers down first. The common questions get approved answers, customer contacts are gathered into one list with the date and source of each permission, and past chats are read for gaps.

  3. Trial on website chats

    Start with the website chat. It answers on the website chat alone with a staff member watching every conversation, and nothing is sent to the customer list during this stage.

  4. Front desk review of live chats

    Staff mark the wrong answers. Support agents and reception staff read real conversations, mark answers that were wrong or cold in tone, and each mark becomes an edit to the library.

  5. Going live

    Add channels one by one. Messaging apps and email follow the website chat, win-back messages start with one small group, and the one-switch pause stays within reach of the manager at all times.

  6. Reviewing afterwards

    Read the weekly lists. The team reads unanswered questions, reply times and opt-outs after a full cycle, adds missing answers, retires messages that annoyed people and compares each measure with its baseline.

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.

  • Engagement rate counts opens, clicks and replies against messages delivered, and the baseline is that count taken from your email and messaging tools for the campaigns before go-live.
  • Response rate counts customer messages answered by a person or the assistant, and the baseline is the answered count from your inbox and chat records before go-live.
  • Lead nurturing conversion counts enquiries that became bookings or sales after follow-up messages. The same count, taken from your CRM for the three months before go-live, is the baseline.
  • Handover rate counts conversations passed to a person, and the baseline is the number of chats your staff handled by hand in the weeks before go-live.
  • Opt-outs and complaints are logged after every send, and the baseline is the count from the last campaigns you sent to the whole list before frequency limits began.
Used responsibly

Where a person stays in charge.

A person owns the answer library

Someone must own the updates. Replies come only from the library your team approved, so a wrong answer is a wrong entry that a named person fixes, and early chats are read.

Upset customers reach a person

Sensitive topics go to staff. Refund requests, complaints, health or allergy questions and anything outside the library go to a named staff member who receives the whole conversation, and the assistant stops replying.

Consent and opt-outs

A reply of stop is final. Each customer’s permission is saved with its date and source, and an opt-out removes that person from every later send on every channel.

Messaging rules differ by country

Rules are set by country. Duties for direct messaging, template approval on chat apps and keeping chat records vary by country and platform, so your own lawyer should confirm each. It prepares records, not legal advice.

Limits of the assistant

Staff keep every decision. It cannot judge tone, take payment or promise a refund, and staff can pause it on every channel with one switch for a holiday or an away day.

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.

  • Website chat
  • WhatsApp Business messaging
  • Booking or appointment software
  • Point of sale or billing
  • Customer records in your CRM
  • Email and SMS tools
Common questions

Questions owners ask about AI engagement.

Will it say wrong things?

It can still be wrong. It answers only from content you approve and hands over anything else, which limits the risk without removing it, so someone must own updates and review early chats.

Do we need WhatsApp for this?

A website chat alone is enough. WhatsApp can be added later through the official business interface, which has its own message approval steps, and rules vary by country and by the platform’s own terms.

Which data does it use?

Start with approved answers. Your customer contacts with the date of each permission, a booking or billing system if you have one, and your usual questions are enough to begin.

Is a loyalty scheme worth it?

Only where visits repeat. As at a salon, a cafe or a gym, points matter when visits repeat, while a business that sells once in years gains little.

What about privacy and permission?

Rules depend on the country. Consent and direct messaging duties differ by market, so your own lawyer signs off how permissions are captured, and the software only prepares records. It gives no legal advice.

Can staff pause it?

Yes, with one switch. It pauses on every channel and a short notice tells visitors that a person will reply, which suits holidays or a day when stock is uncertain.

When is this not worth it?

When few people write in. A shop that gets only a handful of messages does better with a person and a phone, since the library only makes sense once volume rises.

What effort does setup take?

Mostly writing and tidying. Someone writes the approved answers and the reward rules, the contact list is cleaned up with permission dates, and then channels are connected one at a time.

Talk to us

Tell us how you handle AI engagement 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