Can My Employees Receive MYLO Calls on Extensions or Phones?
Your team does not need one identical answering setup. Understand how employee extensions and phone destinations fit into MYLO call flows and how the business chooses where calls should go.
Yes. MYLO’s incoming setup is designed to distinguish between an internal extension, an external mobile destination and an IVR. That lets a business choose how a particular call should reach a person without pretending every employee has to sit beside the same type of desk phone.
Quick answer
- Start from the business outcome; MYLO uses conversation to gather or clarify the information it needs.
- Consequential telephony work stays inside the product's permissions, validation and approval boundaries.
- The telecom provider remains responsible for public numbers, carrier service, capacity and provider-side conditions.
Choose the employee destination that matches the workflow
Extension
An internal Asterisk telephone identity.
Agent mobile
An external mobile destination used by supported call flows.
Business number
The public number customers see or dial; it is not the employee extension.
What Is an Extension in Plain Language?
An extension is the internal identity used by the business phone system for a telephone user. A desk phone or softphone can register with the credentials for that profile. MYLO v0.35 includes managed telephone-user profiles and administrator-only access to the current local PJSIP credentials through the browser/API boundary.
What About an External Mobile?
Some MYLO flows use an employee mobile number as an external destination. That is different from an internal extension because the call must use carrier resources to reach the mobile network. The product’s destination catalogue reflects that difference, including different channel cost for mobile versus extension destinations in campaign flows.
Choose Based on How the Team Actually Works
An office-based support desk may prefer extensions or softphones. A field-sales workflow may need an employee mobile. The article should not declare one universally better. Instead, match the destination to availability, privacy, carrier cost and the customer experience you want.
Keep Credentials and Employee Numbers Controlled
Telephone-profile credentials are sensitive operational data and should not be pasted into public chat or documentation. MYLO’s credential route is administrator-only and intentionally does not send the password through chat, run events or the LLM.
Continue From Here
Custom Requirements and Telecom Responsibility
MYLO configures and operates the customer's local telephony layer; it is not the telecom carrier. Numbers, trunk service, calling charges and provider-side permissions remain with the customer's telecom provider. Where a requirement sits outside the standard MYLO package, MyLineHub can discuss it as a Custom Requirement.
Customisation does not override telecom-provider conditions, customer-consent obligations or applicable Indian telecom requirements. The final calling design must use services and number-routing methods that the business is permitted to use.
Want to see API-driven CRM + Telecom workflows in action? Try the WhatsApp bot or explore the demos.
Comments (0)
Be the first to comment.