Notification routing

Opt in by adding RoutesNotificationsViaContacts alongside HasContacts. It resolves Laravel notification destinations from the owner’s primary contacts:

use Illuminate\Notifications\Notifiable;
use RoundlyConsulting\Contacts\Concerns\HasContacts;
use RoundlyConsulting\Contacts\Concerns\RoutesNotificationsViaContacts;

class User extends Model
{
    use HasContacts;
    use Notifiable;
    use RoutesNotificationsViaContacts;
}

$user->addEmail('[email protected]', primary: true);
$user->addPhone('+421 900 000 000', primary: true);

$user->routeNotificationForMail();     // '[email protected]'
$user->routeNotificationForVonage();   // '+421900000000'
$user->routeNotificationForTwilio();   // '+421900000000'

$user->notify(new OrderShipped($order));   // your own notification class

• routeNotificationForMail() — the primary email.
• routeNotificationForVonage() and routeNotificationForTwilio() — the primary phone.
• Each returns null when there is no primary of that kind, so Laravel simply skips that channel.

Precedence

The trait is intentionally separate from HasContacts and is not applied automatically, because host models often already use Notifiable. When you do add it, these routeNotificationFor*() methods take precedence over Notifiable’s attribute-based routing for the mail, Vonage and Twilio channels.