Recent searches
No recent searches

Maximiliano Cooper
Joined Dec 13, 2022
·
Last activity Nov 19, 2024
I've been working in technology and eCommerce for the past 15 years and as a Zendesk Tech Alliance partner for the past 5 with our Mercado Libre channel integration. https://www.linkedin.com/in/maxicooper/
Following
0
Followers
0
Total activity
30
Votes
5
Subscriptions
18
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Maximiliano Cooper
Maximiliano Cooper created a post,
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)
I would like different locations from a private app to be able to communicate with each other, so that they can share data and avoid unnecessary external API calls.
What problem do you see this solving? (1-2 sentences)
In our specific use case this would be used to preload heavy data needed for a custom app in background so that when the admin user access the app all the data is there and we don't have a minute or two of lag until all the data gets there, significantly improving the user experience. But this could be used for all sorts of apps, sending ticket data to a user_sidebar, or other way round and so forth.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)
Every single day since this private app is essential in our Zendesk administration.
Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)
No workaround so far, but open to ideas :)
What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)
Treat all locations from a private app within a single context so that we can share data between them.
Posted Nov 19, 2024 · Maximiliano Cooper
0
Followers
1
Vote
1
Comment
Maximiliano Cooper commented,
Kudos Zendesk team on this great feature! We would love to be able to use it within our workflows, with triggers, automations and macros, is that something you are considering to add?
View comment · Posted May 31, 2024 · Maximiliano Cooper
0
Followers
4
Votes
0
Comments
Maximiliano Cooper commented,
Hey Zendesk team. Having your pricing model tied to public anonymous interactions is quite risky. For eg. it would be really easy to build a script and start thousands of trivial conversations to my competition and therefore “send” them a few hundred thousands dollars in Zendesk bills to try to put them out of business. Legal concerns apart, as shown in the previous comments, this script wouldn't even need to really say the problem was resolved, just by starting and abandoning a conversation you produce a $1.5 debt to a third party.
Malicious or not, public traffic based pricing tiering has it's caveats. What are your thoughts on this?
View comment · Posted May 15, 2024 · Maximiliano Cooper
0
Followers
13
Votes
0
Comments
Maximiliano Cooper commented,
Which is a very US/Europe-centric view, isn't it Brandon (729) ?
View comment · Posted Apr 23, 2024 · Maximiliano Cooper
0
Followers
1
Vote
0
Comments
Maximiliano Cooper commented,
Hi. Is there going to be a panel where we can review each conversation automatically resolved by the agent?
View comment · Posted Apr 17, 2024 · Maximiliano Cooper
0
Followers
1
Vote
0
Comments
Maximiliano Cooper commented,
Hi. I was told that Meta APIs do include information about where the user is navigating when they
send a Facebook message, Zendesk plans to include this information somehow in the future?
For eg. if a Facebook user is on a specific post and send a message to receive that ticket with the post url as context.
Thanks!
View comment · Posted Sep 20, 2023 · Maximiliano Cooper
0
Followers
1
Vote
0
Comments
Maximiliano Cooper created a post,
Currently if a user sends for the first time an email to the support address, a ticket will be generated under a new user. This user will have the email address unverified, and hence you won't be able to send a NPS survey after closing the case.
Given that one can mark a user's address as verified using the API, it would be great to have an option to mark all incoming email addresses as automatically verified, since almost all incoming tickets are from rightful addresses.
Posted Dec 13, 2022 · Maximiliano Cooper
0
Followers
2
Votes
0
Comments