Polymorfa vs Wavoip

Three reasons teams move from Wavoip

1. 01

   Messages and calls on the same number

   On Polymorfa, the number that sends your messages also places and answers calls. Messages, groups and calls use the same session, the same credentials and the same webhook endpoint, on one bill.^8,2

   Wavoip: Wavoip covers the call. Messages stay on the Baileys or Evolution session you already run, bridged into Wavoip.⁹

2. 02

   Webhooks that keep delivering through an outage

   Polymorfa signs every delivery with HMAC-SHA256 and makes up to eight delivery attempts over 24 hours, set per webhook. Eleven call events, from call.received to call.telemetry, reach the same handler as your message events, and the deliveries API retries anything that still failed.^3,2

   Wavoip: Wavoip gives up after a few retries and disables the webhook.¹⁰

3. 03

   QR or pairing code, plus video and SIP

   Calls run in a browser, in server code that reads and writes PCM audio, or on your PBX through a SIP trunk. Linked-device numbers also take video and group calls. Cloud API calls are one-to-one audio. Polymorfa does not record calls.^2,6

   Wavoip: Polymorfa's hosted QuickLink page pairs a number by QR code or pairing code, so your customer connects from the phone alone.¹¹

   import { MessagingClient } from "@polymorfa/sdk";
   
   const messaging = new MessagingClient({
     credential: { type: "apiKey", value: process.env.POLYMORFA_KEY! },
   });
   
   // The same session that sends this customer's messages
   const placed = await messaging.voip.place({
     session: "support",
     to: "+5511999999999",
     video: false,
   });
   // call.accepted and call.ended arrive on your webhook