-
Notifications
You must be signed in to change notification settings - Fork 7
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
Contact Reloadly Leadership #118
Comments
/start |
Prospected the list of key stakeholders at Reloadly Custom-Table-Default-View-export-1737750279361.csv Launched a mini campaign on them: Email 1Hi {{first_name}}, I’m reaching out to you as the {{Title}} of Reloadly to address some concerns regarding poor service and inadequate support behavior. At Ubiquity, we are building infrastructure for devpools to streamline developers’ motivation, and having a reliable partner for card minting is critical for us. Recently, we encountered an issue with your solution that has left us on the verge of considering alternative providers. Specifically, we had pending orders in your system, and unfortunately, your support team shut us off without resolution. I would appreciate the opportunity to work through this matter with you. If you’re willing to address it, I’ll gladly share the details of the issue along with screenshots of our interactions with your support team. Looking forward to your response. Email 2{{first_name}}, hi I'd like to expand on the context of that situation - One of my colleagues attempted to manually place an order but encountered an error. Upon reaching out to your support team, they were informed that the card in question was unavailable. However, both your API and dashboard showed it as available at the time. To provide clarity, my colleague shared screenshots confirming the card’s availability. In response, your support team proceeded to make the card unavailable on the spot without offering a resolution or explanation. This not only disrupted our operations but also raised serious concerns about the reliability and professionalism of your support processes. Given how critical your service is to our business, this experience has left us questioning whether we can continue relying on your solution. I hope you understand the gravity of the situation and would like to hear how you plan to address it. Let me know how we can work together to resolve this matter and prevent similar issues in the future. Email 3Dear {{first_name}}, I’m writing again to follow up on the concerns I raised regarding the issues we’ve encountered with your service and support team. As mentioned earlier, this matter has significantly impacted our operations, and we’re awaiting a response from your side. To reiterate, we experienced a discrepancy where your API and dashboard indicated availability for a card, but your support team claimed otherwise and subsequently made the card unavailable without explanation. This behavior is both unprofessional and unacceptable for a partnership of this nature. I look forward to hearing from you soon. Email 4Hi, I am disappointed not to have received any response to my previous emails regarding the issues with your service and support team. This delay in addressing a critical matter is unacceptable and does not reflect the level of professionalism we expected when partnering with your company. To remind you, the issue arose when your system indicated card availability while your support team claimed otherwise and proceeded to make the card unavailable without offering a resolution. This incident has disrupted our business operations and shaken our confidence in your reliability as a partner. We need an immediate explanation and a clear action plan to resolve this matter. Failure to respond promptly will force us to escalate the situation internally and explore alternative solutions. I expect to hear back from you within 24 hours. Email 5{{first_name}}, This is my final attempt to get a response regarding the unacceptable service and support issues we’ve encountered with your company. Your continued silence is unprofessional and signals a lack of commitment to resolving the problems caused by your team. To remind you, your support team mishandled a situation involving card availability, ignored clear evidence from our side, and made the card unavailable on the spot, leaving us without a resolution. This has caused significant disruption to our operations and left us with no confidence in your platform. If I do not receive a satisfactory response and resolution within the next 12 hours, we will take the necessary steps to terminate our use of your services and transition to another provider. Additionally, I will ensure that this experience is shared with others in the industry as a cautionary tale. This is your final opportunity to retain us as a client. I hope you take it seriously. |
I actually already assigned you, you can see in the timeline just before you wrote the command. |
okay thank you1 |
Here are the replies from Procurement manager Dren Lubovci and a thread where their Partnership manager Tulita forwarded that to their support team and they doubt that this email is real: Reply from DrenHi Alex For any issues. My Whatsapp: http://wa.me/447446940651 I am here for you 24 hours a day Can you share the txn ids that are pending for us to resolve for you. Kind Regards, Reply from Support teamHello Team, Kindly share the issue you experienced or transaction IDs with the error you encountered for us to investigate. We look forward to your feedback. Regards, Olabode On Friday, 24 January 2025, 22:46:56 -0500, <[email protected]> wrote: |
@0x4007 please accept i'd suggest i will share information from ubiquity/pay.ubq.fi#369 (comment) to their support team in a reply and you will assign someone or will take it from here in telegram with Dren. |
|
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Task | 1 | 100 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|
[ 21.84 WXDAI ]
@0x4007
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Specification | 1 | 21.84 |
Issue | Comment | 1 | 0 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|---|---|---|---|
_Originally posted by @0x4007 in [#369](https://github.com/ubiqu… | 5.46content: content: p: score: 0 elementCount: 1 em: score: 0 elementCount: 1 a: score: 5 elementCount: 1 result: 5 regex: wordCount: 6 wordValue: 0.1 result: 0.46 | 1 | 4 | 21.84 |
I actually already assigned you, you can see in the timeline jus… | 1.11content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 17 wordValue: 0.1 result: 1.11 | 0 | 4 | 0 |
Originally posted by @0x4007 in #369
The text was updated successfully, but these errors were encountered: