Sin impuesto Con impuesto
Contact an expert button module
Read also on our blog

Contact an expert button module

Price: €48.40
First year: €48.40 tax incl.
From the second year: €12.10/year tax incl.
  • One year of technical support and lifetime updates; from the second year, support is extended for €12.10/year and includes taking on your general improvement ideas for the module.
  • Renews automatically; cancel whenever you want, with no minimum term.
One-time payment: €48.40 tax incl.
  • One year of technical support and lifetime updates; after that, support ends (with the subscription it is extended for €12.10/year).
  • A single payment, with no automatic charges.
€40.00 + VAT = €48.40

Put a face to your store: a customer service widget with phone, WhatsApp, email and opening hours, a team page and a public profile for each professional, all published as structured data so that Google knows who is behind the catalog.

PrestaShop 8.0 to 9.x.

Black Friday, 7 to 30 November: spend €50 or more on modules (VAT included) and we give you a €200 voucher (VAT included) to spend on more modules for one month. Ends in until 30 November at 23:59.

Expert content

Reviewed by our experts

Written by

Reviewed by

See all our experts

Content written and reviewed by qualified professionals. Information is provided for guidance only.

Questions about this product?

Trust

Before buying, he wants to ask someone.

And in your store, there's no one in sight. Expert Block puts your team in front of the customer when they're unsure, and in front of Google when it's deciding who to believe.

2 in 1
an attention widget to increase sales and an EEAT layer for positioning
1 person only
the same entity for Google on the team page, in its profile, and in its signature
8.0 → 9.x
Tested on PrestaShop 8.2.8 and 9.1.5

/ A widget that invites you to ask

A block displaying your team's avatars opens a side panel with phone number, WhatsApp, email, and hours. A green or gray dot indicates if someone is currently available. The WhatsApp message can already include the name and link of the product the customer is viewing.

By departments
Each department, with its categories, its experts, and its own contact channels.
Wherever you want it
Below the purchase button, in the warranty box, at the bottom of the listing, or in your own hook.
Actual schedules
It understands split shifts and stretches that cross midnight.
Outside of payment
It is hidden during the purchase process, so as not to distract in the final step.

/ One team page and one profile per expert

You register people in the Catalog › Experts with their position, biography, specialties, training, certifications, professional registration number, and networks. The module publishes the team page in /about-us and a profile for each person, with a configurable slug, canonical URL, hreflang, and entry in the sitemap.

/ Structured data that Google understands

Everything comes out as a single @graph JSON-LD per page: the store as an Organization with its point of contact and hours, the team page as an AboutPage , each expert as a Person within a ProfilePage with their specialties, credentials, training and the store they work for, and the breadcrumbs in both.

And any other module, a blog or some opinions, can sign its content with the expert using the displayRkrExpertByline hook.

Where it's worthwhile: in catalogs where the purchase depends on someone's judgment, such as for pharmacies, opticians, nutritionists, or those selling technical parts. Currently, the module only offers its text in Spanish and is not a multi-store feature .

Compatible with PrestaShop 8.0 to 9.x · PHP 7.4 or higher

Developed and maintained by REKIRE

v2.2.1

  • The panel is once again above the fixed bars. In 2.2.0 It was lowered to the Bootstrap offcanvas layer (1045), and any fixed theme bar above that value covered the panel header and its close button. Now it uses the width of a modal window: 1055 for the panel and 1050 for the background, without !important and configurable with --rkr-be-z-panel and --rkr-be-z-backdrop.

v2.2.0

It corrects what happened when installing it in a real store (PS 9.2 with Hummingbird), where it was necessary to overwrite two templates from the theme.

Accessibility

  • The panel opens with the keyboard. The block is a , which only responds to clicks: pressing Enter or Space did nothing. Now, both open it, focus moves to the close button, Escape closes it, and focus returns to the block. The block carries aria-expanded.
  • Telephone and mail in plain sight. The panel used to only show icons; now each channel has its label and the data (the number, the address), which is what the caller needs from the computer.
  • The button labels can be translated (previously "Telephone" and "Email" were fixed in Spanish) and the images are no longer all called "Expert": the avatar has the expert's name, the logo has the store's name, and the decorative avatars in the block are empty.

Behavior

  • The panel is only painted where there is a block. Previously, its script would appear on every page of the store, even though nothing could open it. The quick view of the listings also doesn't display the block, as it wouldn't open anything there.
  • Clean installation. It was installed with an active sample phone, WhatsApp account, and email, and with the team and expert pages turned on. /who-we-are, which was covering the store's CMS page. Now the contact appears empty and off, the pages are off, and the slug is equipment. The configuration alerts you while there is no active contact channel.
  • The update clears and turns off sample data only if they are still exactly the factory ones.
  • With the team or expert pages turned off, your route is no longer recorded.
  • The team page slug wasn't workingIt was saved by language and read without language, so the path was always /who-we-are. Stores that changed it will now have the URL they configured.

Styles

  • Out with the online styles !important of the panel (support notice, avatars, header, extra button) and of :root With colors: they are now CSS classes and variables that the theme can tweak. The colors of the extra button come as variables (--rkr-be-extra-btn), without loose in the body.
  • front.css no longer uses !important.
  • z-indexThe panel scales down from 99999 to Bootstrap's scaling, 1045 (that of an offcanvas), and 1040 for the background, configurable with --rkr-be-z-panel and --rkr-be-z-backdrop. It is below the modal windows.
  • The store logo, when used as an avatar, is wide and uncropped; a landscape logo was unreadable in the 70px circle.
  • The close button shows the focus (it had outline: none).

Structured data

  • Without Organization duplicate. The Classic and Hummingbird themes already declare one; the module displayed another on the homepage. New installations start with "Where to declare the store listing" in None.
  • New field "@ID of the Organization that already publishes the store"If it is filled in, the module does not declare its own company and depends on that. @id he ContactPoint with the schedule, the team page employees and the worksFor from the experts.
  • On pages without a block, the store's JSON-LD still appears, if necessary.

v2.1.0

Complete review of the module with a focus on structured data, which is the reason for the existence of the E-E-A-T part and was only partially completed.

Structured data (rewritten)

  • All JSON-LD is now generated in PHP (classes/RkrSchema.php) and comes out as a single @graph per page, instead of being handwritten on each template.
  • Stable identity with @id. The same person on the team page, in their profile, and in a byline is now a single entity for Google. Previously, they were three. Person different without identifier, and none accumulated the signal of the others.
  • It's over Organization anonymous on each page. The sidebar declared a Organization without yam neither url on all the store's URLs, which competed with the theme's URL. Now it displays the full store listing, with the @id shared, and only where it's needed: new option Where to register the store listing (default cover and contact information).
  • knowsAbout: the specialties, which were requested in the back-office and were only painted as labels, are published as the experience property.
  • worksForEach expert is linked to the store.
  • hoursAvailableThe opening hours already stored in the module are published as Opening Hours Specification within the ContactPoint.
  • Expert profile as Profile Page with mainEntity → Person, which is the format documented by Google for profile pages.
  • Breadcrumb List on the team page and on the cards, with real breadcrumbs (Home › Team › Expert).
  • hasCredential Corrected: the membership number goes in identifier with credentialCategory: license, Instead of a name with a made-up category, the certifications are separated by commas, and each one is a credential.
  • alumniOf It no longer turns the entire phrase of formation into the name of a university. It writes Title | Institution to declare it; without the slash, only the title is published.
  • Text values are cleaned of HTML tags and entities before serialization, and the JSON is escaped with JSON_HEX_TAG so that a biography with a cannot tear the page.
  • The microdata has been removed (itemscope / itemprop) from the expert record: they described the same person as the JSON-LD, with fewer properties.

SEO

  • The team and expert pages are added to the sitemap (gSitemapAppendUrls).
  • Canonical URL on both pages.
  • hreflang Correct: Each language uses its own slug, instead of repeating the slug of the current language pointing to a non-existent entry.
  • A non-existent or deactivated expert returns a 404 real in your URL, instead of a 302 redirect to the error page.
  • The expert's network links lead rel="me" instead of nofollowThey are the proof of identity that supports the sameAs.

Security

  • Image upload. The three avatar upload forms took the extension of the name sent by the browser and moved the file to views/img/, which is served via the web. Now the extension, actual image type and size (4 MB) are validated, the name is generated by the module and SVGs with executable content are rejected.
  • The configuration colors are validated as hexadecimal when saving and painting them; previously they were injected as is inside a label .
  • Escaped from the variables that were missing in the front templates.
  • File names read from the database are checked before constructing a URL with them.

Corrected

  • Split shifts and schedules that cross midnight. 09:00 - 14:00, 16:00 - 20:00 I only recognized the first section and 22:00 - 02:00 It was always closed. Logic now lives in classes/RkrSchedule.php and it is shared by the green dot and the JSON-LD.
  • Duplicate slugs. Two experts with the same name shared a slug, making the second token unattainable. Now they are numbered, and the update corrects any duplicates.
  • Two positions at the same time. With the active block in the tab and footer, the second tooltip wasn't working: the id They were repeated.
  • The uninstallation deleted 46 of the 74 configuration keys; those for the team and expert pages, the extra button, and the schedule survived and reappeared upon reinstallation.
  • The uninstallation is already complete. It does not delete uploaded imagesPrestaShop uninstalls and reinstalls to reset a module, and that emptied the product listings without warning.
  • The scheme has not changed since getContent(). The columns are created in upgrade/upgrade-2.1.0.php, and upgrade-2.0.2.php is idempotent.
  • Duplicating a department with untranslated languages no longer triggers PHP 8 warnings.
  • The demonstration data downloads avatars with a 5s timeout: in a store without internet access, the panel would freeze for one minute per expert.

Performance

  • The product, category, and department on the page are resolved once per request. All three hooks repeated the same load of Product and the same departmental inquiry.
  • The SELECT e., he. The expert lists now list their columns.
  • New index on (slug, id_lang), the column through which each request to an expert record enters.
  • The CSS of the byline has been moved to views/css/eeat.cssIt was on a label inside the hook and was repeated for each painted signature.

Added

  • Eyelash SEO and structured data in the settings.
  • Field Order in each expert, to cure the order of the team page.
  • Option to hide the widget during the payment process (enabled by default).
  • config.xml, , LICENSE.md, , README.md and index.php in all folders: the module passes the publishing audit without failure.

Known slope

  • The module does not include translation catalogs and its source strings are in Spanish: in a store in another language, the panel and the front end are displayed in Spanish.
  • It's not a multi-store: the boards don't carry id_shop and the configuration is read without store context.

You might also like

rkrmaileditor
€120.88
€99.90 + VAT = €120.88
Blog

4 other products in the same category

Viewed products

Questions and answers

  • ¿Qué incluye exactamente el módulo?

    Equipo de Rekire

    0
    • Dos cosas: un widget de atención con los avatares de tu equipo que abre un panel con teléfono, WhatsApp, email y horario; y una página de equipo en /quienes-somos con una ficha pública por cada experto (cargo, biografía, especialidades, formación, certificaciones, número de colegiado y redes).

      Equipo de Rekire The shop

  • ¿Cómo ayuda al posicionamiento en Google?

    Equipo de Rekire

    0
    • Publica un único @graph JSON-LD por página: la tienda como Organization con su punto de contacto y horario, la página de equipo como AboutPage y cada experto como Person dentro de un ProfilePage, con especialidades, credenciales y formación. Las fichas tienen URL canónica, hreflang y entrada en el sitemap.

      Equipo de Rekire The shop

  • ¿El mensaje de WhatsApp puede llevar el producto que mira el cliente?

    Equipo de Rekire

    0
    • Sí. El mensaje de WhatsApp puede incluir ya el nombre y el enlace del producto que el cliente está viendo, para que sepas de qué te pregunta.

      Equipo de Rekire The shop

  • ¿Puedo tener varios departamentos y horarios partidos?

    Equipo de Rekire

    0
    • Sí. Cada departamento tiene sus categorías, sus expertos y sus propios canales de contacto. Los horarios admiten turnos partidos y tramos que cruzan la medianoche, y un punto verde o gris indica si ahora hay alguien. El widget se oculta durante el proceso de compra.

      Equipo de Rekire The shop

  • ¿Está traducido y funciona en multitienda?

    Equipo de Rekire

    0
    • Hoy no: el módulo trae sus textos solo en español y no es multitienda.

      Equipo de Rekire The shop

  • ¿Con qué versiones de PrestaShop y PHP funciona?

    Equipo de Rekire

    0
    • Con PrestaShop 8.0 a 9.x y PHP 7.4 o superior; probado en 8.2.8 y 9.1.5.

      Equipo de Rekire The shop

Loading...
Cookie consent
Back to top