Talk to the team
Describe the issue, the affected device, and when it happened. Never include a password, PIN, full payment-card number, or private customer records.
Call (845) 723-1213Get help with your setup, discuss a change, or find the tools available in your company workspace.
Describe the issue, the affected device, and when it happened. Never include a password, PIN, full payment-card number, or private customer records.
Call (845) 723-1213Sign in for your company’s enabled features, app downloads, setup guidance, and available product lessons.
Open your workspaceSend a clear description of the help you need. Response hours and any response-time commitments follow your service agreement.
Email LoopcomFor an emergency, contact emergency services directly. Website messages and ordinary support requests are not monitored as an emergency channel. Review the VoIP emergency calling notice.
Include the approximate date and time, the affected business line or user, whether the problem affects one person or several, and what the caller or recipient experienced. Share sensitive identifiers only through the channel the team asks you to use.
Tell us the device type, operating system, app or browser, the action you were taking, and the visible error. Explain whether it worked previously and whether the issue occurs on another permitted device.
Identify the workflow and approximate time, explain which step did not complete, and describe what the destination system shows. Do not repeatedly submit an uncertain order or payment; ask the team to establish the actual result.
Describe the desired outcome, the affected people or location, and any deadline. A new feature, device, workflow, or integration may need a scope review before it can be scheduled.
Keep your designated contacts, schedules, approved business information, and authorized users up to date through the agreed process. Tell the team when an existing vendor, device, or business workflow changes, because a connection may depend on it. Your service agreement defines support availability and any response-time commitments.
For supported Windows remote help, access follows the configured permission and connection process. Understand who is connecting and what access you are granting, and end the session when help is complete. Never send a password or PIN in an ordinary support email.
Sign in to your company workspace and consult your service setup or proposal. Available tools can depend on your role, enabled services, device, and the stage of a tailored rollout.