Call logging

Every inbound and outbound call leaves a record of number, duration, and outcome. A Beam agent reads each new call log from Yay.com as it closes, applies the tagging rule you approved, and writes the matching note or activity onto the right customer record in your connected systems. Missed calls can be queued for a callback list the same way. Calls it cannot tie to a known contact, or ones where the number is withheld, are left untagged and passed to a person, since guessing which account a stray call belongs to would put notes on the wrong file for good.

Voicemail routing

Voicemails arrive as recordings tied to the extension that received them. When a new message lands, the agent reads the voicemail details and the destination extension, applies your forwarding rule, and notifies the owner or team responsible so nothing sits unheard overnight. Urgent keywords in a transcript, where the account provides one, can bump a message up the queue. Messages with no clear owner, or ones your filters mark as spam, are held and sent to a person to place, because forwarding a sensitive voicemail to the wrong desk is worse than a short wait for a human check.

Number and extension setup

Each user, team, and site maps to a phone number and extension in Yay.com. A Beam agent reads onboarding or offboarding events from your directory, applies the provisioning rule you set, and updates the extension assignment or forwarding target so a new hire can take calls on day one. Changes that touch billing, add a whole new number range, or conflict with an existing assignment are never made alone. Those are recorded and routed to a person, since a mistaken extension change can silently drop calls for a whole team until someone finally notices the gap.