What is the role of a Tech Support?

Tech Support helps you diagnose and resolve issues with the MyOperator platform—errors, call-flow behavior, configuration questions, integrations, and connectivity—then escalates to Engineering when needed.
Contents
- When to contact Tech Support
- What Tech Support covers
- What Tech Support doesn’t do
- Prerequisites (what to collect before you contact us)
- How to contact Tech Support (steps)
- What to expect after you contact us
- Example: CRM sync issue
- Self-serve quick checks
- Privacy & security boundaries
- Hours & channels
- Related articles
- Glossary
When to contact Tech Support
Contact us when you experience:
- System errors or failed actions in the web app or mobile app.
- Unexpected call-flow behavior (IVR, queues, recordings, masking).
- Integration issues (CRM, API, webhooks).
- Connectivity problems (one-way audio, dropped calls, agent not ringing).
What Tech Support covers
- First-level troubleshooting: tickets, chat, or calls about platform errors or performance.
- Issue diagnosis & debugging: identify misconfigurations, backend faults, or third-party failures.
- Configuration help: IVR, queues, voicemail, number settings, recording/privacy options.
- Integration guidance: webhook/API configuration, CRM field mapping, basic validation.
- Escalation: hand-offs to Product/Engineering for deeper investigation or platform fixes.
What Tech Support doesn’t do
- Custom development or building new product features.
- Professional services outside standard setup guidance.
- Handling your customers’ data beyond troubleshooting needs.
- Third-party account management (e.g., CRM billing, carrier contracts).
We log feature requests and share them with the Product team for review. Timelines depend on scope, priority, and feasibility.
Prerequisites (what to collect before you contact us)
Have these ready to speed up resolution:
- Account ID and registered email.
- Issue summary and impact (e.g., “20% of outbound calls fail in Sales queue”).
- Time range and affected numbers/agents.
- Evidence: screenshots, error messages, Call IDs or sample numbers.
- Logs (if asked): console log or HAR file, and webhook/API payload samples.
- Change history: recent edits to IVR, queues, integrations, or network/firewall.
How to contact Tech Support (steps)
- Open the Support Portal: JIRA -
https://myoperator.com/support - Click Submit a ticket (or open in-app chat from the help icon).
- Fill in: account ID, summary, impact/severity, time range, samples, and attach screenshots/logs.
- Submit. You’ll get a ticket ID by email.
- For urgent issues, include “SEV1” in the subject:
[SEV1] Brief summary – <Account ID>.
Prefer email? Write to support@myoperator.com with the same details.
What to expect after you contact us
- Acknowledgement: ticket ID and tracking link by email.
- Initial triage: we validate symptoms, gather data, and attempt a quick fix.
- Resolution or escalation: if backend or platform changes are needed, we escalate to L2/Engineering and keep you updated.
- Target first response: within 4 business hours during support hours (may vary by queue/plan).
Example: CRM sync issue
Scenario: Recent calls are not appearing in your CRM.
What Support will do:
- Review Call Logs and recent dispositions.
- Check webhook/API delivery status and error codes.
- Validate integration mapping (lead/contact IDs, required fields).
- Reproduce the issue with a test call.
- Escalate to Engineering if a backend fault is detected and share interim workarounds.
Self-serve quick checks
Before opening a ticket, try:
- Browser refresh & cache clear; test an incognito window.
- Verify agent status is Available and device/softphone is registered.
- Confirm recording/privacy and queue membership settings.
- Check integration credentials (tokens, webhook URLs) and recent CRM permission changes.
- Test with one known-good number and a different network (to rule out firewall/ISP issues).
Privacy & security boundaries
- Do not share passwords, full access tokens, or private keys.
- Mask PII in screenshots (card numbers, government IDs).
- Grant temporary, least-privilege access when we request it.
- We will not perform data deletion or export without account-owner approval.
Hours & channels
- Portal & chat: https://myoperator.com/support
- Include BAN, Service Number, Explain the issue, and Summary of the Issue in every request.
Glossary
- API (Application Programming Interface): A way for systems to exchange data programmatically.
- Webhook: An HTTP callback from MyOperator to your system when events occur.
- CRM (Customer Relationship Management): Your system of record for leads and customers.
- Call ID: A unique identifier for a call used to trace logs across systems.
You’re set. If anything blocks you, open a ticket at https://myoperator.com/support with subject **Tech Support – <BAN/SN> – <Brief summary>`.
Related Articles
What is the role of a Tech Support?
Tech Support is responsible for handling all the technical issues and provides first-level resolution for all the product-related issues. They are also responsible for getting the new development done based on the client's requirements.
What permissions are assigned to each role?
MyOperator Pro has three user roles with a clear hierarchy. Use roles to apply least-privilege access, keep data secure, and make audits simple. Roles at a glance Administrator (Admin / Super admin) — Full, account-wide control across all data and ...
Can I create a role according to my choice?
Short answer: Not right now. MyOperator supports three predefined user roles—Administrator, Manager, and Call Agent. You cannot create new custom roles or edit role permissions. When you’d want this You may want a custom role to fine-tune ...
How can I change the role for an added user?
Use roles to give teammates just the access they need. Follow these steps to change a user’s role. When & why Apply least-privilege access for security and compliance. Update responsibilities when people join, move teams, or leave. Prerequisites ...
How can I change the default permissions for the user or role?
Use role-based permissions to give teammates only the access they need. In MyOperator, default permissions are set at the role level (Administrator, Manager, Basic/Call agent). To affect a single user, change their role or use a customized role if ...