PBX Programming

Recognise callers from CRM data and route them to their account manager, the last person they spoke to or the right team, or send an SMS on a keypress.

PBX Programming: call flows that know who is calling and connect them to the right person

When a customer has to sit through the welcome menu, press keys, wait in a queue and finally reach someone who has never dealt with them, both time and goodwill are lost. MyVoipCRM PBX Programming lets the CRM decide where an incoming call should go. On every call the PBX asks the CRM "where should I put this caller?"; the CRM recognises the contact, knows their account manager, the last person they spoke to and their contact category, and routes the call accordingly.

The result: customers reach their assigned account manager, the field technician handling their job or the person they last spoke to, and VIP customers get priority treatment. Smarter call routing, faster service and happier customers in a single module.

Caller recognition and routing rules

  • Recognise the caller by number: A caller who is in the CRM is connected to the staff member named on their contact card, a voice menu, a queue or the staff member on duty, with an optional audio file played while connecting.
  • Connect to the last person they spoke to: The caller goes straight to whoever they spoke to within the period you choose (from the last 12 hours up to several days), ending the "I'd like the person I just spoke to" problem.
  • Route by contact category: Set rules such as VIP customers to the front desk and corporate customers to accounts; destinations are defined on each category's own card.
  • Recognise your own staff: If the caller is one of your employees, for example a field team member, they are connected to the relevant destination.
  • Recognise by keyed-in number: Someone calling from a withheld or different number is asked to key in their phone number, and the contact is found from that.
  • Greet callers by name: If your PBX has text-to-speech (TTS), the caller is greeted by name.

Keypad options, messages and fallback destinations

  • Route by predefined keypress: Play the caller a keypad prompt and give each key a destination: a queue, a voice menu, the assigned staff member, or an SMS or WhatsApp message.
  • SMS and WhatsApp on a keypress: In a "press 3 for directions" flow, the caller receives the address and a map link by SMS without tying up any staff.
  • PBX message templates: Messages can go to the contact or to staff; for example, details of a customer calling the emergency line can be sent to the on-call person by SMS. WhatsApp templates must be approved by Meta.
  • Advanced multi-level menu: Build voice menus with sub-menus that branch according to who is calling.
  • Default and fallback destinations: If no rule matches, the call goes to the default destination; if the CRM is briefly unreachable, the PBX sends the call to the fallback destination, so no call is dropped.

How it works

  • 1. Connect the PBX: Enable the PBX Programming API module on your Verimor Cloud PBX account and enter the service address shown in the CRM into the PBX settings.
  • 2. Fallback destination: Choose where calls should go if the CRM cannot be reached, such as the welcome menu.
  • 3. Choose the number: Select the PBX number you want to programme in the CRM, then set that number's inbound destination to the PBX Programming API in the PBX panel.
  • 4. Rules: Switch on the recognition, category, last-contact and keypress rules and save; the PBX applies them from the next call onwards.

Who it is for

  • Businesses with account managers: Sales and account teams who want every customer to reach their own contact directly.
  • Clinics and service businesses: Patients or customers return to the adviser they last spoke to, and directions or booking details are sent on a keypress.
  • Companies with field teams: Fast connection to the technician on the job or to staff out in the field.
  • VIP service providers: Teams who want dedicated queues and priority greetings by customer category.

Frequently asked questions

  • Which phone systems does it work with? MyVoipCRM integrates with Verimor Cloud PBX, NetGSM Netsantral and Grandstream UCM, and the screens shown in the menu depend on what the connected PBX supports. Caller-aware PBX programming works through Verimor's PBX Programming API module. See all options on the integrations page.
  • Are calls lost if the CRM cannot be reached? No. The fallback destination you set during set-up decides where calls go when the CRM is temporarily unreachable; we strongly recommend filling it in.
  • How are business hours handled? The PBX can run the business-hours plan: only the in-hours destination is pointed at the PBX Programming API, while out-of-hours and holiday calls go to their own destinations on the PBX.
  • Can I change queue and menu settings from the CRM? Queue members and order, mobile ring group members, extensions' outbound numbers, audio files, the blacklist and PBX programming are managed in the CRM. Extension and queue settings, ring groups, menus and inbound rules are edited in the PBX panel and displayed in the CRM.
  • Queue, ring group or mobile ring group: which should I use? A queue suits busy lines where callers accept waiting; a ring group suits cases where any one of a few people can answer; a mobile ring group rings mobiles for on-call or field teams when nobody is in the office.