Convarza AI
Channels & setup

The settings every channel has, and the ones only some do

Chat channels and calling channels deliberately do not share controls. Knowing which set you are looking at saves hunting for a field that was never meant to exist.

A recurring support question is some version of "where is X on this channel?" — and the answer is usually that X does not exist on that kind of channel, on purpose.

The product refuses to show a control that cannot mean anything. A web widget has no trunk, so it has no trunk settings. A chat has no calling hours, so it has none. This is better than greying out a dozen irrelevant fields, but only if you know the rule.

Reference

Both kinds share three things

The connection card (credentials, health, and for manual setups the webhook), the routing decision, and the Enabled checkbox. Those exist on all thirteen types.

Chat channels get contact and closing behaviour

Do not create contact, and auto-close conversation. Both live under additional settings.

The two chat-only extras. Neither appears on a calling channel.
The two chat-only extras. Neither appears on a calling channel.

Calling channels get resource, region and direction

Plus restricted call timings and a larger additional-settings block. None of these appear on a chat channel.

Calling channels have more under additional settings

Forwarded-from numbers, forward-to number, the IP/domain match list, ping timeout and allowed calls count.

Allowed calls count is the one you will use. The rest matter mainly on SIP.

WhatsApp gets a card nothing else has

Templates, flows, canned messages, payment settings, the QR block, the channel message user and broadcast timings. No other channel type has those concepts.

The WhatsApp-only card. If you are looking for templates on another channel, they do not exist there.
The WhatsApp-only card. If you are looking for templates on another channel, they do not exist there.

Know which fields are admin-only

Credential fields and the connected-account row. A manager owns everything operational: routing, hours, additional settings, enable and disable, and the health readout.

The product shows those controls to managers rather than hiding them, so a manager can see what to ask an admin for.

Put it to use

Open one chat channel and one calling channel side by side and compare them once. Ten minutes of that is worth more than reading any list, and you will not have to look up which controls exist again.

Worth knowing

The parts people get wrong

  • The two sets never borrow each other's controls. If you are hunting for calling hours on a web widget, they were never there.
  • Enabled is not the same as connected. A channel can be perfectly connected and switched off.

Rather be shown than read?

Thirty minutes, your numbers and your channels on the screen.

No setup fee. No per-conversation charge. Cancel from inside the product.