Short answer: Share your Zendesk subdomain and API token, plus your MyOperator service number, with Support for backend enablement. Then validate auto‑ticketing (answered vs missed) and keep agent emails synchronized across both systems so assignment stays accurate.

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

🧭 Table of Contents

• What this integration does
• Prerequisites
• Security & data mapping
• Step‑by‑step setup
• Validate the integration
• User sync & ongoing maintenance
• Expected outcomes & success checks
• Edge cases & limitations
• Troubleshooting
• FAQs
• Related articles
• Structured data (SEO)

📈 What this integration does

• Auto‑creates Zendesk tickets for calls handled via MyOperator.
• Assignment logic (typical):
• Answered calls → ticket assigned to the answering agent.
• Missed calls → ticket assigned to admin or a specified group.
• Adds call context: direction, numbers, time, duration, optional recording link, and MyOperator call ID as a custom field.

Screenshot placeholder
Alt: Zendesk ticket list showing new tickets with tag myoperator and assignees.
Caption: “Tickets created automatically from MyOperator calls with tags and correct assignees.”

Back to top

✅ Prerequisites

• Your Zendesk subdomain (e.g., acme.zendesk.com).
• A Zendesk API token (Admin generates in Zendesk).
• Your MyOperator service number.
• Agent emails match in Zendesk and MyOperator.
• MyOperator Pro plan enabled.
• (Recommended) A test contact and test number for validation.

How to generate a Zendesk API token (copy‑paste steps)

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 and store it securely (you’ll only see it once).
4. Rotate the token periodically and after any compromise.

Back to top

🔒 Security & data mapping

Token handling

• Share tokens only via your approved secure channel.
• Prefer a dedicated integration token; rotate at least quarterly.
• Revoke old tokens after rotation and inform Support to update the backend.

Typical ticket field mapping (illustrative)

Back to top

🪜 Step‑by‑step setup

STEP 1 — Prepare

• Zendesk subdomain
• Zendesk API token
• MyOperator service number
• Agent emails aligned across Zendesk/MyOperator
• MyOperator Pro plan

STEP 2 — Share details with MyOperator Support
Send the following to support@myoperator.com (template below):

Email template (copy‑paste)

Subject: Zendesk integration setup request — <Your Company>Hi MyOperator Support,Please enable the Zendesk integration for our account.Zendesk subdomain: <acme.zendesk.com>Zendesk API token: <paste token or secure-share reference>MyOperator service number: <e.g., +91-80-1234-5678>Primary admin email: <admin@company.com>Agent emails to verify (if different between systems):- <name> — <email>- <name> — <email>We’ll run validation calls once enabled. Thanks!

STEP 3 — Backend configuration by MyOperator
The tech team configures:

• API authentication to Zendesk
• Call‑to‑ticket logic (answered → agent; missed → admin/group)
• User mapping by email; tags/fields per your preferences

STEP 4 — Acknowledge & move to validation
Support confirms when backend setup is complete.

(Optional) STEP 5 — Triggers/Automations in Zendesk

• Add a trigger for tag missed-call to route to your Support L1 group.
• Add automations for SLA follow‑ups if missed‑call tickets remain Open for N minutes.

Back to top

🔎 Validate the integration

Run these checks with one answered and one missed call.

1. Place a test incoming call to your MyOperator service number.
2. Answer the call as an agent mapped by email.
3. In Zendesk, confirm a new ticket is created and assigned to the answering agent, with call details and tags.
4. Place another call and don’t answer. Confirm a ticket is created and assigned to admin (or the configured group).
5. (If recording is enabled) Ensure the recording link is present.
6. Repeat with a second agent to validate mapping.

Back to top

🔁 User sync & ongoing maintenance

When people join/leave or change emails:

• Email support@myoperator.com to sync user emails so tickets keep assigning correctly.
• If you rotate the Zendesk token, notify Support to update the backend.
• Re‑run a quick validation after any user/token change.

Back to top

🎯 Expected outcomes & success checks

• Every MyOperator call results in a Zendesk ticket with call metadata.
• Answered calls assign to the answering agent; missed calls assign to admin or specified group.
• Tags/fields appear consistently; optional recording links are included.

Success checklist

• Tickets appear for both answered and missed tests.
• Assignee matches the agent for answered calls.
• Tags/fields match your requested configuration.

Back to top

⚠️ Edge cases & limitations

• Rate limits (HTTP 429): Zendesk API has limits—stagger bulk calls or coordinate throttling.
• Token rotation: Update Support immediately after rotation to avoid failures.
• Partial routing: If only some calls traverse MyOperator, only those will ticket.
• Recording links: Subject to plan and policy; allowlist URLs if your org restricts external links.
• Agent mismatch: Tickets assign wrong if emails don’t match—keep directories aligned.

Back to top

🧰 Troubleshooting

Still stuck? Email support@myoperator.com with timestamps, agent emails, example numbers, and screenshots.

Back to top

🙋 FAQs

• Do we need to install a Zendesk Marketplace app?
  Not for this setup—the MyOperator team enables the backend integration.
• Can we assign missed calls to a group instead of admin?
  Yes—tell Support the group name/ID to use in backend rules.
• Can we add custom fields or tags?
  Yes—share field IDs and desired tags; the team can add them during setup.
• Is sandbox supported?
  Yes—provide your sandbox subdomain and a sandbox API token for testing.

Back to top

🔗 Related articles

• Zendesk: Create & manage API tokens — enabling token access
  https://support.zendesk.com/hc/en-us/articles/226022787
• Zendesk: Triggers & automations — route missed-call tickets
  https://support.zendesk.com/hc/en-us/categories/4405372617242
• User email mapping — keep ownership accurate
  https://support.myoperator.com/users/email-mapping
• CRM call logging troubleshooting — common causes & fixes
  https://support.myoperator.com/crm/call-logging-troubleshooting

Back to top

🔎 Structured data (SEO)

<script type="application/ld+json">{  "@context": "https://schema.org",  "@type": "HowTo",  "name": "Configure the Zendesk–MyOperator integration",  "tool": ["Zendesk Support", "MyOperator"],  "totalTime": "PT10M",  "step": [    {"@type": "HowToStep", "name": "Prepare", "text": "Get your Zendesk subdomain and API token, note your MyOperator service number, align agent emails, confirm Pro plan."},    {"@type": "HowToStep", "name": "Share details with Support", "text": "Send subdomain, API token, and service number to support@myoperator.com using the provided template."},    {"@type": "HowToStep", "name": "Backend configuration", "text": "MyOperator configures API auth, call-to-ticket logic, and agent assignment by email."},    {"@type": "HowToStep", "name": "Validate", "text": "Place answered and missed test calls; verify ticket creation, assignment, and recording link."}  ]}</script><script type="application/ld+json">{  "@context": "https://schema.org",  "@type": "FAQPage",  "mainEntity": [    {"@type": "Question", "name": "Do we need a Marketplace app?", "acceptedAnswer": {"@type": "Answer", "text": "No. MyOperator enables the integration on the backend after you share details."}},    {"@type": "Question", "name": "Can missed calls assign to a group?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Provide the group name/ID; Support will configure the backend rule."}}  ]}</script>

Back to top

Keywords:

Zendesk integration, myoperator, call-to-ticket, auto-ticketing, agent assignment, missed-call routing, recording link, API token, subdomain, email mapping