Origin-based call rating
In order to adjust to market conditions, telecom vendors in many countries have started charging calls to a given destination differently, depending on where each call comes from. For example, calls to Turkey might cost $0.10/min from Canada, $0.20/min from Morocco, and $0.40/min from Algeria.
With MR119, PortaSwitch supports tariffs that can include multiple pricing options for each destination based on the country or network from which a call originates (determined by the caller’s number – CLI). Such tariffs offer standard prices per destination, with the possibility to either add a surcharge to the standard price or to replace it with a new price if the caller’s number matches a specific rate code (e.g., country code). This feature allows the system to accurately calculate costs for calls routed through vendors using origin-based pricing, so that PortaSwitch properly utilizes the least-cost-routing capabilities and your calculations of vendor cost match reality, allowing you to properly check and reconcile vendor invoices. Optionally, you can also implement this type of charging for your customers (e.g., large enterprises or call centers with end users in various countries) and resellers to ensure there is no revenue leakage.
Example
A service provider called Owl Telecom charges $0.15/min for calls to +90530 (Turkey-Mobile Turkcell). To maintain profitability when sending calls to Turkey via a vendor that uses origin-based pricing, Owl Telecom also adds surcharges on top of the standard customer price, such as $0.25 for calls from +212 (Morocco) and $0.45 for calls from +213 (Algeria).
If a call is made to +905303334567 (Turkey-Mobile Turkcell) from +2132221234 (Algeria), the per-minute customer price is $0.60 ($0.15 standard rate + $0.45 surcharge). If the call originates from any region for which no surcharges are defined in the customer tariff, such as a call from +12045557890 (Canada), the price remains $0.15/min.
What’s improved?
Maintain profitability
Ensure that costs are covered while working with vendors that apply additional charges based on a call’s origin.
Find more details here.
Simplified Call Control API for building custom voice applications
When building voice applications, developers can now create custom logic for playing prompts and automatically stopping them when a DTMF code is dialed, collecting DTMF codes, and performing further actions (such as redirecting calls) using just two new Call Control API methods:
- CallControl/play handles both playing and stopping prompts, replacing the need for two separate methods. This method now also supports WAV and MP3 formats in addition to AU.
- CallControl/get_input manages the start and stop of DTMF input detection, which also previously required two separate methods.
Example
A developer creates an auto-dialer for a hospital to remind patients of their appointments. When patients answer the call, they hear a prompt: “Press 1 to confirm, 2 to reschedule, or 3 to cancel.” If a patient presses “1” before hearing all the options, PortaSwitch notifies the auto-dialer application that the prompt was interrupted and a DTMF code was received. The application then instructs PortaSwitch to play a follow-up prompt (“Thank you for confirming your appointment!”) and then end the call.
What’s improved?
Easier development
Save time and resources when building custom voice applications.
Find more details here.
Transferring calls directly to a call queue
With MR119, call center agents and supervisors can transfer external callers directly to a call queue, for example, when moving a call from one queue to another. Previously, calls could only be transferred to a specific hunt group – bypassing the queue – or to an auto-attendant, requiring callers to enter a DTMF code to join the queue. Now, there’s no need for additional setups like an auto-attendant, as calls can be transferred directly into the queue from an IP phone or an external application.
Example
ABC Company runs a call center for its support departments: First Line Support and Second Line Support. John, a supervisor, is overseeing the call center performance. A client contacts the call center, selects “First Line Support” in the initial auto-attendant menu, and is placed tenth in the corresponding queue. John notices in his web application that this call has already been waiting in the First Line Support queue for 15 minutes. Since only one caller is waiting in the Second Line Support queue, John decides to transfer the client there, reducing their wait time.
What’s improved?
Better customer service
Call centers can improve customer satisfaction and reduce the number of abandoned calls.
Find more details here.
Easily trace payment allocation to invoices
Payment amounts can be distributed among all unpaid invoices, starting from the oldest. It’s now much easier for admins to trace how each payment was allocated, including which invoices it covered and whether any amount was overpaid and assigned to customer’s unallocated payments.
In the case of a financial dispute, an admin simply needs to open the list of the customer’s xDRs, filter payments, and click Allocation per invoice for the relevant payment. A dialog that opens shows a detailed breakdown of how the payment was distributed across invoices.
Additionally, admins can quickly check which payments covered a specific invoice. When the admin hovers over the “Paid amount” for an invoice in the list, a tooltip displays the allocated amounts along with the payment dates. Similarly, the unallocated payments setting now includes a tooltip listing all relevant payments.
Example
Owl Telecom’s customer, ABC Company, has three overdue invoices:
- October: $1,000
- November: $1,000
- December: $1,000
The customer’s services are suspended, and all three invoices remain unpaid. When ABC Company makes a payment of $2,500, the system applies it to the October and November invoices and partially covers the December invoice.
ABC Company contacts Owl Telecom to inquire why their services are still suspended despite the payment. Owl Telecom’s admin can quickly trace the payment allocation and explain to the customer how the amount was applied.
What’s improved?
Easier payment management
Admins save time in resolving payment-related questions.
Find more details here.
Track active subscriptions with zero charges
Subscriptions with a 100% discount, such as promotional offers, can now be easily tracked. When a customer has such a subscription, PortaBilling generates a zero-charge xDR. This record appears on customer invoices, showing that the service is active and provided for free. Additionally, this data can help you analyze how many customers are using services at no charge.
Example
Owl Telecom offers new customers three months of free call recording with their service package. After this period, the service will cost $9.99 per month. During the promotional period, invoices will display “Call recording” with a $0 charge, clearly showing the service is active but free.
What’s improved?
Cost control
Monitor the usage of free services and assess their financial impact.
Improved customer experience
Customers stay informed about their free service period.
Find more details here.
