The m3sh platform underpins and drives m3ter’s interoperability and automation capabilities, encompassing Events and Notifications, Integrations, Workflows, and Apps, such as the Salesforce Managed Package and soon the NetSuite SuiteApp. All m3ter customers have access to m3sh, offering you a generalized plug-and-play capability with the systems making up your quote-to-cash stack. In this way, m3sh facilitates and unlocks the full power of m3ter for fastest time-to-market implementation of usage-based and hybrid pricing and billing.This section introduces m3sh, gives an overview of it’s key design principles, and reviews some common use cases:
If you have m3sh Workflows set up for your Organization, further topics in this section offer guidance on understanding m3sh Workflows and how to review and manage them:
Note: m3sh in Preview Release! Please note that m3sh is currently available in Preview release version. See Feature Release Stages for Preview release definition.
From the outset, a core objective was for the m3sh platform to extend and strengthen the value proposition of m3ter:
Can be directly hooked into m3ter configuration and functions to complement and strengthen the platform’s capacity to address and fulfill evolving operational billing and analytical needs.
m3sh triggers for automated update and management of key billing entities in response to defined end-customer account events, such as balance depletion or contract expiry.
For this use case, m3sh mediates and orchestrates data flows between the customer platform, Salesforce, m3ter, AWS, and NetSuite to implement multi-endpoint invoicing with enrichment and alerting:
For this use case, m3sh allows you to consolidate usage data and/or contract data from different CRMs - Salesforce and HubSpot - and from your customer platforms to enable centralized metering and rating for multiple products:
Automated Plan and Contract Management with m3sh Triggers
For this type of use case, m3sh triggers are set up to automate actions like plan switching, balance resets, and custom field updates in response to events such as balance depletion, contract expiry, or imposed usage limits: