Callback Requests

Summary of what the module offers

Callback Requests - Sales Call Lead Queue adds a callback button to a PrestaShop store and turns every request into controlled sales work. Basic operation starts with the shop's hours and notification address, while the scheduling, form, targeting, design, workflow and privacy settings support a larger team and several shops.

• Credible callback times: weekly hours, split shifts, overnight work, exceptions, public holidays, broad windows and exact bookable slots.
• One working queue: deadlines, live overdue state, click-to-call numbers, account links, statuses, notes, bulk handling and filtered export.
• Useful sales context: source page, product, variant, language and placement arrive with the request.
• A form that fits the business: selectable and required fields, translated labels, international phone handling and recorded consent.
• Precise storefront control: several placements, page and audience rules, visual settings, custom icon and phone visibility.
• Follow-up and privacy: separate notification controls, recovered delivery, overdue reminders, consent evidence and automatic retention.

How does the team keep every promised call under control?

Every request becomes a row under Customer Service with a clickable phone number, requested window, call deadline, source, notes and received time. Overdue state is calculated when the list is viewed, so a missed deadline appears immediately. Four figures above the list show new requests today, overdue requests now, calls completed today and the median time to call.

The workflow covers New, Called, No answer, Recall, Cancelled and Done. Status and notes change directly in the list, bulk actions process a group of requests, and filters narrow the work by status, deadline, product or date. A signed-in buyer's row links to the customer account, while the current filtered result exports to CSV for reporting or handover.

Repeated submissions from the same number and customer identity become one lead inside the selected duplicate period. The row records the extra attempts, fills in missing product context and keeps the earlier deadline when the later request is more urgent. The team therefore calls one person once without losing the strongest promise.

Where does the button appear, and who sees it?

You choose a floating button in any corner, a header position, a button beside Add to cart or a position provided by the theme. Each placement has its own switch. Inclusion and exclusion rules then restrict the button to selected products, categories and content pages, or keep it away from them.

Product rules also use price, stock state and quantity. Audience conditions distinguish guests from signed-in customers and target selected customer groups, so a wholesale enquiry reaches a different form than a retail visit. Each shop keeps its own placements, recipients, schedule and text.

Colours, border radius, form width, spacing and launcher dimensions are set in the module, together with a custom phone icon or image. A separate phone switch hides the launcher on small screens when space matters. The default design is responsive from installation, while the visual controls bring it into line with the storefront without changing the theme.