A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | Zerodha CEO Nithin Kamath's Swift Action Over Compliance Issue Impresses Customer | Get Indian Desi Latest Political News & Updates in USA. Get domestic, republic government updates - NRI Page
Edit

Zerodha CEO Nithin Kamath's Swift Action Over Compliance Issue Impresses Customer

Zerodha CEO Nithin Kamath's Swift Action Over Compliance Issue Impresses Customer

Zerodha CEO Nithin Kamath’s swift response to a customer’s compliance concern has earned widespread praise, demonstrating how the brokerage firm’s proactive customer service strategy drives positive outcomes. The incident unfolded when Bengaluru-based product manager Sachin Jha was compelled to close his Zerodha account after his wife joined a global investment bank. The bank classified Zerodha as an “untrusted” platform due to its lack of physical branches, aligning it with digital-only entities rather than established financial institutions like Kotak Mahindra Bank or ICICI Bank. Jha, who was disappointed with the situation, decided to write a final email to Nithin Kamath explaining the reason behind his account closure. He didn’t expect a response but chose to voice his concern nonetheless. To his surprise, Kamath replied within just ten minutes, leaving Jha astonished.
 

In a LinkedIn post recounting the experience, Jha revealed how Zerodha’s CEO personally addressed the issue. Kamath acknowledged the compliance concern and assured Jha that Zerodha was actively working to resolve the problem. Kamath’s team promptly investigated the situation and informed Jha about their efforts to build stronger relationships with institutional investors. Additionally, they reached out to Jha for assistance in establishing a compliance partnership with his wife’s employer to directly address the bank’s concerns. In his post, Jha described the experience as a “$2 billion lesson in customer obsession.” He highlighted how Zerodha’s team not only admitted the compliance gap but also transparently outlined their action plan. Jha shared that Zerodha was actively fixing the issue with banks and proactively working on building institutional trust to prevent similar situations in the future. Despite Zerodha’s prompt action and willingness to address the compliance concern, Jha ultimately proceeded to close his account. However, he acknowledged that Kamath’s response and the company’s efforts had deeply impressed him, earning his trust for life. Jha praised Zerodha’s proactive and customer-focused approach, stating that the experience left a lasting impression on him.
 

The incident sheds light on Zerodha’s strategic focus on customer engagement and transparency, even in situations where outcomes may not be immediately favorable. By addressing Jha’s concerns directly and committing to improving institutional trust, Kamath showcased how customer-centric leadership can significantly impact brand perception. Kamath has publicly acknowledged that while digital platforms like Zerodha offer seamless experiences for trading and investments, the absence of physical branches remains a limitation when it comes to gaining trust from large institutions and certain financial entities. Kamath believes that physical branches are still essential for building deeper customer relationships, especially for financial guidance, lending services, and institutional collaborations. Despite this challenge, Kamath clarified that Zerodha currently has no plans to pursue a banking licence. He cited regulatory complexities and potential risks as major reasons for the company's decision to focus on strengthening its existing services rather than transitioning into full-fledged banking operations.
 

Instead, Zerodha is prioritizing growth through strategic partnerships and collaborations that enhance trust among institutional clients. By focusing on improving compliance procedures and forging strong alliances, Zerodha aims to address concerns raised by organizations hesitant to engage with digital-only platforms. The proactive response by Kamath and his team has underscored Zerodha’s commitment to customer satisfaction and adaptability. While Jha’s account closure was unavoidable, Zerodha’s swift action and transparent communication won admiration from the fintech community and reinforced the company’s reputation for responsive customer service. The incident highlights how customer trust can be earned even in challenging situations when businesses demonstrate empathy, accountability, and a genuine willingness to resolve concerns. Kamath’s quick response serves as a valuable lesson in leadership, proving that customer loyalty is often built through meaningful engagement rather than immediate results.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD