Smart Follow-Ups
Assigned is not finished. Somebody has to keep asking.
Tickets do not usually fail loudly. They go quiet on a Tuesday and nobody notices until the customer writes again, angrier. The chatbot chases the person who owns the ticket and tells the customer where it stands. Every single day it is open.
Order 88214, two items missing
Al Khuwair · WhatsApp · Owner: Maha, Fulfilment
- Promised to customer
- Today, before 5pm
- Owner acknowledged
- 09:26, 14 minutes after assignment
- Chases sent to owner
- 2
- Customer updates sent
- 1, with reason
- Revised promise
- Tomorrow, by 11am
Illustrative ticket
Where support actually breaks
An assigned ticket is not a finished one.
Almost every system in the market is good at the first ten minutes: capture the issue, write it up, give it an owner. Then it stops, and the rest is left to whoever remembers. Meanwhile the customer is holding a promise nobody is tracking.
It chases the person, not the queue
A ticket assigned to Maha is chased on Maha's phone, at intervals you set, until she acknowledges it or it goes back to the pool. Nobody has to notice that it went quiet.
It knows what was promised
Whatever the customer was told in the chat becomes the deadline. Every reminder is measured against that promise rather than against when the ticket happened to be opened.
It tells the customer, on their channel
Updates go back on WhatsApp or wherever the conversation started. The customer never has to open a portal to discover what is happening.
One ticket, followed the whole way
Two items missing in Al Khuwair, from assignment to confirmed.
Maha, Fulfilment
CB-4821 is yours. Order 88214 delivered to Al Khuwair with two items missing. Promised to the customer: an answer today before 5pm.
Thanks for telling us. Your missing items are logged as CB-4821 and Maha in our fulfilment team is on it. You will hear back before 5pm today.
What they are now expecting
An answer today, before 5pm
Told at 09:12
The promise made in the chat becomes the clock everything else is measured against.
The message nobody wants to send
When it will take longer, say so first.
Customers forgive delay. What they do not forgive is finding out about it themselves, at the end of the window, after clearing an afternoon. A message that arrives before the deadline with an honest reason and a new time costs you almost nothing. The same message an hour late costs you the customer.
So the chatbot watches the promise, not the ticket. When the promise is at risk it gets the reason from the person doing the work, sends it in the customer’s own language, and offers them a way to change their mind.
Fatma Al-Harthi
WhatsApp · 16:21
Sent 39 minutes before the 5pm we promised
1The count at our Sohar warehouse does not match the picking list, so we need them to confirm in the morning before we ship.
2You will have a firm answer by 11am tomorrow.
3If you would rather have a refund for the two items now, reply REFUND and we will process it today.
1The real reason, in words the customer can repeat to someone else.
2A new time with a number on it. Not soon, not shortly.
3A way out, so the delay becomes their decision rather than your announcement.
When nobody answers
Four steps, and the customer only sees the last one.
Reminder to the owner
Quiet, private, and repeated on your schedule. Most tickets never get past this step.
Back to the queue
If it is still unacknowledged after your limit, the ticket is released so someone else can take it.
Supervisor told
The person who has to answer for the delay hears about it while there is still time to fix it.
Customer told, with the reason
A revised time and the honest cause, sent before the original promise expires rather than after.
Everything it does between assigned and closed.
- Chase schedules set per category and per priority
- Acknowledgement tracking on every assignment
- Automatic return to the queue when nobody accepts
- Escalation to a supervisor before the deadline, not after
- Customer updates sent on the channel they wrote from
- Delay reasons recorded against the ticket
- Revised time windows the customer can accept or move
- Silence rules, so trivial internal steps never bother the customer
- Confirmation asked for after resolution, not assumed
- Reopening when the customer says it is not fixed
- Working hours and Omani public holidays respected
- Delay causes rolled up into reporting so patterns surface
One raises the ticket. This one refuses to let it rot.
Automated Support Tickets ends the moment the ticket has an owner. Smart Follow-Ups starts there and does not stop until the customer has confirmed it is actually sorted.
Automated Support TicketsFAQ
The questions Omani teams ask us most often.
How is this different from a reminder in our helpdesk?
A helpdesk reminder tells your team a date has passed. This chases a named person until they respond, escalates when they do not, and separately keeps the customer informed. The customer side is the part almost nobody automates, and it is the part they judge you on.
Will customers be spammed with updates?
No. Chatbot.OM only messages the customer when something they were told has changed. Internal steps like a ticket being opened or reassigned do not generate a message, because the customer's expectation has not moved.
What counts as late?
Whatever you promised. If the chat said an answer before 5pm, 5pm is the deadline. You set the point before it, typically an hour or two, when the chatbot must either confirm the work will land or start preparing the customer for a new time.
Can staff reply to the chase?
Yes. A one-line reply from the owner, such as needing another two hours or a part being out of stock, becomes the recorded delay reason and feeds the message the customer receives.
Does it respect Omani working hours?
Yes. You set the working week, the daily hours, and public holidays. Chases and customer updates hold outside those windows unless the ticket is marked urgent, so nobody gets a work reminder at 11pm on a Friday.
Does this need Automated Support Tickets?
It is built on it. Tickets are what get chased. If you already run a helpdesk we can chase tickets there instead, but the pairing is where it works best.
Automated Support TicketsYour website is quiet. Fix that.
Give us your website and we will have Chatbot.OM reading it today. Your customer data stays inside Oman.
Oman Personal Data Protection Law compliant · Data never leaves the Sultanate