Agent Extension to Customer Phone: How the Flow Works

In the agent-extension-to-customer-phone flow, MYLO calls an approved office extension first and originates the customer call only after the agent is ready. This ordering reduces the chance that an answered customer waits for a human or is abandoned because the agent leg failed. Its trade-off is agent time: the employee may wait through ringing, no answer, busy, or an unsuccessful customer attempt. Deterministic runtime services assign one eligible agent, enforce capacity and schedule, select an authorised caller ID, and classify outcomes after an approved campaign starts. Asterisk originates and bridges the legs; the telecom provider supplies external service and channels. The business owns the lead purpose, contact authority, staff readiness, retry policy, recording decision, and call outcome. Agent-first is a customer-experience choice, not proof of improved answer rates.

Prepare the Agent

MYLO selects an eligible extension and asks Asterisk to call it. The agent should receive enough campaign context to understand the expected interaction. Busy, unavailable, rejected, and no-answer states stop the flow before customer contact and remain agent-side outcomes.

Registration is necessary but not sufficient evidence of human readiness. Login, campaign assignment, working hours, and one-active-flow-per-person rules should agree. Shared desks and forwarding need documented ownership.

Originate the Customer Call

After the agent-ready condition, the deterministic service selects the approved lead attempt and authorised business caller ID. It then originates the external leg. The agent may hear an accurate waiting indication while the phone rings. Set a maximum duration so an employee is not held indefinitely.

Customer busy, no answer, rejection, invalid number, and provider error require distinct results and bounded retry rules. Voicemail should be handled according to the approved campaign policy rather than assumed to be a person.

Bridge and Record the Outcome

When the customer answers under the defined state, Asterisk bridges media. The runtime preserves agent, lead, DID, timestamps, attempts, leg outcomes, and bridge evidence. The employee records the business disposition separately because connection does not equal resolution.

If either participant hangs up before bridging, the remaining leg must end safely. Recovery after a service restart reconciles stored state with live telephony evidence to avoid duplicate contact.

Practical Example

An office insurance-service team returns requested calls through extensions 301–305. MYLO first rings the assigned employee. After the employee confirms readiness, the customer's phone rings with an authorised business number. If the customer does not answer, the agent is released and the attempt follows the approved retry window. If the employee does not answer initially, no customer call occurs.

The supervisor measures agent wait, customer answers, bridge success, retries, and outcomes. Tests include unavailable extension, customer voicemail, trunk capacity, agent hang-up, and restart recovery.

Limits and Responsibilities

• Agent-first uses employee time during customer ringing.
• Extensions can be registered yet unattended.
• Provider channels and authorised caller IDs remain external dependencies.
• The customer owns lawful contact, lead quality, schedules, retries, recording, and staffing.
• MYLO's AI assistance cannot override deterministic capacity or initiate unapproved work.

Checklist

• How does an extension become eligible?
• What confirms the agent is ready?
• How long may the customer ring?
• What releases the agent on failure?
• How are voicemail and no-answer classified?
• Are retries and caller IDs approved?
• Can restart recovery prevent duplicate calls?
• Has each failure path been tested externally?

Compare the reverse order in Customer Phone to Agent Extension and the remote-agent version in Agent Mobile to Customer Phone.

Agent Readiness Changes the Customer Experience

This flow spends some agent time before knowing whether the customer will answer, but it avoids placing an answered customer into a wait for an employee. The business should give the agent enough campaign context before the customer leg starts, define how long the customer may ring, and release the agent promptly after no answer, busy or provider rejection.

Measure agent waiting separately from connected conversation time. A high no-answer rate may indicate list quality, timing or caller-identification problems rather than poor employee performance. Test customer voicemail, early agent hang-up and trunk-capacity exhaustion so each outcome closes both legs safely.