Skip to main content

Have something to say?

Tell us how we could make the product more useful to you.

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.

Joshnavi3 days ago

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.

Mention "all" in a group chat

To mention “all“ in a group chat (@All).

Pow Mei Jun10 days ago

Improve AI Session Logging for Self-RCA

Problem When an AI session is skipped, terminated, or fails to generate a response, the current session logs do not always show why execution stopped. For example, we observed a session where context was successfully retrieved, but the session ended with: 0 AI messages 0 tool calls 0 input/output tokens 0m duration There was no error or termination reason available in the session logs, making it difficult to complete RCA without involving Periskope Support. Requested Improvement Expose session pipeline stages Show the execution lifecycle and the last successfully completed stage: TRIGGER_RECEIVED → CONTEXT_RETRIEVED → PROMPT_BUILT → MODEL_DISPATCHED → OUTBOUND_SENT Expose termination/skip reason Whenever execution stops, display a clear reason/status, for example: SKIPPED_BY_ACTIVATION_FILTER AGENT_RESPONSES_DISABLED OUTSIDE_SHIFT_HOURS SENDER_INTERNAL_EXCLUDED LLM_DISPATCH_FAILED UPSTREAM_TIMEOUT Expose failure details Where applicable, show the error message, timestamp, failed stage, and relevant request/session identifier. Expected Benefit This would allow us to perform self-RCA for AI response failures, quickly identify whether an issue is configuration-, filtering-, or model-related, and reduce dependency on Periskope Support for individual session investigations.

Aman Kumar Singh11 days ago

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.

Alejandro15 days ago

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.

Alejandro15 days ago

Emoji based native rule action

Classify a stream of text into categories and accordingly add an emoji to it, and once the emoji is entered, it should initiate a workflow externally.

Gourang Kumar19 days ago

Quick replies in API

We are trying to setup automation so that we can send automatic meeting reminders with google meeting links along with person’s name and contact name so that 1 hour before the meeting a template can be chosen and sent automatically if API has that feature

Kirti prakash22 days ago

Universal Filters

If i can created some filters for myself using labels, my team should also be able to access them.

Shubham Bhatia24 days ago
Completed

Unable to send voice note on chats

While whatsapp web allows to send voice note on chats by clicking the mic icon and recording , periscope does not. Can this feature be added please ?

gauravisonline1 month ago
1
Completed

disable the existing ticket labels while keeping the historical ticket data

Hi Periscope Team, I’d like to confirm something regarding the ticket label changes. We’re planning to improve the current ticket labeling process and introduce new ticket labels. For the existing labels that are frequently used, we would like to disable them rather than delete them, as we’re concerned that deleting the old labels might affect or remove the historical data associated with them. Could you please confirm whether it’s possible to disable the existing ticket labels while keeping the historical ticket data and label information intact? We would appreciate your support and confirmation on this. Thank you!

septi.lingga2 months ago
1
Completed

Chat list report with all numbers inside a group

A new column showing all the numbers inside each group would be very useful. It would help us know which groups a specific number of ours is not yet part of. We could also use this info to identify groups where our clients have left, leaving only our own numbers behind. That way, we could exclude or archive these groups.

Pedro Mussi2 months ago
1
In Progress

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 Holidays2 months ago
Rejected

Slack integration

Can you integrate with Slack similar to how you do it for Whatsapp?

Elad Safdieh2 months ago
Rejected

Salesforce integration

Please add a native Salesforce integration with Periskope. We will bei migrating to Salesforce by Feb 2027

Elad Safdieh2 months ago
Rejected

Audit/View Access

Need another view access that can be used for audit purposes by the quality team or by internal data time for creating reports. I want restrictive access where they cannot send messages to the customers.

Shilpi Mishra2 months ago
Completed

Ticket symbol in chat window need to disable for closed chats

for the all chat window there is a ticket symbol displayed below profile photo this symbol should be only visible for open tickets if ticket is closed ticket symbol should be removed so we can get to know this person has one open ticket.

nikhil2 months ago
1
In Progress

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 Mohanty2 months ago
In Progress

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 Senwal2 months ago
1
Rejected

Flagging or Reminder for New Chat Limit

With the limitation of New Chat initiated, for our operational flow where we need to initiate on new chat to follow up for schedule/visitation. There is need some assistance when our new initiated chat almost hit the limit so our phone/number doesn’t get suspended where it will affect our operational

alvin.rozaan2 months ago