Learn about product rate tables and recurring actions in TRACT


Billing and revenue management platform for XaaS and IoT

4.0/5 (1 review)

Learn about product rate tables and recurring actions in TRACT

Video Transcript

Speakers in this video: Jimmy (GetApp) and Dan (TRACT)

Dan: And I'm actually using some rate tables for this, so if I look at specific rate tables, so again I get 30 cups of Coffee per month as my allowance and then going in to that I'm going to use specific types of whiteners or sweeteners syrups as well as different types of coffee as well and with those come different types of rates. So maybe the regular blend is a given, the regular type of coffee is included but maybe if I want that (00:00:39) then I'm going to pay 3 cents extra each time.

And maybe if I want to add some type of syrup, you see here for caramel we have the five cent charge, so you could see as we're looking in and we're looking at the sweeteners here, we're looking at various rate tables you start to formulate some ideas in your head of all the different types of ways and the flexibilities that you have and how you want to charge your customers. So again the idea is not being held hostage by your billing system, by the limitations of it, the idea is however you can think up any type of way that you want to measure and bill your customers you should be able to do that and that shouldn't be based on the limitations of your current billing system.

So with Tract, lots of different flexibilities in how you can actually have this setup and it can get quite complex. And actually if we go back into this recurring charge and again if we go into the allowance, again just to show you some of the actions, there could be several actions in a framework, so for that monthly allowance we were looking at, again we can set some actions up so around threshold met. So maybe I want to send out when we have one set up here and email send out to the account when 90% of their monthly allowance is used up. And you could set up as many of these as you want, so 75% and again all the different types of email templates that you can have set up and again set up some sort of API workflow maybe when the account hits 90% you also want to set up a task or an opportunity that is automatically sent out to sales force to your CSR to follow and just give that customer a call.

So again a lot of flexibilities just here as were looking of setting up various rules for this product. Again we have the ability for related products as well, we get a parent-child relationships products as well as recommended products, so it's recommended when someone purchases this coffee club membership maybe they also want to buy custom logo mug or travel mug as well. And again, we have an associated agreement with this product as well and again some various actions that could be set up, we have a new member welcome action set up here, so everytime coffee club membership is actually sold, maybe you want to send out a welcome email or something like that.

So again you start thinking of different ideas and different actions and rules that you could set up with just your own particular use cases as well. You see we have a couple accounts associated, couple accounts that have these products in place today, so if we check out Carl, it's our first account that we ever signed up here. We're looking at Carl, his account detail page. This is a customer of mine, this is Carl and in this account details page this is all something that can be pushed out to API to sales force or any CRM. The great part of how Tract interact with the CRM is that it actually populates within the window of the CRM. The CRM in self is in storing it any of this data, any of the AR data, so Icould see the debit adjustments, credit adjustments, invoices, payments and so forth.

All these information about this client whenever you call up this account within your CRM a window will also populate with all these information, populating via API into the CRM, so you know if you're using something like sales force you're not going to get dinged for using their storage because you're not storing anything within sales force, it's all being populated within sales force via API, as well as you're not being dinged for using their API's because you're using go tranverse API as well. A lot of advantages there. So we're looking at the account details page, we can see a lot of information about Carl's account here, what his invoice type is, his currency, his payment terms, this can also be adjusted in his file as well, as well as his current balance, any pending charges.