What are the responsibilities and job description for the Callback Requests position at mypresta.rocks?
A shopper who wants two minutes on the phone before ordering will not fill in a ticket form, and the requests that do arrive age out of sight in a shared inbox. Callback Requests turns each one into a row in a back office queue, with call-back windows, overdue reminders and storage that stays inside GDPR.
A callback request that arrives as an email is a task you will forget. This one arrives as a row in a back-office list with a status, a deadline and a place to write what happened. Filter by status, by window, by product, by date, or by whether it is overdue. Change a status inline, add a note without leaving the page, run bulk actions on a morning's worth of calls, and export the current view to CSV. Four numbers at the top tell you whether the queue is under control: new today, overdue now, called today, and how long you are taking to call people back.
The widget only offers times you can keep
A promise of "we will call you in five minutes" is a promise a person has to keep, and at 22:40 on a Saturday nobody keeps it. This module never makes that promise. It reads your opening hours and offers real choices: as soon as possible while you are actually open, this morning, later today, or your next open day. Outside hours it says plainly that you will call back within business hours and offers the next valid windows instead. The "usually within N minutes" line appears only while the shop is open, and the deadline in the back office is the same moment the shopper was shown.
Lunch breaks, holidays, timezones and the clocks changing
Opening hours are never a single range. This module takes several intervals per day, so the gap between them is your lunch break and no window will ever straddle it. Exception dates replace a whole day for a holiday or a stocktake, and you can import a country's public holidays instead of typing twelve dates. Each shop has its own timezone, every window is stored in UTC, and the scheduler is built around daylight-saving transitions rather than hoping they do not happen. The settings page shows exactly what a visitor would be offered right now.
Phone leads die quietly, so the module makes noise
The reason callback features fail is not that shoppers stop asking. It is that a busy shop misses one, then another, and the ones who were not called never say so. Callback Requests emails you the moment a request arrives, and emails you again when a request passes the window the shopper was given. Overdue is calculated when you look, so it is never a stale flag left behind by a job that did not run, and the reminder is recorded once per request so you are told about a problem rather than buried in it.
A phone number is personal data, so it is treated that way
Each request stores the exact consent wording the shopper agreed to, with a timestamp, so you can show what was accepted rather than what the page says today. The official PrestaShop GDPR module can export and erase a registered customer's requests, and because a guest leaves only a number, the settings page gives you a lookup that exports or erases by phone. Requests are deleted automatically after thirty or ninety days. Meanwhile a honeypot, a timing check, rate limiting and duplicate-number collapse keep the queue full of people and empty of bots.
PrestaShop 1.6 to 9, PHP 7.1 and newer
One ZIP installs on every PrestaShop release from 1.6 through the current 9.x, and runs on PHP 7.1 and every version since.
- A queue, not an inbox. Every callback request becomes a row you can filter, sort, annotate and close, with the phone number as a click-to-call link.
- Windows, never countdowns. The widget offers times computed from your opening hours, so it cannot promise a call you were never going to make.
- It nags you, not the customer. A request that ages past its window turns overdue and sends you a reminder.
- Knows where the shopper was. Product, page and placement are recorded with the request, so you open the call already knowing what it is about.
- Business hours with real edges. Breaks, exception dates, imported public holidays, per-shop timezone and correct behaviour across daylight-saving changes.
- Spam does not reach the queue. Honeypot, timing checks, rate limiting and duplicate-number collapse, so one impatient visitor is one lead.
- Choose where it appears. Show the button on chosen products, categories or pages, or everywhere except them.
- GDPR handled, not mentioned. Consent text stored with each request, official GDPR module hooks, lookup and erase by phone number, and automatic deletion after 30 or 90 days.
A callback request that arrives as an email is a task you will forget. This one arrives as a row in a back-office list with a status, a deadline and a place to write what happened. Filter by status, by window, by product, by date, or by whether it is overdue. Change a status inline, add a note without leaving the page, run bulk actions on a morning's worth of calls, and export the current view to CSV. Four numbers at the top tell you whether the queue is under control: new today, overdue now, called today, and how long you are taking to call people back.
The widget only offers times you can keep
A promise of "we will call you in five minutes" is a promise a person has to keep, and at 22:40 on a Saturday nobody keeps it. This module never makes that promise. It reads your opening hours and offers real choices: as soon as possible while you are actually open, this morning, later today, or your next open day. Outside hours it says plainly that you will call back within business hours and offers the next valid windows instead. The "usually within N minutes" line appears only while the shop is open, and the deadline in the back office is the same moment the shopper was shown.
Lunch breaks, holidays, timezones and the clocks changing
Opening hours are never a single range. This module takes several intervals per day, so the gap between them is your lunch break and no window will ever straddle it. Exception dates replace a whole day for a holiday or a stocktake, and you can import a country's public holidays instead of typing twelve dates. Each shop has its own timezone, every window is stored in UTC, and the scheduler is built around daylight-saving transitions rather than hoping they do not happen. The settings page shows exactly what a visitor would be offered right now.
Phone leads die quietly, so the module makes noise
The reason callback features fail is not that shoppers stop asking. It is that a busy shop misses one, then another, and the ones who were not called never say so. Callback Requests emails you the moment a request arrives, and emails you again when a request passes the window the shopper was given. Overdue is calculated when you look, so it is never a stale flag left behind by a job that did not run, and the reminder is recorded once per request so you are told about a problem rather than buried in it.
A phone number is personal data, so it is treated that way
Each request stores the exact consent wording the shopper agreed to, with a timestamp, so you can show what was accepted rather than what the page says today. The official PrestaShop GDPR module can export and erase a registered customer's requests, and because a guest leaves only a number, the settings page gives you a lookup that exports or erases by phone. Requests are deleted automatically after thirty or ninety days. Meanwhile a honeypot, a timing check, rate limiting and duplicate-number collapse keep the queue full of people and empty of bots.
PrestaShop 1.6 to 9, PHP 7.1 and newer
One ZIP installs on every PrestaShop release from 1.6 through the current 9.x, and runs on PHP 7.1 and every version since.