Think of progressive rates as build steps on a stair. But keep in mind that in a2billing, you can define a maximum of 4 steps: Step A, B and C and the regulat flat rate. After running the last step, the rate will default to the regular flat rate. The following drawing shows you some possibilities that you can do:
One Step:
Code:
____...Flat...
_..A..__/
_..A..__
\____...Flat...
Two steps:
Code:
____...Flat...
_..B..__/
_..A..__/
_..B..__
_..A..__/ \
\____...Flat...
_..A..__
\_..B..__
\___...Flat...
___...Flat...
_..A..__ /___...Flat...
\_..B..__/
\___...Flat...
These examples show only 1 or 2 steps. Feel free to experiment the 3 steps progressive billing. Here, you can see that I have not shown any situation where the rate in step B is the same as the flat rate (the regular rateinitial). That's because it would be wiser in such situation to use only step A after which the rateinitial will be used.
Quote:
STEPCHARGE
Like a Connection charge when enter this step
CHARGE
minuterate for this step
TIMECHARGE
How long this Step should before entering next
BILLING BLOCK
Increment
Have I got is right?
Yes you go it right.
If you want to ignore a block, simply remove its content. A2Billing will then use 0 by default.
Important: Use the block in the correct order. You can only do one of the following:
- Standard flat rate alone (no step A, no Step B, no Step C). This is what most users are doing.
- Standard flat rate & Step A only (no Step B, no Step C)
- Standard flat rate & Step A & Step B only (no Step C)
- Standard flat rate & Step A & Step B & Step C
Note: The rates of the steps does now have to follow any pattern. Each step can go up and down an last a long as you want.
Does that help?
Cheers
A. Siby