Skip to main content

In Review

18

Under consideration

Feature Request

Add 'chat_id' Filter to 'GET /chats' Endpoint

Problem: Currently, to find all interactions with a specific contact across multiple Org Phones, we must either: List all chats for the entire org and filter manually (slow due to created_at sorting). Call GET /chat/:id repeatedly for every single Org Phone in our workspace. Proposed Solution: Add a chat_id query parameter to the GET /chats endpoint. Expected Behavior: GET /chats?chat_id=919876543210@c.us should return an array containing only the chat objects for that specific JID across all organization phone numbers. Benefit: This allows developers to retrieve a contact's activity and labels across the entire organization in a single, high-performance API call without the overhead of maintaining a separate webhook database.

Arsh Gupta
Feature Request

Native CSAT for Customer Support Evaluation

I would like to suggest the implementation of a native CSAT (Customer Satisfaction Score) feature to evaluate customer support interactions directly within the platform. The idea would be to allow an automatic satisfaction survey to be sent whenever a conversation is closed, with the option to configure which types of conversations should receive the survey. For example: Send CSAT surveys only for private conversations; Allow administrators to choose which channels or conversation types should receive the survey; Enable or disable CSAT surveys depending on the operation’s needs; Automatically send the survey after a conversation is closed. This feature would be very helpful for monitoring customer support quality, allowing teams to measure customer satisfaction directly within the platform without relying on external tools or manual processes. Additionally, being able to define which conversations should receive the survey would help prevent CSAT requests from being sent in situations where they may not be appropriate, such as certain group conversations or internal interactions.

Thayná - Atendimento Avançado
Feature Request

Per-number notification settings

We run several WhatsApp numbers in one workspace and each team member only handles one or two of them. Right now notifications are workspace-wide, so everyone gets alerted for every number, or nobody gets alerted at all. Request: let each user choose which numbers trigger sound/push notifications in their own notification settings (a simple checklist of the org's numbers). Ideally combined with the existing notification-type toggles, so I can say "sound for new messages on number A and B, silent for the rest". This is the biggest source of notification noise for multi-number teams, and it's a per-user preference, so it shouldn't affect how the workspace is configured for others.

Alejandro
Feature Request

Notify on internal notes only when @mentioned

Today the notification setting for internal notes is all-or-nothing: any internal note in any chat triggers a sound/push, even when nobody is tagged. In a team with several agents this means constant noise, so most people end up disabling internal-note notifications entirely, and then miss the notes where they are tagged. Request: add a third option for internal notes: "Only when I'm @mentioned" (alongside the current on/off). Tagging someone in a note already creates a task for them, so the intent is explicit; the notification should follow that same logic. Nice to have: same option for group chats (notify only on @mention), which is how WhatsApp itself behaves.

Alejandro
Feature Request

Organisation working hours

There should be an option to set the days of working along with operational hours for the AI Agent

Arihant Agarwal
Feature Request

option to open chats in new tabs

We were delighted when the option to open multiple chats in tabs just like chrome we have chats and can follow up with 4 customers at a time. sadly it has been disabled. I think it would be better if can have a toggle if somebody doesnt want this feature. but i and my team loved this tabs feature. i request to bring it back

Taher Madarwala
Feature Request

Option to bulk update custom properties of tickets by selecting them

Custom properties currently can be updated by clicking on individual tickets. Would be great to have an option to select multiple tickets and update their property.

Bhavik / Urvi
Feature Request

Notifications based on different filters/ labels

Is there a way I can choose which notifications to receive on a granular level? Like I want to receive notifications of DM and not of Groups messages. Aur I want to receive notifications only from messages in a chosen filter/ label etc. If not, I believe this could be quite powerful. Right now, my only option is to disable all notifications because I get a notification almost every few seconds. But I do want to get notified for important messages I feel that most of your customers will be getting a barrage of messages so categorising notifications can be a good addition.

Maaz Azam
Feature Request

setting user permissions like how we have for phone numbers

i loved the feature where we can share limited settings access to staff like enabling setting but disabling analytics. but can we get feature where a certain staff gets analytics access , other have new user creation and so access.

Taher Madarwala
Feature Request

Provide a UI-level option to export and manage common groups

Issue Type: Request Issue Description: Currently, common groups cannot be exported or copied. Request: Provide a UI-level option to export or copy common groups, similar to the existing export functionality. While exporting from chat list, please also include a “Last Active” column.

Joshnavi

In Progress

9

Actively being built

Feature Request

Follow-Up Reminder Feature Request for Periskope Dashboard

I would like to request the addition of a “Follow-Up Reminder” section on the Periskope dashboard to help track pending client follow-ups and reminders efficiently. This feature would improve task management and ensure timely communication with clients. Kindly find the attached sample image for reference and consideration.

Zainab Rampura MTT Packages
Feature Request

Ticket assignment based on member flag it

It would be beneficial to implement a new rule for ticket assignment based on member flags, as it can improve efficiency and accuracy in routing tickets.

aditya.h
Feature Request

Contact upload and download format should be same

currently we have contacts that are synced with whatsapp and if we have multiple numbers connected, then the system shows 1 name now and other name after a while. i request to make this option so that we can download periskope contact and make necessary changes and upload the same file. as manually typing every name and number is a nightmare.

Taher Madarwala
Feature Request

Task Pop ups

Whenever we create a task and set a time and date for the same , the system should throw a pop up to the user to notify that he needs to finish / clear that task . Currently there is no pop up and chances to miss out on the same are very high . Also if you can set up the pop up , there should be a snooze button for the pop up just in case i need to take that up again after a few hours

Classic Holidays
Feature Request

Add sender_name (WhatsApp display/push name) to the message object

Currently the message object identifies the sender only by phone-based IDs — author, from, and sender_phone all return values in the {phone_number}@c.us format. There's no field for the sender's WhatsApp display name (push name), which is what WhatsApp itself shows in group chats. This means any consumer of the API has to either show raw phone numbers or maintain a separate phone → name mapping and keep it in sync via the contacts endpoint. That's an extra lookup per message. Requested change: add a sender_name field to the message object, populated with the sender's WhatsApp push name (nullable when unavailable). Ideally this is also included in webhook payloads so real-time consumers don't need a follow-up API call.

Shobhit Mohanty
Feature Request

Dashboard improvement Suggestion to add summary of top 10 issues

Suggestion to add summary of top 10 issues in dashboard for last 24 hours with count of clients raised those issue on the dashboard. for ex:

Nidhi Senwal
Feature Request

Delivery-status webhook for broadcasts (alert on failed ack)

POST /message/broadcast returns a broadcast_id, but that only proves the request was accepted, not that anything delivered. During a recent outage, a completely dead queue and a healthy one looked identical from the API — every call returned 200. Two things would close this: A message.ack.updated webhook (or confirm it exists) so we can alert on ack: -1 (failed) within minutes. A broadcast-level delivery-status endpoint, like the per-message GET /messages/{unique_id}/status. Right now there's no supported way to detect that scheduled messages silently stopped sending.

Shortcastle Technologies
Feature Request

API to list scheduled broadcasts

There's no way to fetch pending scheduled broadcasts via the API. GET /v1/message/broadcast and /v1/message/broadcasts both 404. The dashboard (Bulk Messages → Scheduled) shows them, but the API can't. Impact: when our broadcast queue stalled, we couldn't enumerate what was pending or reconcile after recovery — we had to work blind. A GET that returns pending broadcasts (id, chat, message, scheduled_at, status) would make the API self-sufficient for anyone automating reminders.

Shortcastle Technologies
Feature Request

Search functionality in the Scheduled Messages section isn't indexing text within polls

https://console.periskope.app/settings/scheduled If i want to search for a word in a poll (even if its in the heading of the poll as opposed to the choices) it doesnt search, it only searches scheduled messages that are not polls) Can you allow it to search for text within polls please?

Christian Steiner (Main)

Completed

150

Recently shipped

Feature Request

Support for vCard attachments (.vcf files)

It would be useful to support the upload vCard files (.vcf)

Gabriele Piccinnu
Feature Request

Bulk export of chat audit logs (all chats, not one at a time)

Currently, chat audit logs can only be viewed/downloaded per individual chat, which doesn't scale when analysing across hundreds of conversations. Request: Ability to export audit logs for all chats (or a filtered set) in one go, ideally as CSV/Excel, with filters for date range, label/tag, and assigned agent. Use case: We track how leads move through stages (lead → high-intent → paid) over WhatsApp. A bulk export would let us: Reconstruct the nurture journey for each lead over a given period Run cohort-level analysis on stage movements and response patterns Feed this data into our lead scoring model to improve accuracy Without bulk export, this analysis means opening chats one by one, which makes any cohort-level work impractical.

Shubham Pinge
Feature Request

Custom messaged for WA group invites

When forming a WA group via the system, we end up sending a generic message with the group chat invite. If we could send a custom message, or even a templated message which can be programed to say the client’s name or such, it would make the invite more personal, and the client wont’t consider it spam.

Yash S
Feature Request

General Customer Sentiment

Would be great that now that there is an (AI to extract data from specific chats) that the AI could build a general customer sentiment score, rather than checking on each chat individually.

Ignacio Fernández Baños
Feature Request

Custom Rules Engine

The custom rules engine allows users to create tailored workflows and automate repetitive tasks by setting specific conditions and actions. It evaluates incoming data or events against predefined rules, triggering automated actions to improve efficiency and reduce manual effort. This flexibility lets businesses to adapt Periskope to their unique operational needs without requiring manual intervention. Key Features and Example of workflows: Automated Responses: Automatically reply to messages with specific keywords or conditions. Send auto responses outside business hours. Ticket Creation: Raise tickets for messages with certain keywords or reactions. Automatically create tickets for flagged messages. Message Flagging: Flag messages with specific keywords for better categorization. Chat and Ticket Assignment: Auto-assign chats to team members using round-robin logic. Assign tickets based on multiple criteria. Label Updates and Ticket Management: Update chat or ticket labels based on criteria. Automatically close tickets when specific messages are received. Notifications: Send email notifications for events like ticket or chat assignments. Trigger webhook notifications based on conditions.

Periskope Support
Feature Request

Hide contact list to non-admin members

I think it is necessary that team members who are not Administrators do not have access to the contact list of the number. Not just their phone numbers, but the names and the whole list. It would be enough to set this permission for the non-administrator member role, or you could even make it so that members can only see the contacts that have a certain label assigned to them.

info
Feature Request

Auto-Assign System Enhancement

I would like to request a feature enhancement for the auto-assign system. Currently, the auto-assign feature does not detect the online or offline status of agents, so inquiries are still being assigned to all agents, whether they are online or offline. We propose enhancing the system to detect the agent status, ensuring that inquiries are only assigned to agents who are online. This will improve efficiency and reduce the load on agents who are offline. Thank you

CS Partner
Feature Request

Ability to forward multiple messages + Improve Search

You have built a great tool, but what sometimes becomes a challenge is the ease of how one would use normal Whatsapp. I think that has to be seamless for Periskope to be a non-brainer adoption rather than figuring trade-offs. 1. Ability to forward multiple messages at the same time. 2. When I search a name which is there in 100 groups, those 100 groups show in search results, so I have no way to jump to that contact to personally DM. This is quite intuitive in normal Whatsapp

Maaz Azam
Feature Request

Tickets to support internal comments

To align on the resolution details, handover to other staff, and add progress updates — comments is essential tool for teams to work on tickets and solve them.

Is S
Feature Request

Adding options like last 7 days, last 30 days, last 90 days in Last Active filter

I chose the date range of last 7 days yesterday and created a filter to address queries if my clients. This morning for quite some time, I thought my chats are complete cleared because I couldn’t see anything. Only on investigating, I realised that end time of my last active was set till yesterday in the filter. If we have an option like last 7 days, etc that dynamically updates it, would be very helpful. Something like this:

Maaz Azam