Fyers Support.

Traders Lounge
1

There is Telegram channel, Phone support and community. At the time of need neither the telegram channel not the community is useful. Can a live chat facility be introduced? That way we will not have to be on call for 30min and can just wait for chat notification.

2

Hi @arindam_ghosh,

We are always available on the community & our customer support is available from 9:00 AM to 11:55 PM. Kindly let us know your concern here, and we will be happy to help you.

With regards to the Live chat support, we are already working on it!

Thanks :slight_smile:

1 Like
3

I was trying to get to the bottom of ticket 694587. It was resolved via call. But chat option would have enabled me to chase this during market hour as I was stuck in office call and could not call earlier. Good to know chat facility will be available in future. Chat will allow asynchronous interaction.

4

The actual problem was as follows.

  1. I had 81 berger paint stock in my holding. I pledged it before. Yesterday I sent the unpledge request. Usually it gets unpledged overnight and is free next morning. So I was expecting unpledged 81 berger paint stock today morning.

  2. However that was not the case. The status was showing unpledge pending. I requested for unpledge again and that went into pending status also.

  3. Also, I had bought 101 berger paint on monday 01/08 and those were in T1. I actually wanted to sq off 101 berger paint share today.

  4. When the sq off order went from my python api, the holding section showed 81 deducted from the pledged pot and remaining from T1 pot.

  5. At that time the unpledged request was still pending.

  6. So I wanted to know why unpledge is taking so long

  7. Will there be a problem due to the sq off request

  8. Finally what will happen due to duplicate unpledge request.

  9. During the Fyers call that I made, the 1st unpedge request started to show as success and I could eventually relax. Also the helpline person said that duplicate unpledge request will not cause any problem.

  10. However why did the unpledge request take longer than usual?

5

Hi @lzMMNwbR8T , do you have a view on above, specifically why unpledge took longer than usual?

6

This is now closed by support satisfactorily.