Date | Topic | Details | POD | Effective Date |
March 12, 2024 | SOP for activating as KLA | SOP: Link 1. Website is functional & all policies updated: Process: Agent proceeds ahead by granting API keys if the account is GTG for activation 2. Website is not functional or policies missing: Scenario: Ask the merchant on estimated ETA to get the website details updated. 2.1. If the ETA is less than or equal to 7 days Approach: Agent to raise NC & ask the merchant to update the website. 2.2. If the ETA is greater than 7 days Approach: Agents to follow the approach of activating the merchant as a KLA by taking merchant’s consent(i.e, activate the account by not granting the API keys) as per the process. | All Pre Onboarding | March 12, 2024 |
March 12, 2024 | Disabling/ enabling of the Payment Link SMS/Email at MID level | SOP : Link | SRF | March 12, 2024 |
March 12, 2024 | Pricing plan attachment changes | We have revamped the process of sending the plan details to the banking ops team. Earlier we were attaching the screenshots in the banking ops child ticket and sent the child ticket to bankingops. Going forward the SPR, SRF, and SRT agents will attach the pdf in the ticket. There is a onetime configuration that has to be made by the agents before downloading the plan. Page layout should be changed to Landscape. Paper Size should be set to A0 Background graphics should be checked. Once the agents click on save the plan will be downloaded. | SPR, SRF, and SRT | March 12, 2024 |
March 12, 2024 | Reopening FinOps child ticket - Updated process | We have made changes in the flow where if the Finops ticket is in WOC the CS agents has to add the required details in a private note and change the ticket status to pending with finops. This will reopen the existing finops ticket instead of creating a new ticket | BSO | March 12, 2024 |
12 March 2024 Print
Modified on: Tue, 12 Mar, 2024 at 7:22 PM