Jade Global breaks new ground by extending Salesforce Billing to transform customer experiences.

Industry:

Event Management

About the Client

The Knot Worldwide (TKWW) is USA’s leading digital wedding resource offering a seamless, all-in-one planning experience—from finding inspiration and local vendors to creating and managing all guest experiences, wedding registries and more. The trusted brand reaches a majority of engaged couples in the US through the #1 wedding planning website TheKnot.com and #1 iOS and Android mobile app The Knot Wedding Planner, The Knot national wedding magazine, and The Knot book series. Since its inception, The Knot has inspired approximately 25 million couples to plan a wedding that’s uniquely them.

Products & Services

  • Salesforce Billing
  • Experience Cloud

Challenges the company met

  • TKWW needed to integrate with Adyen payment gateway, which was a completely new payment gateway for Salesforce Billing
  • Native Salesforce billing pages were not operational on communities
  • Collecting payments upfront was a major challenge for TKWW. Salesforce Billing does not track payment failures scenarios of unsettled transactions from banks. This means that if the transaction failed to settle, it just showed as successful in Salesforce Billing, but later when the bank settled it shows as failed.
  • Additionally, they wanted customers to be able to login into their portal and make payments for the quotes that were created.

Bringing Salesforce Billing Up to Speed to the Business Needs

TKWW recently launched a new product to engage its proactive global clientele. To streamline and offer a seamless billing experience to their customers, they brought Salesforce CPQ and Billing onboard.

However, their Salesforce billing implementation was marred with complexities, not using native Salesforce billing package and payment gateways. When Jade Global took on the onus to set their Salesforce Billing right, TKWW was already working on a rigid timeline. TKWW had only a month to go live, and their billing cycle was not configured, and they needed Salesforce billing implementation with payment connectors.

Back to Top ↑