# Channels: editing in a side panel

Review channel configuration in a side panel within the list. Learn how to configure and validate the feature in your environment.

Source: https://zild.ai/en-US/docs/apps/zild-assist/updates-canais-edicao-painel

Review channel configuration in a side panel within the list. Learn how to configure and validate the feature in your environment.

## How to use it

Open the channel list and edit the desired channel. Review settings in the panel, save and confirm the result in the list. Check the associated agent and provider before testing incoming conversations.

## Limits and prerequisites

This improves the editing workflow; it neither grants access to new channels nor replaces provider configuration and authentication.

## Validate in your operation

Edit a test configuration and verify persistence after reopening the panel. For service-affecting changes, check incoming messages and routing.

## Prepare the account and connect through Meta

Cloud API uses a Meta business portfolio, a WhatsApp Business Account (WABA) and a business phone number. Confirm with the administrator who may authorize those assets. Account and phone-number identifiers differ from the visible phone number and the Zild API key.

In the reviewed Zild version, open the WhatsApp API channel configuration and save it before connecting. In the Meta connection area, use Login with Facebook and complete embedded signup with the company assets. The interface receives an authorization code, WABA ID and Phone Number ID; WhatsApp Identifier and WhatsApp Account SID are read-only fields in this workflow. Labels may be translated depending on interface language.

Wait for connection confirmation and reopen the channel to check its agent association. A coexistence option exists in the implementation, but selecting it does not prove Meta has enabled the account and number. Confirm eligibility during embedded signup before planning simultaneous use or migration of an existing number.

## Confirm operations before expanding the channel

Cancelled signup, missing identifiers and pending authorization are incomplete states. Check the displayed message and permissions with the owner; do not remove an active integration merely to retry. Screen availability depends on the deployed version.

With an authorized test contact, separately validate incoming messages, agent replies, delivery status and handoff to the correct queue. Check the association between channel, conversation and process; an API-accepted send does not prove delivery or receipt of events. If an event does not arrive, the administrator must review the webhook subscription and destination for the deployed integration. This guide does not provide a universal webhook URL.

Record the outcome, time and failure owner without copying tokens into the report. Only then expand recipients and volume. For template tests, confirm language, variables, approval and purpose; follow the window and consent rules applicable to the channel.

## Shared contacts in field processes

When the WhatsApp channel receives a shared contact, the integration prepares a message for each contact in the event. Text uses the name and the first non-empty phone number received. When the event contains a vCard accepted by the integration, it is stored as contato.vcf and associated with the message; missing content or invalid encoding leaves readable text without a vCard file.

For a delivery or technical visit, use this to record the contact provided for the location and review it alongside the incident. Do not confuse the shared contact with the conversation sender: receiving a card does not establish identity, permission to change the recipient or creation of an ERP record. Confirm the responsible person and delivery or service-order reference before operational changes.

Use fictional data to validate a contact with a file, a text-only contact and an event containing multiple contacts. Check the messages actually persisted in the deployed version; the text summary does not guarantee that all phone numbers in the card are visible.

## Availability

Feature identified in the platform code in October 2026. Availability depends on the deployed version, permissions and environment connectors. Contact Zild if it is not visible yet.

Documentation reviewed: 2026-10-28.

[Read the announcement](/en-US/blog/canais-edicao-painel)