Notification

Sends an e-mail when the call passes through, with your variables in both the recipient and the text. The call continues on its way in every case.

In brief

How it works

When the call passes through, the {{variable}} entries in the recipient and the text are replaced by their value, then the e-mail is sent.

If, after replacement, the recipient is empty, no e-mail is sent. The call still continues to the module's output: this is one of two modules that never end the call for their own reason, along with Record. Nothing is flagged on screen, and that is precisely why a silent notification can go unnoticed for months.

The general rule then applies as everywhere else: if the module's output is not connected to anything, the call is hung up, once the e-mail has been sent.

What to fill in

The usable variables are the built-in variables, {{caller}}, {{caller_name}}, {{callee}}, {{did}}, {{datetime}} and others, plus those set earlier in the plan by a Variable module, a DTMF entry, an API request or an Odoo module. A variable unknown at this point is replaced with blank.

Steps

1. Choose the point in the path you are interested in: the timeout output of a queue, the unknown branch of an access list, the closed window of a time condition.
2. Place the Notification module at that point and connect the previous node to its input.
3. Open it and enter the address in Destination e-mail address:.
4. Write the Message text:, placing the useful variables in it, for example Unhandled call from {{caller}} on {{datetime}}.
5. Recheck the recipient: a misspelled address produces no alert, and the plan will carry on as if nothing were wrong.
6. Connect the output to the rest of the path.
7. Click Apply changes.
8. Call in a way that goes through this specific branch, then check that the e-mail arrives.

If it doesn't work

No e-mail arrives. Check the address first. If it is written with a {{variable}} and that variable has no value at this point in the plan, the recipient becomes empty after replacement and nothing is sent. The call continues the same way in both cases, so nothing flags it to you.

The e-mail arrives, but values are missing from the text. The variables concerned do not exist at this point in the plan and were replaced with blank. The module that sets them, Variable, DTMF entry, API request or Odoo, must be placed before the notification in the path.

The caller's name is empty in the e-mail. No name is presented by the carrier for this call, and no Caller ID module set one earlier. {{CALLER_NAME}} then has nothing to pick up.

The call is hung up after the notification. The output is not connected to anything. The module never ends the call for its own reason: what ends it here is the missing connection.

The e-mail lands in spam. The sender is no-reply@axivox.com and the subject "Axivox Notification". Add this sender to your mailbox's trusted addresses, or create a filtering rule for it there.