Mobile navbar hamburger

Payments are an important part of the day-to-day of many industries like financial services, healthcare, gaming, real estate, e-commerce, and marketplaces to name a few. For the customers they serve, payments is a delicate aspect of their experience.

Even with the best systems, things can still go wrong. Issues like payment delays or missing funds can quickly lead to customer frustration and distrust. When this happens, providing excellent customer service makes all the difference. A great customer service team responds to complaints quickly while having all the information needed to resolve issues effectively.

In this article, you'll learn how some of our customers use Blnk Finance to empower their customer service teams to deliver delightful experiences to their users.

Example scenario

Let's imagine we have a customer named Praise asking our e-commerce app, AcmePay, why his wallet has not yet been updated after funding it. Note: AcmePay uses Blnk Finance to manage their financial data.

Step 1: Onboard the CX team

First, you need to have a Blnk Cloud organization account. If you don't have one, sign up and connect your financial data from your Blnk Core. This automatically streams all your customers' data into your Cloud workspace.

Next, we'll invite all customer support team members to our workspace and assign them the Operator role.

Blnk Cloud: Invite team members to workspace

The Operator role allows team members to view all financial data and perform actions on them like refunds, committing/voiding transactions, flagging transactions, etc.

Step 2: Responding to the customer's request

In our scenario, the CX manager will search for the customer's identity via email or name, and find the balances connected to him.

An identity details page.
Blnk Cloud: View details of customers' identities and their connected balances

Next, they'll click to view the balance details to see its transaction history. This is to determine if the transaction exists in the ledger.

A balance details page showing pending transaction amounts and transaction history
Blnk Cloud: View details of a customer's balance and transaction history

Our dashboard shows that Praise has a transaction of $2,000 pending inflight, i.e., there is an expected deposit of $2,000 but it hasn't been applied to his balance yet. This may be due to a payment that eventually failed or Blnk has not yet been notified of a successful payment.

To confirm this, the CX manager logs into Stripe to confirm the status of the payment on Stripe. There are 3 possibilities:

  1. The payment was successful on Stripe, but wasn't updated on Blnk.
  2. The payment failed on Stripe, but wasn't updated on Blnk.
  3. The payment is still being processed.

At this point, the CX manager can now update the customer with the latest status and next steps.

If the payment is successful, the customer is informed that their wallet will be updated promptly. If it fails, they are notified that the payment failed and a refund will be processed within a few days. If it’s still processing, they are asked to remain patient as the payment is being finalized.

Step 3: Updating the customer's balance

Finally, based on result in step 2, the CX manager can perform some actions to update the ledger.

I. Successful payment; not yet updated on Blnk

If the payment was successful on Stripe, they navigate to the transaction details and commit the inflight transaction. This lets Blnk know that the transaction has been completed and the balances of the customer should be updated.

A confirmation modal asking the user if they'd like to commit an inflight transaction.
Blnk Cloud: Commit an inflight transaction to apply it to its balances

Once committed, the customer's balance in the ledger gets updated accurately and they're able to make purchases from their wallet.

A balance details page showing its updated balance and its inflight history
Blnk Cloud: The balance is now updated to $2,000.00

II. Failed payment; not yet updated on Blnk

If the payment failed on Stripe, they void the inflight transaction instead. This cancels the transaction in the ledger letting Blnk know that the transaction failed.

A confirmation modal asking the user if they'd like to void an inflight transaction.
Blnk Cloud: Void an inflight transaction if payment fails

III. Payment doesn't exist in Blnk

In the rare case where a payment was successful in Stripe, but doesn't exist in Blnk, the CX manager can create a transaction record to correct this oversight in the ledger.

Blnk Cloud: Create new transaction records to correct oversights

Conclusion

There are several other kinds of customer service scenarios that can be easily handled through Blnk Cloud. For example, CX teams can view the anomaly history of a particular user to determine if their complaint is genuine. They can refund transactions, manually flag transactions, view a map of a customer's interaction within their application and so much more.

With Blnk Cloud, your CX team gets the tools they need to deliver fast, efficient customer service to your users while ensuring seamless collaboration with the rest of the organization.

If you'd like to see how Blnk Cloud can work for your organization, please reach out to us.