How to Create the First MYLO Administrator and Start the MYLO Telephony Agent

The first MYLO administrator is the person who takes responsibility for the appliance’s initial ownership, user access, approvals, and consequential changes. Creating this account is not merely a form-filling step. It establishes who may approve changes that affect calling, credentials, recordings, customer data, and other users. The account should belong to a responsible individual, use a strong unique password, and be created from an authorised computer on the office network. MYLO’s guided assistance can explain or prepare supported work, but it does not replace administrator accountability. After the account is created, the administrator should secure recovery information, understand the session rules, review the site and provider prerequisites, and proceed to configuration only when the required evidence is available safely.

Why the Administrator Role Matters

A phone system can affect every public conversation a business receives or initiates. Changing an inbound route can send customers to the wrong department. Changing a caller ID can cause a provider rejection. Mishandling a recording can expose personal data. For that reason, MYLO separates conversational help from authority to execute consequential actions.

The administrator is the accountable owner of that authority. This person manages access, reviews proposals, confirms business intent, and coordinates with the telecom or network provider when facts are missing. The role should be assigned deliberately rather than given to whichever employee happens to unpack the appliance.

Choosing the First Administrator

The right first administrator normally:

• has formal permission to manage the business phone environment;
• understands which teams, numbers, and call flows the business owns;
• can obtain provider and network information without sharing it unsafely;
• can approve or reject changes based on business impact;
• will remain available for ongoing access reviews and incident decisions; and
• knows when to involve a telecom, network, privacy, or legal specialist.

In a very small company this may be the owner or office manager. In a larger organisation it may be an IT or telecom manager. Job title matters less than documented authority and availability.

Creating the Initial Account

Open MYLO through the confirmed local address from an authorised device. Verify that the page is the expected appliance interface. Enter the requested identity details accurately and create a password that is unique to MYLO. Avoid reusing a router, email, or provider password.

Complete the journey privately. Screensharing, unattended meeting recordings, browser password exposure, and copied screenshots can reveal credentials. If the organisation uses an approved password manager, store the account there with access limited to the responsible people.

The initial account should not be a generic identity such as “office” unless the approved product process explicitly requires it. Individual accountability makes later audits and access changes clearer.

Password and Recovery Protection

A strong password should be long, unpredictable, and used nowhere else. The business should also protect the email address or recovery method associated with administration. A secure password is of limited value if recovery messages go to an unmanaged shared mailbox.

Credentials should never pass through an LLM or ordinary chat response. When MYLO offers a protected credential-management action, use that dedicated authenticated surface. Support staff can explain where to perform the action without asking the customer to paste the secret into a conversation.

Document the recovery owner and offboarding procedure. If the administrator leaves the business, access must be transferred through a controlled process rather than by continuing to use that person’s account.

Understanding Single-Session Behaviour

MYLO may limit an account to one active session so that concurrent use does not obscure who is performing an administrative action. If the same account is opened elsewhere, the product’s current session behaviour should be followed rather than treated as a fault or bypassed by sharing credentials.

Sign out when administration is complete, especially on a shared workstation. If another authorised person needs access, create or assign the appropriate account and role through the supported process instead of having several people reuse the first administrator identity.

Session control reduces one category of risk but does not replace device security, screen locking, browser updates, and network access controls.

What the Administrator Approves

MYLO can understand a business request, ask questions, and prepare a proposal. A deterministic service then validates supported operations and enforces policy. The administrator’s approval confirms that the proposed outcome matches the business intent; it does not authorise unrestricted system commands.

Consequential work may include changes to users, extensions, trunks, inbound routes, IVRs, caller IDs, campaigns, recordings, provider credentials, and network configuration. The administrator should review the proposed scope, affected resources, available backup or rollback path, and verification plan before approving.

Approval is meaningful only when the person understands what will change. A vague “fix everything” request should be refined into a bounded outcome with clear acceptance evidence.

A Practical Ownership Example

A property agency assigns its operations manager as the first MYLO administrator. The manager owns the provider account, knows which published numbers belong to Sales and Support, and can approve route changes. Team supervisors receive suitable lower-privilege access later rather than sharing the administrator password.

When a supervisor asks to redirect all weekend calls, MYLO helps gather the schedule and destination. The administrator reviews the proposal and approves it. A real call then verifies that the provider’s called number reaches the intended destination. The conversational request, approval, controlled application, and live test remain distinct stages.

The Next Setup Step

After the initial account is protected, the administrator should assemble the setup packet: office network facts, SIP provider document, business numbers, channels, authentication method, user list, department structure, endpoint choices, recording decision, and expected call flows. Missing facts should be requested from their authoritative source rather than guessed.

If MYLO will use an external AI provider, the customer supplies and controls the applicable provider account and key. The key should be entered only through the approved protected workflow. It is separate from the SIP provider’s credentials and billing.

Administrator Responsibilities and Boundaries

• Keep user access aligned with current job responsibilities.
• Protect provider, endpoint, AI, and administration credentials.
• Review and approve only changes that have a clear business purpose.
• Ensure call recording, customer data, and outbound use follow the organisation’s obligations.
• Coordinate with providers and specialists where MYLO cannot establish an external fact.
• Preserve audit and history information rather than deleting inconvenient evidence.
• Require real-world tests for customer-facing call paths.

The administrator does not need to become an Asterisk engineer. The role is to own decisions and access, recognise boundaries, and obtain qualified help when a custom or high-risk requirement sits outside the prepared appliance.

First-Administrator Checklist

• Choose a named, authorised and available owner.
• Use an approved device and the confirmed local MYLO address.
• Create a long, unique password and protect the recovery method.
• Keep secrets out of ordinary chat, screenshots and spreadsheets.
• Understand the current session and sign-out behaviour.
• Plan role-appropriate accounts instead of sharing the administrator identity.
• Collect provider, network, user and call-flow information before configuration.
• Review the scope and verification method before approving a consequential change.
• Record who owns ongoing administration and offboarding.

First read how to find and open MYLO on the office network. Then review why MYLO uses the customer’s own AI-provider key. Contact MyLineHub for a scoped implementation when the required governance or integration goes beyond the prepared product boundary.

Create the Account Through a Controlled Handover

The first administrator should be a named person accountable to the business, not a shared role such as “IT” or “reception.” Verify the person through the approved onboarding process, use an individual work address where applicable, and create a strong unique password in a password manager. If the current product supports an additional authentication factor, enable and test it. Never place the initial password, recovery material, SIP secrets, or AI-provider key in ordinary email, chat, screenshots, or an article.

Complete the handover while two responsible people are available. Confirm the administrator can sign in from the permitted office network, reach only the functions expected for the role, review pending proposals, and find system evidence without exposing protected values. Record who authorised the account and when. The installer or implementation specialist should not remain as an undocumented permanent administrator after handover.

Separate Daily Work From High-Privilege Work

Administrator access should not become the default login for dialer operation, reporting, ordinary user management, or routine observation. Create narrower roles for configuration agents, campaign users, and other staff according to the supported MYLO permission model. Approval should follow the effect of an operation: reading safe status may be permitted, while changing trunks, routes, roles, network settings, campaigns, or restore state requires the authorised path.

Review the account after staff changes, suspected compromise, provider changes, and significant upgrades. Maintain a second authorised recovery administrator where the organisation’s policy permits, and test the recovery process without sharing one credential. Remove access promptly when responsibility ends. Keep durable evidence of important user and role changes while avoiding unnecessary logging of routine activity or secrets.

First-Day Security Checklist

• Confirm the management page is reachable only through the approved network or secure access method.
• Replace any temporary onboarding secret and store recovery material safely.
• Identify the business owner, carrier contact, network owner, and backup administrator.
• Verify system time, current roles, provider ownership, and escalation contacts.
• Do not approve a telecom change until its scope, backup, and acceptance test are understood.

A first administrator account is successful when authority is traceable, access is recoverable, and ordinary work can continue through least-privileged roles. It is not successful merely because one person can open every screen.