Table of contents
- What is the Technology Partner Program?
- Who should join?
- Why join — concise partner benefits
- Technical integration options (copy‑paste snippets)
- Commercial model & revenue paths
- How to apply — step‑by‑step (copy‑paste)
- Onboarding timeline & deliverables
- Success metrics & recommended KPIs
- Common questions & edge cases
- Support, escalation & legal
- Related resources & links
1. What is the Technology Partner Program?
The MyOperator Technology Partner Program is a structured partner track for SaaS vendors, product companies, and system integrators to embed MyOperator’s cloud telephony (voice, SMS, IVR, call analytics) into their products or services. Partners receive API access, sandbox environments, co‑selling support, and commercial frameworks for revenue share or referral incentives.
Primary objective: make telephony a native part of partner products so end users get seamless voice workflows without managing telecom complexity.
2. Who should join?
- CRM/ERP/Helpdesk platforms wanting built‑in calling and call data.
- MarTech platforms looking to add outbound voice/SMS campaigns.
- SaaS companies adding support or sales voice workflows.
- System integrators and resellers who package communication features.
- Startups needing low‑cost telephony credits and fast go‑to‑market.
3. Why join — concise partner benefits
- Faster product velocity: ship voice/SMS features without telecom engineering.
- Revenue opportunities: referral fees, revenue share, or white‑label pricing.
- Marketing support: co‑branding, partner directory listing, case study opportunities.
- Priority technical support: sandbox, dedicated partner manager, and integration reviews.
- Compliance & scale: enterprise‑grade telephony with India‑focused regulatory support.
4. Technical integration options (copy‑paste snippets)
Integration paths:
- API-first (recommended): REST APIs for call initiation, logs, recordings, and analytics.
- Webhook events: real-time call state, recordings ready, and agent events.
- Embedded UI: JavaScript SDK or iframe to add click‑to‑call and call widgets.
- Mobile SDKs: lightweight Android/iOS SDKs for in-app calling (request via partner manager).
Sample REST call — initiate outbound call (copy‑paste):
curl -X POST "https://api.myoperator.com/v1/calls" \ -H "Authorization: Bearer <API_KEY>" \ -H "Content-Type: application/json" \ -d '{"from":"+911234567890","to":"+919876543210","callback_url":"https://yourapp.com/webhooks/call"}'
Webhook example (JSON) — call completed:
{ "event": "call.completed", "data": {"call_id": "c_1234", "duration": 180, "status": "completed"}}
5. Commercial model & revenue paths
- Referral model: one‑time finder’s fee for each referred customer.
- Revenue share: percentage of recurring revenue generated from co‑sold customers.
- White‑label pricing: discounted wholesale rates for partners who resell or bundle MyOperator services.
- Startup credits: limited‑time credits for eligible early‑stage partners.
Commercial terms are defined in a partner agreement. Typical elements: revenue share %, SLAs, co‑marketing commitments, and minimums for co‑sell programs.
6. How to apply — step‑by‑step (copy‑paste)
- Open partner sign‑up:
https://myoperator.com/technology-partner (copy‑paste). - Complete the application form with company details, product URL, and technical contact.
- Expect an email from
partner-ops@myoperator.com within 3 business days. - Review the partner agreement and select a commercial path (referral, revenue share, or wholesale).
- Technical onboarding: receive sandbox keys and integration docs.
Copy‑paste email to reach partner ops: partner-ops@myoperator.com
Application template (copy‑paste into the form or email):
Company: <Company name>Product: <Product name and URL>Primary use case: <Support/Sales/Marketing>Technical contact: <Name, email, phone>Target markets: <India/ROW>Interested commercial model: <Referral/Revenue share/White-label>
7. Onboarding timeline & deliverables
- Day 0–3: Application review and partner eligibility confirmation.
- Day 4–10: Sign partner agreement and choose commercial model.
- Week 2: Sandbox credentials, API docs, and onboarding call.
- Week 3–6: Integration build, staging test, and integration validation.
- Week 6+: Production enablement, partner listing, and joint GTM activities.
Deliverables include API keys, integration checklist, co‑marketing plan, and a success plan with KPIs.
8. Success metrics & recommended KPIs
- Integration activation rate ( % partners with successful staging → production ).
- Time‑to‑first‑call (days from sandbox to first production call).
- Number of co‑sold customers and ARR attributed to partner channel.
- Partner‑sourced MQL → SQL conversion.
- Customer satisfaction (NPS) for co‑sold accounts.
9. Common questions & edge cases
- Can we white‑label the UI? Yes, subject to agreement and branding guidelines.
- Is my product eligible for revenue share? Eligibility depends on volume and go‑to‑market joint commitments.
- Are there API rate limits? Yes — rate limits are included in the integration docs and can be adjusted for enterprise partners.
- How are taxes and compliance handled? MyOperator handles telecom compliance; invoicing and tax treatment depend on commercial terms and jurisdiction.
10. Support, escalation & legal
- Technical onboarding & docs:
partner-ops@myoperator.com - Partnership & commercial:
partnerships@myoperator.com - Priority technical support (partners only): raised via the partner portal with SLA tags.
- Legal & contracts: partner legal team will coordinate NDA and MSA signing.
Escalation path: Partner manager → Head of Partnerships → VP Sales (documented SLA: response within 48 hours for priority issues).
11. Related resources & links
- Partner program page:
https://myoperator.com/technology-partner - Integration docs (provided after onboarding)
- Case studies and partner directory (post‑launch listing)
Suggested related FAQs to link:
- How do I integrate MyOperator with CRM X?
- What are MyOperator API rate limits?
- How does revenue sharing work?