This shows you the differences between two versions of the page.
| — |
how_tarriffs_work [2011/04/07 11:39] (current) chris created |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== How Tarriffs Work ====== | ||
| + | |||
| + | Tarriffs are the backbone of any good Telecommunications provider and are another word for "Call Costs". | ||
| + | |||
| + | With the FaktorTel reseller system Tarriffs are set in an easy to use spreadsheet style, where you set the area, the number or prefix and the call cost. | ||
| + | |||
| + | It is important however to understand how the tarriff system actually works so you can effectively create your tarriffs in a very short period of time. | ||
| + | |||
| + | ===== Order of events ===== | ||
| + | |||
| + | <note important>The Tarriffs Order of events is the MOST important thing to understand about how the tarriff system works.</note> | ||
| + | |||
| + | The FaktorTel reseller Tarriff system has 3 distinct levels, these levels allow you to quickly create packages without the need to add 10,000 dialling patterns and codes each time. The levels are: | ||
| + | |||
| + | - User Package (E.g. "My Package") | ||
| + | - Default User Package (E.g. Default-Username) | ||
| + | - Default Package | ||
| + | |||
| + | The reason why these are important is because it is how the system looks through the packages when it is charging your customer for a call. | ||
| + | |||
| + | Lets take this customer tarriffs package called "My Package" for example. You can see it lists all the Australian numbers, and rates beside them: | ||
| + | |||
| + | {{:tarriff_spreadsheet.png|}} | ||
| + | |||
| + | Now, if a customer on this package was to dial **0312345678** the system would do the following: | ||
| + | |||
| + | - Step 1: Check the package "My Package" for the number (or start of the number) 0312345678 | ||
| + | - Step 2: If the number exists (or the start of that number, e.g. 03) then charge the customer 11c | ||
| + | |||
| + | Now, if the customer was to dial **"001144123456789"** which we can see is NOT on the list, this is what would happen: | ||
| + | |||
| + | - Step 1: Check the package "My Package" for the number 001144123456789 | ||
| + | - Step 2: The number or prefix doesn't exist in this package! | ||
| + | - Step 3: The system will now check "Default-Username" (where username is your username, e.g. default-chris.c) | ||
| + | - Step 4: Seeing you have all the international prefixes in your default-username tarriff, the system finds 001144 is England and charges at the England rate. | ||
| + | |||
| + | ===== Why have different levels? ===== | ||
| + | |||
| + | The reason why we have these levels is so that we can upload all of our international rates to a package called "Default-username", now whenever an international rate changes or is varied, we can simply change it on the "default-username" package and it will affect all of our packages. | ||
| + | |||
| + | Secondly, when we want to create a new package we don't have to worry about international rates. We simply enter in the rates that want effective on the package, without the need to enter in any international or special rates, and we're good to go. | ||
| + | |||
| + | ===== What if the rate exists in both packages? ===== | ||
| + | |||
| + | Lets use the **0011441123456789** example. Being a good provider you setup all of your international rates and put them into "Default-Username", now you have a package where you want to charge the customer 5c per minute to call england, but your default-username package has it set to 10c per minute. | ||
| + | |||
| + | This is easily, fixed, because of the order of operations as mentioned at the start, the users package (in this example "My Package") is always checked first. So if we put **001144** as a prefix in "My Package" then this will happen: | ||
| + | |||
| + | - Step 1: Check if 0011441123456789 exists in the package "My Package" | ||
| + | - Step 2: Yes it does exist - Charge the customer 5c | ||
| + | - No more steps, customer is charged. | ||
| + | |||
| + | As you can see, putting in the 001144 prefix overrided what was in the default-username package. | ||
| + | |||
| + | This is what the package / tarriff looks like with the 001144 prefix in it: | ||
| + | |||
| + | {{:international_tarriffs1.png|}} | ||
| + | |||