Trigger callback requests from the website widget

CallPage's website widget lets a visitor request an immediate or scheduled callback from a sales rep. A Beam agent reads new callback requests as they come in, checks the visitor's details against the CRM, and either creates a new lead or attaches the request to an existing one. It notifies the assigned rep or queue based on the rule the team set, such as by region or product interest. When a request has no clear owner or the visitor's details do not match anything in the CRM, the agent routes it to a manager instead of assigning it blindly.

Log call outcomes against lead records

After a CallPage call happens, the outcome, whether connected, missed, or completed, needs to be reflected wherever the lead lives. A Beam agent reads the call record once it closes, matches it to the corresponding lead, and updates the lead's status and notes field in the CRM. It logs the call duration and outcome for reporting. When the call record cannot be matched to a lead with confidence, or the outcome looks inconsistent with the lead's current stage, the agent leaves the update pending and flags it for the rep to confirm.

Track widget performance and call volume

CallPage reports how many visitors triggered the widget, how many became calls, and how many converted into leads. A Beam agent pulls these figures on a schedule and compares them against the prior period or an agreed benchmark. It updates a shared report with the current numbers so the marketing team can see trends without pulling the data manually. When call volume or conversion drops sharply against the benchmark, the agent flags the change to the marketing owner rather than logging a bad week silently.