The Rate alerts tool allows you to check and analyse rates increase for destinations you are currently sending traffic to.
There are 3 stages to the report:
1. First, the system just gets all the rates that changed over a given period. The interval and vendor Rate plans are set in the
Rate alert report floating window:
In this window you also set other options which will be used during the 2nd and 3rd stages (see 2. and 3. below). The Rate alert table that is open will give you results after implementing the 2nd stage, but you may view just the pure vendor rates that were changed in the
View rate changes floating table:
The procedure is 100% same as in the VendRate range table, however, the results are written to a separate tmp table in the DB so that you may use them multiple times later on (getting changed rates may take several minutes for all Rate plans, so we kind of cache the results to reuse them).
2. Second, we match the areas. This is done automatically if you start with stage 1, but you may also change the matching later on using cached rate changes via the
Match button.
We need to set customer code decks here because codes can be significantly different by code decks, we can only match vendor areas to each area in each code deck separately. Usually, if you know that you have only 2 main code decks, you may just choose them ignoring all others (test decks, etc.).
The table after stage 2 will look like this:
The matching is done separately for 2 decks. How come we have so many rows for a Gldline deck? This is due to code mismatch between vendor and customer rates. The line with no vendor area or rate plan is there to show that there are extra codes in Brazil-Cell area that are not matched with changed vendor codes.
We also have stats areas to the right matched by names to code deck areas. If names are same or very close - the matching will be perfect, if not - we try to do our best to match areas by names. If this does not work in some weird cases - you may manually choose a different area.
Another matching here is Vendor Rate plan -> Vendor in stats. This is done either by name (it should match completely), or by choosing a proper stats object in the Rate plan table per each plan.
3. Third, we get the stats. At first, at the Area->Vendor level.
Min. minutes allows you to cut off all the areas with no or very little traffic.
Then you may investigate each area individually, or just press the
Expand all button to fetch all Customer->Area->Vendor stats.
You may change the
Alert margin,% on the fly, any rates that will have a lower margin will have a red tag on the right showing how short the actual margin is from the margin you need.
Customers in stats are matched to customer Rate plans in the same way as vendors.
Note that 2 customers are under the Gldline code deck, as their Rate plans belong to this deck, and one customer is under another deck.
The easiest way to investigate large tables with lots of changes would be, probably, by filtering by
Margin alert ::<0 (filter at 2nd level), so you will only have the customers with alerts. You may also export any table as is to excel now, using the export in right-click menu, and then pressing the
Download Excel file.