What is Salezshark CRM? How do I integrate MyOperator with Salezshark?

What is Salezshark CRM? How do I integrate MyOperator with Salezshark?

⚡Quick answer -

SalezShark is a cloud CRM for sales and marketing. Integrating MyOperator adds click‑to‑call, screen pops, automatic call logging, and recording links inside SalezShark. To set it up, get two webhook endpoints from SalezShark (inCallWebHook and afterCallWebHook), share your MyOperator number with MyOperator Support, and complete the endpoint + secret configuration.

Test by placing a call and confirming screen pop + call log + recording URL in the contact timeline.

What is SalezShark CRM?

SalezShark is a cloud‑based CRM that helps teams capture leads, manage pipelines, run email campaigns, and report on performance. It supports contact segmentation, tasks/reminders, and permissioned access for teams.

Why integrate MyOperator with SalezShark

  • Click‑to‑Call: Dial contacts directly from SalezShark.
  • Incoming Screen Pop: See caller context (lead/contact) when the phone rings.
  • Auto Call Logging: Inbound/outbound calls logged against the right record.
  • Recording & Notes: Recording URL attached; agents add notes/dispositions.
  • Follow‑ups: Create tasks from call outcomes.
  • Unified Analytics: Combine call KPIs with CRM funnel metrics.

Before you start (prerequisites)

  1. MyOperator: Active account and service number (DID/toll‑free) you’ll connect.
  2. MyOperator plans - SUV and Above (New Plans)
    Growth or higher (Old Plans)
  3. SalezShark: Admin access to configure webhooks/integrations.
  4. Support contacts: Ability to open tickets with both vendors.
  5. Test user & test lead: For end‑to‑end validation.
  6. (Recommended) Secure endpoint with HTTPS + a shared secret for signature verification.

How the integration works (at a glance)

  1. MyOperator emits events when a call starts and ends.
  2. It POSTs JSON to SalezShark webhooks:
    • inCallWebHook → when a call starts (for screen pop).
    • afterCallWebHook → after the call ends (for logging + recording URL).
  3. SalezShark matches the phone number to a lead/contact, opens a screen pop, and logs the call with details.

Step‑by‑step: Enable the integration

  1. Collect details
    • Your MyOperator service number(s) and account ID.
    • SalezShark will provide two webhook URLs: inCallWebHook and afterCallWebHook (plus an optional secret/token).
  2. Open a MyOperator Support ticket
    • Subject: Enable SalezShark CRM integration for
    • Include: service number(s), the two webhook URLs, and any shared secret you want MyOperator to use for signing requests.
  3. Configure in MyOperator (once Support enables the connector)
    • Go to Manage → Integrations → SalezShark (labels may vary).
    • Paste inCallWebHook and afterCallWebHook.
    • Add Authorization header or signature secret if provided by SalezShark.
    • Save.
  4. Configure in SalezShark
    • In Settings → Integrations/Webhooks, confirm both endpoints are active and set to accept MyOperator payloads.
    • Map phone fields to your standard (e.g., E.164).
    • Enable screen pop and auto‑log options.
  5. Test end‑to‑end
    • Create a test contact with your mobile number.
    • Place an inbound call to your MyOperator number from that mobile.
    • Expect: screen pop at ring; call log + recording URL after hang‑up.
    • Place an outbound call via click‑to‑call and confirm logging.

Expected result -

  • Ringing triggers screen pop.
  • Call completion posts a timeline entry with direction, duration, status, agent, and recording URL.
  • New unknown numbers can auto‑create leads (if enabled).

What success looks like

  • Agents click‑to‑call from SalezShark, and every call is logged automatically.
  • Incoming calls show who’s calling with context (open deals, last notes).
  • Supervisors see recordings and durations in the CRM timeline and can report on conversion vs call activity.

Troubleshooting & edge cases

  1. No screen pop on the ring
    • Confirm inCallWebHook URL is correct and reachable (200 OK).
    • Check that the caller number format matches CRM (use E.164).
    • Verify the contact exists or enable auto‑create lead.
  2. Call doesn’t log after hang‑up
    • Check afterCallWebHook URL, SSL certificate, and authentication token.
    • Ensure your SalezShark workflow for call_ended events is active.
  3. Recording URL missing
    • Verify call recording is enabled in MyOperator and the user/department policy allows capture.
    • Confirm SalezShark field mapping for recording_url.
  4. Duplicate contacts created
    • Turn on dedupe rules in SalezShark (match on phone/email).
    • Normalise numbers (country code) before matching.
  5. 403/401 on webhook
    • Align Authorisation headers or signature secrets on both sides.
    • Rotate secrets and re‑test.