Articles on: MyOperator

What AfterCall services does MyOperator offer and how do I enable each one?

Info

Quick answer — MyOperator offers multiple AfterCall automations that trigger the moment a call ends.


You can:


  1. Send an SMS
  2. Send an Email alert
  3. Push Call Logs via Webhook
  4. Auto-sync call details to your CRM
  5. Send WhatsApp messages (NEW — WhatsApp API required)


All services can be configured in under a few minutes and verified via Notification Logs, Webhook Logs, or your CRM.


When should I use this guide?


Use this guide if you want to automate “next steps” after a call:


  • ✔ Sending follow-up or acknowledgement messages
  • ✔ CRM updates
  • ✔ Supervisor notifications
  • ✔ Triggering workflows in external systems
  • ✔ Sending WhatsApp notifications for improved engagement


This reduces manual work and ensures faster, consistent follow-ups.



1 — AFTERCALL SERVICES AT A GLANCE


Service

What it does

Typical Triggers

Common Uses

AfterCall SMS

Sends templated SMS to customer or agent

Missed, Voicemail, Answered

Callback links, survey URLs, thank-you text

AfterCall Email

Sends call details via email

Missed, VIP caller, Long calls

Supervisor alerts, QA review, shift monitoring

Webhook (Call-Log Push)

Sends call data (JSON) to your server

Any call completion

Trigger workflows, DB updates

CRM Sync

Creates/updates lead/activity

Any call completion

Auto-logging calls in CRM

NEW: AfterCall WhatsApp Message

Sends templated WhatsApp messages

Missed, Answered, Voicemail

Fast customer engagement, CSAT surveys, callback instructions



2 — Prerequisites (common to all)


  • Admin role in MyOperator (to create/configure automations)
  • SMS: sufficient SMS credits and correct E.164 numbers
  • Email: verified sender address (or SMTP configured)
  • Webhook: HTTPS endpoint that accepts POST + returns 2xx for success
  • CRM: Connected CRM app / authorised user and mapping ready
  • WhatsApp AfterCall: an approved WhatsApp template for business-initiated messages and sufficient Meta message quota/account balance



3 — Set up SMS notifications


  1. Dashboard → Call → AfterCall SMS.
  2. Recipients: Customer, Agent, Custom number, or Department.
  3. Trigger: Missed, Answered, Voicemail, etc.
  4. Template: Compose text. Variables available: {{caller_number}} {{department_name}} {{call_id}} {{timestamp}}.
  5. Save and toggle Enable.



Alt text: Set up SMS notifications



4 — Set up Call-Log Push (webhook)


  1. Dashboard → APIs & Webhook → Calling Webhooks → Webhooks (AfterCall).
  2. Endpoint URL.
  3. Event filter: All / Missed / Answered / Voicemail.
  4. (Optional) Headers: X-Shared-Secret: your-secret.
  5. Test: Click Send test event; expect HTTP 2xx.
  6. Save and toggle Enable.



Alt text: Set up call-log webhook



5 — Set up CRM data sync


  1. Integrations → CRM → (Select CRM).
  2. Click Connect and authorise the app/user.
  3. Field mapping:


Call Field

CRM Field

caller_number

Lead/Contact Phone

outcome

Call Status

recording_url

Attachment / Link


  1. Rules: Upsert by Phone → Create if not found.
  2. Toggle Attach recording (optional) and Enable.



6 — Set up email alerts


  1. Manage → Automations → AfterCall → Email.
  2. Add Recipients (users, groups, external).
  3. Trigger: Missed, VIP caller, Long duration > X min.
  4. Subject/Body:
  5. Subject: Missed call from {{caller_number}}
  6. Body: Missed at {{timestamp}}. Ref: {{call_id}}.
  7. Save and flip Enable.



7 — WhatsApp AfterCall (new)


Warning

Important: WhatsApp business-initiated messages must use pre-approved templates. AfterCall WhatsApp uses templates to send messages after a call ends.


  1. Ensure you have:
  • a live MyOperator WhatsApp account,
  • at least one approved template (Manage → WhatsApp → Templates),
  • sufficient message quota/account balance.
  1. Manage → WhatsApp → AfterCall WhatsApp (or Manage → Automations → AfterCall → WhatsApp)
  2. Select the WhatsApp account & phone number, choose trigger(s) (Missed / Voicemail / Answered), and pick an approved template.
  3. Map template variables to call variables (or static fallback values).
  4. Save and Enable.
  5. Verify: check campaign/notification logs for WhatsApp send status and Meta message consumption.


Notes/constraints:


  • WhatsApp templates are reviewed by Meta — approval time varies.
  • Sending a template opens a paid conversation under Meta rules (billing & message limits apply).
  • If you want free-form messages, the customer must first message you (opens a 24-hour window). AfterCall WhatsApp is for business-initiated templates only.



8 — How to confirm it worked (quick checks)


  • SMS: Notification Logs → delivered/failed (1–3 min typical)
  • Email: recipient inbox (check spam) (under 2 min typical)
  • Webhook: your server must return 2xx; check your access logs for POST events (real-time)
  • CRM: activity/lead created in CRM (1–5 min typical)
  • WhatsApp: check WhatsApp activity logs + Meta conversation counter; message status (sent/delivered) in panel


Always run one test call per service to confirm end-to-end flow.



9 — Edge cases & best practices


  • Use call_id as a unique key (idempotency) to avoid duplicate processing.
  • Queue webhooks & implement retries (exponential backoff) to handle transient failures.
  • Respect privacy: purge recordings per policy and do not send PII over insecure channels.
  • SMS: honour STOP/opt-out keywords and maintain suppression lists.
  • WhatsApp: only use templates for business-initiated messages; avoid marketing content in transactional templates (Meta may reclassify/reject).
  • For high volumes, stage and test on non-production numbers first.



10 — Troubleshooting matrix (common problems)


  • SMS not delivered → No credits / invalid number.
  • Fix: Recharge, use E.164 format.
  • Webhook 4xx/5xx → Auth/header mismatch or server error.
  • Fix: Align headers, return 2xx on success.
  • Duplicate CRM leads → Create-only rule used.
  • Fix: Switch to upsert by phone.
  • Email in Spam → Sender reputation.
  • Fix: Add to allow-list, verify SPF/DKIM.
  • WhatsApp not sent → Template not approved / insufficient message quota.
  • Fix: Use the approved template, increase quota via FBM verification or balance top-up.
  • Nothing triggers → Service disabled or incorrect filter.
  • Fix: Enable the AfterCall toggle and verify trigger filters.


If you can’t resolve, escalate with: support@myoperator.com — include Call ID, timestamp, service name, and a screenshot of the automation.



11 — Quick examples (real use cases)


  • Missed call → SMS: “Hi, we missed your call from {{caller_number}}. Reply or click {{callback_url}} to request a callback.”
  • Voicemail → Email: Supervisor gets an email: “Voicemail from {{caller_number}} at {{timestamp}} — recording: {{recording_url}}
  • Any call → Webhook: Push JSON to your ticketing system to auto-create a support ticket with call_id, caller_number, and recording_url.
  • Answered → WhatsApp template: Send a post-call summary template with invoice/payment link (requires approved template & quota).


Keywords: MyOperator AfterCall, post-call automation, webhook call.completed, SMS after missed call, CRM call logging

Updated on: 09/01/2026