The Piyion support page keeps a record of development improvements, fixed bugs and changes to the integration with the official WhatsApp API. Each release covers the affected module, the reported behavior and the update communicated by the team.

This page will be updated with confirmed development reports. The most recent updates will appear first, while earlier releases will retain their context. This lets you follow how the platform evolves and find useful information when reviewing an issue.

Consolidated period: October 10–21, 2026. Information updated through October 21, 2026, based on the support summary. Log edited on October 22, 2026. The history of previous periods remains available.

How to read Piyion support statuses

  • New: a feature added according to the report.
  • Improved: an adjustment to an existing feature.
  • Fixed: behavior reported as corrected by development.
  • First version: a released feature whose use cases remain under validation.

These statuses describe the information in the log. A change marked as fixed does not guarantee that every similar case has the same cause. If the behavior persists, report it with steps to reproduce it.

Piyion support: changes from October 10–21, 2026

Information updated through October 21, 2026. This section covers the improvements and fixes ready to communicate from the October 10–21 summary. The period identifies the reporting window for Piyion support; it does not establish a separate deployment date for every change.

Tickets: second phase of development

Improved — Phase 2 of 3. Created tickets can be saved as recoverable drafts. The main Tickets view also refreshes automatically every 15 seconds, and the change history provides clearer tracking.

Options for configuring and editing fields and templates have also expanded, with adjustments to stages, types and attachments. A quick action lets users send templates to contacts associated with the ticket.

Page Builder: creating landing pages

New — Pages within Piyion. Page Builder also lets you create and publish landing pages from the platform. For example, you can connect an existing domain or use one provided by Piyion.

Shopify and WooCommerce: cart recovery

New — Recovery section. Stores connected through Shopify or WooCommerce have a dedicated section for recovering abandoned carts. This adds a specific management area alongside the data handling documented in the previous period.

Improved — Connection instructions. Instructions for connecting WooCommerce were added, following the guidance already available for Shopify.

Email and permissions: Piyion support improvements

Improved — Email history. The history of email template sends was improved to make communications easier to track.

Improved — Access notices. Tickets and CRM show clearer notices when an agent tries to change settings reserved for administrators. This helps distinguish a permission restriction from a product fault.

Piyion support fixes

Fixed — Quick replies. Issues that prevented the creation of audio, text and multimedia quick replies were resolved.

Resolved — Phone searches. Phone search and normalization were adjusted to prevent false duplicates when locating contacts. This complements the character cleanup documented earlier.

Fixed — Inactive user access. Sign-in validation prevents an inactive user from entering the platform. This fix applies to the check performed at sign-in.

Resolved — Creating template messages. An intermittent issue when creating template messages was also resolved. This fix is separate from the earlier adjustment for sending to contacts with active chats.

Fixed — PDFs in WhatsApp. The display of embedded PDF files in the WhatsApp channel of Piyion chatbots was fixed.

Piyion support: progress from October 6–9, 2026

Information updated through October 9, 2026. This section covers progress communicated by support for the October 6–9 cycle. The date refers to the reporting period, not a new deployment date for each feature.

CRM: Piyion support updates

New — Images and attachments. Sales management now supports files that keep supporting evidence alongside follow-up. The team can review the context of each activity without scattering files across tools.

Improved — Visual clarity. The presentation of CRM information was refined to make activities easier to read, review and update.

Tickets: first phase of development

New — Phase 1 of 3. Each ticket has an ID and a direct URL to simplify references and tracking. Drafts also preserve work in progress while a ticket is being written.

The content for detailed responses now supports up to 4,000 characters and includes rich text formatting. This release was the first phase of the Tickets improvements.

Mobile apps: Piyion support fixes

New — Tickets from chats and contacts. Tickets can be created and edited in the mobile apps from a conversation or a contact profile.

Fixed — Android. The app no longer closes when a user tries to assign a chat to themselves.

Fixed — iOS. App crashes when opening the app or assigning a chat to oneself were fixed. These stability fixes are listed separately from the new Tickets actions.

WhatsApp: connection and support improvements

Improved — Channel connection. The authorization sequence for the WhatsApp channel was clarified to reduce ambiguity between steps.

Improved — Access to the official channel. The links for requesting chatbots and support from Piyion through the official WhatsApp support channel were updated.

Improved — Interactive menus. Options are displayed more clearly to guide the conversation. This adjustment applies only to Piyion chatbots that use interactive menus.

Integrations: contacts, tags and recovery

New — WhatsApp ID and tags. When creating or updating a contact with a phone number and country code, Piyion can build and store its WhatsApp ID. Responses also include tag names.

Improved — Zapier. The Labels selector retrieves the company’s current tags, so automations can use the configuration in Piyion.

Improved — Shopify and WooCommerce. The integrations provide the buyer’s phone number and store tags for the mobile number and label variables in the abandoned cart recovery template. The documented scope is data handling and transfer; no new trigger rules are being announced.

Chatbots: Piyion support review and fixes

Improved — Preview and conditions. The editor separates responses, parameters, routes and events, with individual selection and scrolling. It also lets users choose the source and review numbered, independent or nested conditions. Conditions are not limited to multilingual cases.

Improved — Authorized editing. Authorized users can edit text and options in conditional responses, routes and events. They have an immediate preview and can restore individual responses without changing their logic.

Fixed and improved — Flow map. Connection points were fixed and the map was rearranged from top to bottom. Parallel routes are separated, and long or returning connections run around the cards. The initial view, side navigation and connection details were also adjusted.

Platform: access control and traceability

Improved — Access management. Controls were strengthened so user profiles can use the capabilities appropriate to their responsibilities. User creation records also provide context for support and administrative review.

Piyion support: other documented changes from October

The following changes were already part of the general October log. They appear only once here, and the original report does not specify their deployment dates.

Tickets: statistics and documentation

New — Ticket statistics. An initial dashboard now shows reported, open or active, resolved and closed tickets. This makes it possible to review operations without opening each request individually.

Improved — Initial setup and Description. The documentation area was adjusted for long content and different screen sizes. For example, it is easier to record background information, steps to reproduce and the context of a request.

Conversations: history and continuity of support

First version — Active chats in history. A contact’s history can show an active conversation and who is handling it. The team is still validating cases based on conversation status and how the conversation began.

Fixed — Duplicate conversations. A behavior that could create several active conversations for the same contact and channel was fixed. When an active conversation exists, new events should remain linked to it. This reduces fragmentation in the history.

WhatsApp: templates for contacts with active chats

Fixed — Sending from Templates. Sending to contacts who already have active conversations was restored. The settings let the team include or exclude them. Chat status therefore does not force a send; the team retains control over the selection.

To review the campaign process, see the guide to scheduled WhatsApp sends. You can also learn about our messaging with the official API.

Contacts: importing, deleting and exporting

Fixed — Visibility after import. An issue was resolved where the list appeared empty or failed to show new records correctly after importing a database.

Improved — Import process. The display of steps, statuses and results during an import was adjusted, giving users a clearer view of its progress.

Fixed — Deletion reflected on screen. The interface now updates after a contact is deleted. Previously, the record could remain visible until the page was refreshed manually.

Fixed — Export by creation date. The exported file now reflects the selected date range and excludes records outside the requested period. This makes the filter and result more consistent.

Data quality: cleaning the phone field

Fixed and prevented — Invisible characters. A specific case was fixed, and broader phone number cleanup was implemented. The adjustment covers creating, editing and importing contacts.

The cleanup also removes invisible characters, nonstandard spaces, line breaks, tabs and control characters. This reduces inconsistencies before saving or using WhatsApp-related information.

Access: email normalization

Improved — Sign-in. An email address is recognized as the same account regardless of letter case. Its value is normalized before validation.

Piyion support and the official WhatsApp API

If an issue affects WhatsApp, record the channel, the action taken and the error code, if one appears. Then check the official status of Meta services and the Meta error reporting tool.

These links are external resources. This log does not automatically copy their statuses or attribute a Piyion issue to Meta without verification. It is also useful to review the WhatsApp Business policies when analyzing message sends.

Open issues and follow-up

This log brings together changes confirmed for communication and is not an exhaustive list of issues. The case still under validation in the general log is the first version of active chats from contact history.

When development confirms an open issue, its record should include the report date, module, symptom, status, temporary workaround if available and latest update. The fix can then link to its corresponding release.

How to report an issue to Piyion support

To help the team review it, prepare the following details:

  1. Date, time and time zone when you observed the behavior.
  2. Module and channel, such as Tickets, contacts, conversations or WhatsApp.
  3. Steps to reproduce it: what action you took and in what order.
  4. Expected result and actual result.
  5. Error message or code, plus a screenshot without credentials or personal data.
  6. Frequency and impact: whether it happens every time, intermittently or only in one case.

Contact the Piyion support team with that information. This article serves as a change log; the team handles the issue report separately.

For a practical view of the features, visit Piyion updates. This article complements that page with technical details of the fixes.