Skip to content

Channel Overview ​

Perfox agents work across web chat, browser voice, phone calls, WhatsApp, SMS, email and eight messaging apps. This page is the short answer to "what can I connect today, and what do I need for each channel". Read it before you plan an integration around a particular vendor.

What you can connect ​

You connect channel providers yourself on Admin → Connections. This is what the page offers today:

ChannelProvider on the Connections pageNotes
Phone calls (inbound and outbound)PlivoOne Plivo connection covers voice, SMS and WhatsApp
SMSPlivoIndia DLT fields live on the same connection
WhatsAppPlivoSend and receive through Plivo as your WhatsApp provider
EmailResend, AWS SES, SendGrid, Postmark, Mailjet, Mailgun, Gmail / Google Workspace, SMTP / IMAP, Microsoft 365 (Email)Nine providers. Each card says how it receives mail
Messaging appsTelegram bot, Slack app, Facebook Messenger, Instagram Direct, Microsoft Teams bot, Discord app, Google Chat app, RCS Business MessagingThe Messaging apps section. Each card connects your own bot or app on that platform. See Messaging Apps
Web chat and browser voiceNothing to connectPerfox manages them. Turn them on in the Web Chat trigger

The Connections page: a connected Plivo card covering WhatsApp, SMS and Voice, followed by the email providers.

You don't connect the AI and voice models (Gemini, OpenAI, Sarvam, ElevenLabs) on this page. You pick them for each agent on its AI Model sub-node, and they work with no extra setup. See Voice Providers.

Not on the Connections page

A direct Meta WhatsApp Cloud API connection isn't self-serve. If you need it, raise a ticket in the Support Center. The page doesn't offer Twilio or Exotel either, and neither can carry traffic.

Replying: which channels need a Sender ​

A channel trigger lets a message start your agent. On email, SMS, WhatsApp and the messaging apps, sending the reply is a separate choice:

ChannelHow the reply reaches the customer
Web chat, browser voice, phone callsInline, over the widget or the call itself. You need nothing extra
Email, SMS, WhatsAppOnly when an Email Sender, SMS Sender or WhatsApp Sender action is connected to the AI Agent's Action port
Messaging appsOnly when a Chat Sender action, set to that app, is connected to the AI Agent's Action port

If one of these agents has no matching Sender, the inbound message is trigger-only. The agent runs and you can read its answer in Conversations, but nothing goes back to the customer, and that message is marked as not delivered. This is on purpose, because some agents only take messages in. Perfox shows it as a publish warning, not an error. It is also the most common reason a new agent seems to "do nothing". When a Sender is connected, the agent knows its reply is delivered for it, so the customer never gets the same answer twice.

The Email, SMS and WhatsApp Senders ask for the same things: an Instruction that tells the AI when to use it, a Send from number or address from your Connections (you can't publish without it), Send to, and What to send. The Chat Sender only asks which Messaging app it replies on: the reply always goes back to the chat the customer wrote from, through the bot they wrote to. When a Sender runs as a step in your flow with fixed or template text, variables in the message are filled from the run (for example a post-call Summary: ); a variable with no value is left blank. The details are on Sender Nodes.

No default sender ​

Every message and call leaves from a number or address that is linked to the agent: the business contact on its trigger, or the Sender's Send from. It goes out through the connection that owns that number or address. There's no default number, address or account to fall back on:

  • SMS and WhatsApp go through the Plivo account that lists the number.
  • Email goes through the provider account that owns the address (with AWS SES, any identity you've verified there). A reply leaves from the inbox the customer wrote to, even when that inbox was only in Cc.
  • A Send from that none of your connections owns shows as an amber warning when you publish.

A refused send or call isn't silent. When no connection owns the sender (or none is linked), Perfox records it and your workspace gets a notification such as "SMS from +91… was refused", linking to the agent or to Connections, at most once a day for each channel and number (see Notifications). And whenever an email, SMS or WhatsApp send is refused (no account owns the number, the contact is on your Suppression List, the daily limit was reached, or the provider refused it), the agent gets the reason. It doesn't retry, and on a call it can tell the customer the message couldn't be sent right now.

Messages Perfox ignores ​

Some incoming messages are dropped at the door, with no reply and no customer record, conversation or charge:

  • Blocked senders. A contact on your Suppression List with direction Inbound or Both is ignored: no reply, and calls are rejected. This covers SMS, WhatsApp, RCS, email and phone calls. On web chat it applies only to a customer who has identified themselves with that phone or email; an anonymous visitor is never blocked.
  • Machine mail. Bounces, auto-replies, bulk mail and system senders such as no-reply or mailer-daemon.
  • Email that fails DMARC. A message whose sender domain fails DMARC is refused, so a forged address can't reach your agent or create a customer.

Bridging a gateway of your own ​

You can also connect a gateway of your own through the Webhook trigger. That works, but you have to map the caller's identity before it behaves like a real channel, because a plain webhook run has no end user attached.