Inbound Lead Routing

Convolo.ai connects an inbound lead to a sales rep as soon as they call or submit a form, since response speed affects whether the lead converts. A Beam agent reads the lead's details as they come in, applies the approved rule for which rep or queue should get the call, such as routing by territory or product interest, and passes the lead through Convolo.ai accordingly. It notes the routing decision for later reporting. Leads that don't match an existing routing rule, such as a product line with no assigned rep yet, are routed to a human to place.

Call Outcome Logging

After a Convolo.ai call ends, the outcome, such as booked, no answer, or not interested, needs to be reflected against the lead record so the next action is clear. A Beam agent reads the call outcome, applies the approved rule for what happens next, such as scheduling a follow up call for a no answer, and updates the lead's status. It keeps the record current so reps aren't working from stale information. Calls with an outcome that's unclear or that involve a complaint are routed to a human to review before the next step is taken.

Callback Scheduling

When a lead can't be reached or asks to be called back later, Convolo.ai needs that callback queued for the right time and rep. A Beam agent reads the requested callback window, applies the approved rule for scheduling it, such as matching the lead's time zone and rep availability, and books the callback in Convolo.ai. It confirms the booking and reminds the assigned rep so the lead isn't missed. Requests with an unusual timing ask, like a callback outside normal business hours, are routed to a human to arrange directly.