Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhanced Support Ticket Management for Shared Accounts #2132

Open
ashishsaretia opened this issue Jan 11, 2025 · 0 comments
Open

Enhanced Support Ticket Management for Shared Accounts #2132

ashishsaretia opened this issue Jan 11, 2025 · 0 comments

Comments

@ashishsaretia
Copy link

Is your feature request related to a problem? Please describe.

We are using a shared business account on Frappe Cloud -> Frappe Helpdesk (support.frappe.io) to raise support tickets for our team. Currently, all tickets are raised using a common email ID, which is internally distributed among our team members.

This setup presents the following challenges:

  1. Lack of Individual Identification: As a manager, when I access the support portal, I am unable to identify which team member has raised a particular ticket. This makes it difficult to manage and track accountability.
  2. Reply Notifications Not Distributed: Reply notifications are sent to the common email ID, meaning individual team members do not receive updates directly. They need to manually check the portal for updates, which leads to delays and inefficiencies.

Describe the solution you'd like

  • Add a "Raised By" Field: Allow team members to add their name or an identifier while raising a ticket. This field can be displayed on the support portal for easy tracking.

  • Enable Notification Forwarding: Introduce a feature to forward reply notifications to a specified email address (e.g., the email of the team member who raised the ticket) or allow adding CC email IDs for better communication while raising the tickets.

Describe the alternatives you've considered

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant