Five Ways MYLO Can Connect Your Team and Customers

MYLO v0.35 has five defined campaign connection patterns. They are not marketing examples invented for this article; they are seeded product data that tells the campaign engine whether the customer or employee side is called first and what kind of destination is required.

The five v0.35 campaign connection types

1. Customer → Agent Mobile

MYLO calls the customer first. After the customer answers, the configured employee mobile is called. This suits a workflow where the employee should only be involved after a customer connection is available.

2. Customer → Agent Extension

The customer is called first and, after answer, MYLO connects the configured internal extension. This keeps the employee on the office/softphone side of the telephony system.

3. Agent Extension → Customer

MYLO waits for the employee’s extension to answer before it calls the customer. The employee is therefore ready before the customer leg begins.

4. Agent Mobile → Customer

The employee’s mobile is reached first; after answer, MYLO calls the customer. Because the mobile is an external destination, this flow uses carrier resources differently from an internal extension.

5. Customer → IVR

MYLO calls the customer and connects an answered call to an active IVR. This is the automated/menu path rather than a live-employee path. Use it only for an appropriate, compliant business purpose.

Why MYLO Keeps These as Defined Patterns

Defined patterns make campaign execution predictable. The customer chooses the business flow during preparation; the deterministic scheduler then follows the stored pattern. If a business needs a sixth, materially different connection design, that should be evaluated as a Custom Requirement instead of pretending the standard product already contains it.

Continue From Here

• How the two call legs connect
• Choose mobile or extension
• Customer-to-IVR in more detail
• Why IVR capacity differs

Use MYLO Within Your Telecom and Customer-Consent Rules

MYLO provides the telephony and campaign layer; it does not turn an unapproved calling practice into an approved one. Businesses using outbound or automated calling must follow the current rules that apply to their purpose, sender registration, consent, customer preferences and telecom-provider service. TRAI maintains current guidance for commercial-communication senders and explains spam and unsolicited commercial communication.

Customisation is welcome. MyLineHub can discuss a Custom Requirement when the standard MYLO package does not cover the required workflow. Any custom implementation must still use telecom resources lawfully and follow applicable provider conditions and Indian telecom requirements.