Short answer: You’ll need your Zendesk subdomain, a Zendesk API token, your MyOperator service number, and matching agent email IDs across both systems. A MyOperator Pro plan is required, and you must be able to share these details with Support and request user sync when your team changes.

• Applies to: Zendesk Support (latest) & MyOperator Web Dashboard • Audience: Admins/Owners • Plan: MyOperator Pro or higher

🧭 Table of Contents

• Overview
• Requirements checklist (copy‑paste)
• Why each item matters
• Generate your Zendesk API token
• Security & compliance
• Provide details to Support (email template)
• Validation (quick sanity check)
• Troubleshooting
• FAQs
• Related articles
• Structured data (SEO)

📋 Overview

To enable Zendesk ↔ MyOperator integration, prepare these items:

• Zendesk subdomain (e.g., acme.zendesk.com).
• Zendesk API token (Admin → Admin Center → Apps & integrations → APIs → Zendesk API).
• MyOperator service number (your primary/virtual number).
• Matching user email IDs in Zendesk and MyOperator for correct ticket assignment.
• MyOperator Pro plan enabled.
• Ability to contact MyOperator Support to submit the details and raise user‑sync requests when users are added/changed.

Back to top

✅ Requirements checklist (copy‑paste)

Copy this block, fill it, and send it to Support (see email template below).

Zendesk subdomain: <acme.zendesk.com>Zendesk API token: <paste token or secure-share reference>MyOperator service number: <e.g., +91-80-1234-5678>MyOperator plan: Pro (yes/no)Agent email alignment confirmed: (yes/no)Primary admin/contact: <name> — <email>Need group for missed-call assignment? <group name/ID>Need tags/custom fields? <list>

Back to top

🧠 Why each item matters

Back to top

🔐 Generate your Zendesk API token

1. In Zendesk Admin Center, go to Apps and integrations → APIs → Zendesk API.
2. Enable Token Access and click Add API token.
3. Copy the token (you will only see it once); store it securely.
4. Rotate the token periodically and after any suspected compromise.

Back to top

🛡️ Security & compliance

• Share tokens only via approved secure channels; avoid email where possible.
• Prefer a dedicated integration token; rotate quarterly and revoke old ones.
• If your org restricts external links, allowlist recording URLs used in tickets.
• Ensure lists respect consent/DND rules if call recordings/links are included.

Back to top

✉️ Provide details to Support (email template)

Use this template to submit your requirements.

Subject: Zendesk integration requirements — <Your Company>Hi MyOperator Support,Please enable the Zendesk integration for our account using the details below.Zendesk subdomain: <acme.zendesk.com>Zendesk API token: <paste token or secure-share reference>MyOperator service number: <e.g., +91-80-1234-5678>MyOperator plan: Pro (yes/no)Agent email alignment confirmed: (yes/no)Missed-call assignment group: <group name/ID, if any>Tags/custom fields to apply: <list>Primary admin/contact: <name> — <email>We’ll run validation calls once enabled. Thank you!

Back to top

🧪 Validation (quick sanity check)

After Support confirms enablement, perform one answered and one missed test call:

• Answered call → a ticket is created and assigned to the answering agent; it includes call context (direction, time, duration, tags, optional recording link).
• Missed call → a ticket is created and assigned to admin or the configured group with missed-call tag.

If either test fails, request a user sync or token re‑check with Support.

Back to top

🧰 Troubleshooting

Back to top

🙋 FAQs

• Is a Marketplace app required?
  No. The MyOperator team enables the backend integration after you share the requirements.
• Can missed calls be assigned to a group?
  Yes. Provide the group name/ID in your request.
• What if our team changes?
  Email Support to sync users so ticket assignment remains accurate.
• Where do I find the API token?
  Admin Center → Apps and integrations → APIs → Zendesk API → Add API token.

Back to top

🔗 Related articles

• Configure Zendesk ↔ MyOperator — step‑by‑step setup and validation
• Zendesk: Create & manage API tokens — enabling token access
• Triggers & automations for missed calls — route missed-call to the right group
• CRM call logging troubleshooting — common causes & fixes

Back to top

🔎 Structured data (SEO)

<script type="application/ld+json">{  "@context": "https://schema.org",  "@type": "FAQPage",  "mainEntity": [    {"@type": "Question", "name": "What are the requirements for Zendesk integration with MyOperator?", "acceptedAnswer": {"@type": "Answer", "text": "Zendesk subdomain, Zendesk API token, MyOperator service number, matching agent emails, MyOperator Pro plan, ability to share details with Support and request user sync."}},    {"@type": "Question", "name": "Why must agent emails match?", "acceptedAnswer": {"@type": "Answer", "text": "Ticket assignment relies on email matching between Zendesk and MyOperator to attribute tickets to the correct agent."}},    {"@type": "Question", "name": "How do I get a Zendesk API token?", "acceptedAnswer": {"@type": "Answer", "text": "Admin Center → Apps and integrations → APIs → Zendesk API → Add API token; copy and store securely."}}  ]}</script><script type="application/ld+json">{  "@context": "https://schema.org",  "@type": "HowTo",  "name": "Provide Zendesk integration requirements to MyOperator",  "tool": ["Zendesk Support", "MyOperator"],  "totalTime": "PT5M",  "step": [    {"@type": "HowToStep", "name": "Collect details", "text": "Gather subdomain, API token, service number, confirm agent emails and plan."},    {"@type": "HowToStep", "name": "Send to Support", "text": "Use the provided email template to share details with support@myoperator.com."},    {"@type": "HowToStep", "name": "Validate", "text": "Perform an answered and a missed test call and verify ticket creation and assignment."}  ]}</script>

Back to top

Keywords: zendesk integration requirements, myoperator, subdomain, API token, service number, email mapping, pro plan, tech support access, user sync, missed-call routing, recording link