Articles on: MyOperator

How do I become a MyOperator technology partner?

MyOperator Technology Partner Onboarding


Apply via the Technology Partner form or email partnership@myoperator.co. Complete onboarding, use sandbox and API docs to build and test your integration, pass verification, and go live. Co-marketing and directory listing are optional after go-live.



Quick summary (1 line)


Apply → Onboarding call → Get sandbox & docs → Build & test → Verify → Go live → (Optional) Co-market.



Who should apply


  • Registered companies (SaaS, CRM, telephony/PBX/IVR vendors).
  • Integrations that add value to MyOperator (lead routing, CTI, analytics, CRM sync).
  • Teams able to dedicate at least one technical contact for onboarding and testing.



Prerequisites (what we’ll ask for)


  • Company name, legal entity and invoicing contact.
  • Short integration brief (what you’ll integrate: auth, webhooks, API endpoints).
  • Primary technical contact (name, email, Slack/Teams preferred).
  • Target timeline and a staging/test environment (recommended but optional).



Step-by-step: How to join (detailed)


  1. Apply (Start)


  • Fill the Technology Partner form on the MyOperator partner page or email: partnership@myoperator.co.
  • Include: company name, website, short integration description, technical contact, and preferred go-live month.


  1. Onboarding call (30–45 min)


  • A partner manager schedules a call to align goals, confirm prerequisites, and share the success criteria.


  1. Get developer resources


  • You will receive: sandbox credentials, API docs, example requests/responses, webhook specs, and IP/URL allowlist details.


  1. Implement & test


  • Implement authentication, required API endpoints, and webhook handlers. Use the sandbox for end-to-end testing.
  • Recommended test checks:
    • Auth / token lifecycle
    • Webhook signature verification
    • E.164 phone number formatting
    • Retry logic for transient failures


  1. Example webhook payload (copy-paste for your test harness):


{
"event_type": "call.connected",
"call_id": "abc123",
"from": "+919876543210",
"to": "+911234567890",
"timestamp": "2025-07-24T12:34:56Z",
"metadata": {
"lead_id": "lead_987"
}
}


  1. Sandbox verification


  • Share test logs and sample requests/responses with the partner manager. MyOperator will run verification tests to confirm integration behavior.


  1. Production go-live


  • After verification, production credentials are issued and a short monitoring window is scheduled to confirm stability.


  1. Post-go-live: listing & co-marketing (optional)


  • Eligible partners may be listed in the MyOperator Partner Directory and considered for joint promotion (case study, blog, newsletter).



Success criteria (what success looks like)


  • Integration passes sandbox verification tests.
  • Production creds issued and live traffic delivered for the agreed monitoring window.
  • No critical errors for the agreed acceptance period (typically 48–72 hours).



Common edge cases & troubleshooting


  • Webhook not delivered: check allowlist, firewall, and HTTPS certificate chain; confirm retries and idempotency.
  • Signature validation fails: confirm HMAC secret, header name, and timezone/clock skew.
  • Auth 401/403: check token scope and expiry; refresh tokens if required.
  • Phone formatting mismatch: ensure phone numbers use E.164.


Info

When contacting support, include: sandbox account ID, timestamps, sample payload(s), and request IDs.



Support & escalation


  • Partnership & onboarding: partnership@myoperator.co (include company name + integration brief).
  • Developer support: dev support channel provided after onboarding (ticket system or Slack/Teams link).
  • Urgent escalations: request the partner manager on the onboarding call to open an incident.



Typical timeline (examples)


  • Apply → Onboarding call: 1–7 business days.
  • Build & test: 2–8 weeks (depends on scope).
  • Verification & go-live: 1–5 business days after tests pass.



Suggested visuals & accessibility


  • Onboarding flow diagram (4 steps: Apply → Onboard → Build/Test → Go live).
  • Alt text: “Partner onboarding flow: Apply, Onboarding call, Build & Test, Go live.”
  • Sandbox API screenshot showing a sample cURL request/response and the webhook test page.
  • Caption + alt text provided for each image.

Updated on: 11/09/2025