> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://myoperator.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Why is MyOperator offering this program?

## Table of contents

1. [What is the Technology Partner Program?](#2-1-what-is-the-technology-partner-program)
1. [Why is MyOperator offering this program?](#2-2-why-is-myoperator-offering-this-program)
1. [Who should join?](#2-3-who-should-join)
1. [Partner benefits (quick list)](#2-4-partner-benefits-quick-list)
1. [How to join — step-by-step](#2-5-how-to-join-step-by-step)
1. [Technical prerequisites & integration paths](#2-6-technical-prerequisites-integration-paths)
1. [Onboarding timeline & deliverables](#2-7-onboarding-timeline-deliverables)
1. [Expected outcomes & KPIs](#2-8-expected-outcomes-kpis)
1. [Common edge cases and limitations](#2-9-common-edge-cases-and-limitations)
1. [Troubleshooting (common issues & fixes)](#2-10-troubleshooting-common-issues-fixes)
1. [Related resources & contact](#2-11-related-resources-contact)

---

## 1. What is the Technology Partner Program?

The MyOperator Technology Partner Program is a formal partner track for software platforms (CRM, ERP, helpdesk, and other SaaS tools) to integrate MyOperator’s cloud telephony. Partners get access to APIs, sandbox environments, co-marketing, and joint GTM (go-to-market) support.

## 2. Why is MyOperator offering this program?

*  Bold Make telephony available where customers work. Integrations embed calling, IVR, and call analytics inside third-party apps.
*  Bold Speed innovation. Partner-built integrations release features faster than building everything in-house.
*  Bold Scale sales efficiently. Partners extend MyOperator into new verticals and smaller cities without adding direct-sales overhead.
*  Bold Create shared commercial value. Co-selling, revenue share, and joint-marketing increase deal velocity for both parties.
*  Bold Support startups. Credits and low-cost onboarding help early-stage companies adopt telephony early.

## 3. Who should join?

* SaaS platforms that serve customer-facing teams (support, sales, ops).
* CRMs, ERPs, helpdesk systems, and workflow platforms that benefit from embedded voice and call data.
* Early-stage startups building voice-dependent products and looking for low-cost telephony.

## 4. Partner benefits (quick list)

* Dedicated partner manager and onboarding support.
* API access and sandbox environment.
* Co-branded marketing programs and partner listings.
* Revenue-sharing on referred and co-sold customers.
* Startup credits for eligible early-stage companies.

## 5. How to join — step-by-step

1. Visit the partner page: [https://myoperator.com/technology-partner](https://myoperator.com/technology-partner) (copy-paste).
1. Complete the partner application form.
1. A partnership manager will confirm eligibility and send the onboarding pack.
1. Sign the partnership agreement (standard terms).
1. Start technical onboarding: get API keys and sandbox access.
1. Validate the integration in staging, then request production enablement.

Bold Copy-paste contact: [partner-ops@myoperator.com](mailto:partner-ops@myoperator.com)

## 6. Technical prerequisites & integration paths

Bold Prerequisites (minimum):

* API-capable platform with webhooks or server-side scripting.
* Ability to host OAuth or API-key based authentication.
* Test/staging environment to validate call flows and webhooks.

Bold Supported integration paths:

*  Bold Embedded UI integration: Use MyOperator JavaScript SDK or iframe for quick UI embed.
*  Bold API-first integration: Use REST APIs for call initiation, call logs, and analytics.
*  Bold Webhook-based events: Receive real-time call events for call status, recordings, and agent events.
*  Bold Mobile SDKs: Lightweight SDKs for Android/iOS for in-app calling (ask partner manager).

Bold Sample curl to fetch call logs (copy-paste):
```
curl -X GET "https://api.myoperator.com/v1/calls?from=2025-07-01&to=2025-07-24" \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -H "Accept: application/json"
```

Bold Expected success response (example):
```json
{ "calls": [{ "id": "c_1234", "from": "+91XXXXXXXXXX", "to": "+91YYYYYYYYYY", "duration": 180 }] }
```

## 7. Onboarding timeline & deliverables

*  Bold Day 0–3: Application review and eligibility confirmation.
*  Bold Day 4–10: Legal + commercial setup; sign agreement.
*  Bold Week 2: Technical onboarding, sandbox keys, and docs delivered.
*  Bold Week 3–4: Integration build + staging validation.
*  Bold Week 5: Production enablement and co-listing on partner directory.

|| Info
Timeframes are typical. Exact timelines depend on partner engineering bandwidth.

## 8. Expected outcomes & KPIs

Bold Short-term (30–90 days):

* Working sandbox integration.
* First joint marketing asset or co-listing.

Bold Mid-term (3–6 months):

* 1–3 live customers using the integration.
* Shared sales leads and first revenue share payments.

Bold KPIs to track: Integration activation rate, time-to-first-call, number of co-sold deals, ARR from partner channel.

## 9. Common edge cases and limitations

*  Bold Non-API platforms: If a partner lacks APIs, MyOperator may offer limited integration paths or require middleware.
*  Bold Regulatory limitations: Local telecom regulations (DND, consent) may affect call features in certain regions.
*  Bold Recording restrictions: Call recording availability depends on regional laws and customer consent flows.

## 10. Troubleshooting (common issues & fixes)

*  Bold Webhook not received: Check firewall/IP allowlist and verify webhook URL responds with HTTP 200.
*  Bold API authentication error: Confirm API key or OAuth token validity and system clock sync (for signed tokens).
*  Bold Call quality issues on mobile: Verify network (3G/4G/5G) and codec settings; enable STUN/TURN if needed for real-time media.

If you hit a blocker, open a support ticket at [support@myoperator.com](mailto:support@myoperator.com) with these items: integration name, environment (staging/prod), sample request ID, and timestamps.

## 11. Related resources & contact

* Partner program page: [https://myoperator.com/technology-partner](https://myoperator.com/technology-partner)
* Integration docs & sandbox: (provided after application)
* Support: [support@myoperator.com](mailto:support@myoperator.com)
* Partnership contact: [partner-ops@myoperator.com](mailto:partner-ops@myoperator.com)

Bold Suggested related FAQs to link from this article:

* How do I integrate MyOperator with [CRM name]?
* What are MyOperator’s API rate limits?
* How does call recording compliance work in India?